# JPMorgan on Solana: What Tokenized Funds Mean for Onchain Data

J.P. Morgan Asset Management has brought two tokenized money market funds to Solana. For developers, the opportunity is not simply another token to trade—it is another category of financial activity to observe, interpret and integrate into applications.

On October 22, 2026, the firm announced that MONY and JLTXX are available on Solana to qualified U.S. investors through Morgan Money. Investors subscribe and redeem through the platform and receive token balances at their blockchain addresses. [J.P. Morgan’s announcement](https://am.jpmorgan.com/us/en/asset-management/institutional/about-us/media/press-releases/jp-morgan-asset-management-expands-access-to-tokenized-money-market-funds-solana/).

The important distinction is this: **a financial asset can exist on a public blockchain without being freely available to every wallet.**

For teams building monitoring tools, treasury dashboards and market-data infrastructure, understanding that distinction is where useful work begins.

## What are MONY and JLTXX?

The two products are money market funds with different structures:

- **MONY — My OnChain Net Yield Fund:** a private-placement fund for qualified investors seeking U.S. dollar yields.
- **JLTXX — JPMorgan OnChain Liquidity–Token Money Market Fund:** a U.S.-registered government money market fund designed to support reserve investments by stablecoin issuers.

Both belong to J.P. Morgan Asset Management’s tokenized liquidity offering. They are not shares in JPMorgan itself, and tokenization does not turn them into ordinary permissionless trading assets. [Background on the funds](https://am.jpmorgan.com/us/en/asset-management/adv/about-us/media/press-releases/jp-morgan-asset-management-launches-second-tokenized-fund-on-ethereum/).

For developers, the practical question is therefore not only “can I buy this token?”

It is also: **what can my application reliably learn from its onchain activity?**

## Public visibility does not mean unrestricted access

Public blockchains expose transaction and account data. Access to a financial product is a separate matter.

Solana’s token infrastructure can support issuer controls, including freezing token accounts. Token extensions can also introduce additional transfer logic: a transfer hook, for example, can enforce rules about which wallets may receive a token. [Solana token documentation](https://solana.com/docs/tokens), [transfer hooks](https://solana.com/docs/tokens/extensions/transfer-hook).

These are general capabilities—not a claim that every tokenized fund uses the same configuration.

A monitoring application should inspect the specific token’s program, authorities and extensions rather than assume that familiar wallet interfaces imply familiar transfer rules.

Being able to observe an asset does not establish eligibility to hold it, transfer it or redeem it.

## Start with the issuer’s token addresses

Token names and symbols are not reliable identifiers. On Solana, a token is identified by its mint address.

J.P. Morgan published the following Solana addresses in its announcement:

**MONY**

```text
EToDtBM2knZ8N1BHyUq2Riq5ngWTcoD3k6qpsgf7CKYY
```

**JLTXX**

```text
J4cTuCH6frt4AnEmKfMS2k8hsUf7K94PV62sjUJno8Cz
```

Use the [issuer’s publication](https://am.jpmorgan.com/us/en/asset-management/institutional/about-us/media/press-releases/jp-morgan-asset-management-expands-access-to-tokenized-money-market-funds-solana/) as the starting point for your asset registry—not a matching ticker or an unsolicited token link.

For each asset, retain its network, mint address, token program, decimals and the source used to verify its identity.

## What onchain data can—and cannot—tell you

An application can inspect token supply, token-account balances and recorded transactions. Solana’s `getTokenSupply` method, for example, returns the supply associated with a particular mint. [RPC reference](https://solana.com/docs/rpc/http/gettokensupply).

The harder part is assigning economic meaning to those observations.

A monitoring system should not automatically label:

- A token transfer as a new investment.
- A newly created token account as a new investor.
- A supply increase as money newly entering Solana.
- A wallet balance as independently verified fund assets.
- A visible transaction as a trade executed at a market price.

Those conclusions require additional context.

A useful dashboard distinguishes **what the chain records** from **what the application infers**. When the economic purpose of a movement is unknown, keeping it unclassified is better than presenting an unsupported inflow figure.

## Build monitoring around events, state and verification

A practical tokenized-asset monitoring system needs more than a live transaction feed.

### Establish a baseline

Read the relevant mint and token-account state. Record the observation slot and commitment level so that subsequent comparisons have a defined starting point.

### Observe relevant transactions

Track the programs and accounts involved in the activity your application needs to monitor.

A mint-only address filter should not be assumed to capture every relevant operation. Coverage depends on the transaction format, account references and the interface being consumed. Maintain the account relationships your application needs instead of treating one subscription as a complete asset index.

### Verify execution before updating authoritative records

An observed signed transaction expresses an instruction to the network. It does not, by itself, prove that balances changed.

Use execution results and account state to establish what actually happened. Solana’s `getTransaction` method can retrieve a transaction at the requested supported commitment, including execution metadata when available. [Transaction reference](https://solana.com/docs/rpc/http/gettransaction).

### Reconcile interruptions

Store signatures, distinguish provisional observations from verified outcomes, and detect gaps.

If a stream disconnects, do not silently interpret the missing interval as “no activity.” Recover through an appropriate historical source and reconcile against current state.

**A fast event starts an investigation. Verified state supports the conclusion.**

## Where Shredo fits

Different applications should begin at different points in the data pipeline.

[**Shredo Raw Shreds**](https://docs.shredo.xyz/products/raw-shreds) delivers deduplicated Solana shreds over UDP for teams operating their own reconstruction and parsing infrastructure.

[**Shredo Decoded Transactions**](https://docs.shredo.xyz/products/decoded-transactions) delivers reconstructed, signed transactions through authenticated gRPC, with program and account filters. It lets developers begin with transaction events instead of building shred reconstruction first.

A team could use these inputs to trigger analysis of relevant account activity, classify transaction instructions or feed an alerting pipeline.

However, Decoded Transactions is not a ready-made fund-transfer index. It does not include canonical execution results, live balances or a verified interpretation of fund subscriptions and redemptions. Applications requiring those outputs need additional state, execution and reconciliation components.

Not every tokenized-asset application needs the earliest possible signal. A periodic reporting dashboard may be well served by finalized records. A time-sensitive monitoring system may benefit from earlier observations followed by verification.

Choose the interface around the application’s requirements—not around latency alone.

## Does every tokenized asset belong in a pool catalogue?

No.

An asset being represented on Solana does not establish that it has a supported DEX pool, executable liquidity or unrestricted secondary trading.

[Shredo Pool Catalogue](https://docs.shredo.xyz/products/signed-pool-catalogue) provides an inventory of supported liquidity pools and their dependency accounts. It is not a registry of every tokenized security, and the JPMorgan announcement should not be interpreted as a claim that these funds are covered by the catalogue.

Pool discovery becomes relevant when an application needs to analyse an actual supported trading venue.

## The opportunity is better financial observability

JPMorgan’s expansion gives developers a concrete reason to think beyond dashboards designed only for memecoins and swaps.

Potential applications include verified asset registries, account-activity alerts, supply monitoring and reconciliation tools.

The strongest implementations will make their boundaries explicit: which assets they recognise, which events they observe, what they verify and what still requires issuer information.

**Tokenization puts financial activity onchain. Useful infrastructure turns that activity into information people can trust.**

[Explore Shredo’s data products →](https://console.shredo.xyz/#/products)