Tokenized-stock analytics · Solana
Start with the stock.
Then inspect the wrapper.
The same ticker can give you a different legal claim, different issuer powers and different ways out. Start simple, then open the evidence only when you need it.
Showing the bundled sample fixture
(stocks/fixtures/stocks-issuers.sample.json and stocks-tokens.sample.json), not live data. Three issuers and twelve token addresses, for layout
work only. Do not cite any number on this page while this banner is visible.
Your private briefing
Continue where you left off
Saved locally in this browser by default. No account, profile or tracking cookie.
Saved stocks
Saved issuers
Saved comparisons
Recent additions
catalogueProtocol support changes
exact-token listingsChoose a starting point
What do you want to understand?
Find any stock, token or issuer
Search by company, ticker, token symbol, issuer programme, protocol or exact Solana token address. Results explain why they matched.
New on Solana
Token addresses this pipeline first saw in the last 14 days. “First seen” is when Jupiter first returned the address to us, not necessarily when the token was created.
Show every recent addition
Funnel chart: token addresses → issuers → control recipesOpen the complete catalogue map
Every token address we can find on Solana, read left to right: what it tracks, which issuer programme created it, which control recipe that programme runs on it (the token program plus the extensions that are switched on), and which token program holds it. A circle's area is its number of token addresses (with a floor, so a one-token programme is still a dot); a line's thickness is how many tokens take that step. A hollow circle is a programme with no live tokens. Click an issuer circle for its dossier.
Many token addresses come from a few issuers, one token program and a handful of recipes, so most tokens are technically alike. A recipe lists what the issuer can technically do to a token: pause it, claw it back, limit it to an allowlist or charge a transfer fee. It says nothing about what the holder owns. That is the horizontal axis in the next section.
Is the token the official record, and how close is it to the share?
Up the side, how far the token is the official record (Level 4 top → Level 0 bottom): each step adds one thing. The blockchain is the official record of who owns it; then the token moves without anyone’s approval; then holding it is enough to redeem, without the issuer; then a theft or court order can be corrected on the ledger.
Across, how close you are to owning the share (0 left → 4 right): what the holder legally owns: price exposure only, an unsecured claim on the issuer, a claim secured over collateral, a beneficial interest in shares held for holders, or the registered share itself.
Each dot is one issuer programme, sized by the log of its total Solana DEX liquidity (floored, so an illiquid programme is still visible). Click a dot for the dossier. The bottom-right corner is a real registered share that barely trades on chain. The middle is a freely transferable wrapper that gives no claim on the share itself. The two scores measure different things and are not added together.
Trading diagnostics, last 24 hoursOpen volume quality, traders, venues and spread
One row per live programme, aggregated over its token addresses. This is the counterpart to the liquidity numbers above: liquidity is how much depth sits in the pools, and these columns are how much actually traded against it. Defunct programmes are not listed. Click a programme to open its dossier, or a column header to sort.
| Programme | Traded 24h / tokens | Trades 24h | Traders 24h | Trades / trader | Organic | Venues | Venue spread | Last trade | Flags |
|---|
What this is: trades, traders and organic share are Jupiter's 24-hour aggregates per token address; venues, the last-trade time and the cross-venue price spread come from DexScreener pairs and CoinGecko tickers. Not collected: per-trade on-chain history, counterparty or wallet-level analysis, CEX order-book depth, and exact trade timestamps on DEXs. So a DEX-only token has trades but no last-trade time, and trader counts are per-token sums in which one wallet can appear twice.
No activity aggregate in this build yet, so most cells
read —. Re-run npm run stocks:venues && npm run stocks:build to fill them.
Issuer programmes (…)
One card per programme. We analyse the programme as a unit: one wrapper, one document set and one set of issuer controls, issued as one or many token addresses. Live programmes come first, ordered by on-chain liquidity. Defunct ones are greyed out and left out of every headline total. Issuer controls are listed as facts and never summed into a score.
Understand the wrappers
Choose an underlying
Choose wrappers and requirements
Published claims vs observed evidence
Where the public description and the stronger evidence diverge
These are open or resolved conflicts between what an issuer or protocol publishes and what its documents, code or chain show. Corrections to RWA Sonar’s own research are kept elsewhere. Both sides are shown with their own sources. A discrepancy stays open until the issuer’s records, governing documents, code or observed state are reconciled.
What can you actually do with these tokens today?
This section counts observed use only. What could work in theory is further down. An asset is counted only when its exact token address appears in a live protocol registry or pool, or an asset-specific live product names it. Generic Token-2022 support and issuer ecosystem logos do not count.
Why protocol custody may not equal enforceable collateral →
Browse shareable exact-token protocol and market dossiers →
Watched daily
New in DeFi
When a protocol adds or drops one of these exact tokens, in its own registry or by holding it on-chain, it appears here. A program we cannot yet attribute is shown as under review until we identify it.
Start with the protocol
Where these tokens are usable now
Each protocol card counts exact Solana token addresses found in the checked live registry, pool or product. Choose an action to answer “where can I do this?” before drilling into an asset.
The Protocol support column in the token-address table lists the protocols and actions for each asset. Open Details for market size, LTV, access restrictions and links to the product and evidence. A listing in a protocol’s own registry shows the protocol supports the exact token. It does not show that any user action succeeded. “Not listed” means we found no listing; the token may still be used somewhere we do not check.
What could work in theory?Open the technical and legal composability analysis
A token being transferable does not mean a smart-contract lender can safely use it. Each row combines one issuer's legal structure with one on-chain control recipe and asks four different questions: can a protocol hold it, can the lender enforce a borrower default, what can happen after a hack, and what happens when a contract or key becomes inaccessible? Recovery powers cut both ways: they can return stolen tokens to a victim, and they also let the issuer move tokens out of a protocol's custody.
This table measures what is technically and legally possible. It does not show that any lending protocol lists or accepts the token.
| Tech + legal template | Tokens | Verdict | Smart-contract escrow | Borrower default | Protocol hacked | Access / key loss |
|---|
Raw token catalogueOpen the paginated table of every exact Solana token address
Every token address
All exact token addresses found in the universe fetch, loaded from the API 50 at a time, including paused tokens and tokens with no pool. A premium on an illiquid token means little: below roughly $50k of liquidity the on-chain price is a stale AMM print. Reference prices come from three unrelated places and the column names which one. An issuer mark is the sponsor's own number and is not independent. Click a row, or its Details button, for the token's full panel: identity and on-chain control, market, trading activity, every venue it trades on, and the reference price.
0 tokens
On a small screen, choose a column preset and scroll the table sideways. Every row also has a Details button with the complete record.
| Token | Issuer | Underlying | Instrument | Price | Reference | Premium | Liquidity | Vol 24h | Organic | Trades 24h | Traders 24h | Venue spread | Holders | Top-10 | Last trade | Protocol support | Flags | Detail |
|---|
How to read RWA SonarMethodology, definitions and known gaps
Where the data comes from
- Legal facts: hand-researched per issuer from primary documents only (prospectuses, issuer terms and conditions, transfer-agent and regulator records), each with its source URL in the issuer's detail panel. A dossier carries its own confidence rating.
- The token-address universe: Jupiter token search, read in full on the date shown at the top of this page.
- On-chain control: the Solana RPC, read directly off each token address's Token-2022 extensions.
- Reference prices: Pyth where the feed is entitled, an implied price derived from the Ondo registry, or the sponsor's own published mark. The table always names which.
What a grade means
Ledger maturity is the site-wide 0–4 level, computed identically to the main assets table: Level 0 unless the chain is the main ledger, then Level 1 unless transfers are unconditional, Level 2 unless redemption is bearer, Level 3 unless a forced-transfer mechanism exists, else Level 4. The score beside it sums ten booleans, +1 for yes and −1 for no.
Claim depth is a 0–4 level read off the legal form: synthetic exposure, unsecured claim, claim secured over collateral, beneficial interest, registered share.
Verification strength replaces a yes/no on third-party attestations with a 0–5 scale: none, issuer statement, periodic auditor attestation, daily verification agent, on-chain proof of reserve, transfer-agent register.
Attestations are positive statements by a named attestor. Findings are negative or neutral facts we observed ourselves, with the evidence attached. No one attests to those.
Known gaps
- The universe is a union of searches. No authoritative listing exists. There is no working "all tokenized stocks" call, so the fetch fires many queries by issuer and ticker name. An issuer absent from that query list is invisible here.
- The forced-transfer pillar grades whether the power exists. It does not grade the process around it. A permanent delegate exists on roughly half the tokens, mostly held by single keys with no published procedure; whether it is bound to a legal process is tracked separately and does not yet move the level.
- Reference prices are thin. Most tickers have no entitled Pyth feed, so the premium often rests on a quotient derived from an issuer's own registry. That is good enough to spot a 20% gap and too rough to use as a quote.
- Transfer hooks are reserved but empty. Almost every token reserves the hook slot and none has a hook program installed, so nothing is enforced on chain today. The authority to install one later is kept.
- Token symbols can differ from tickers. Some issuers truncate their symbols, so joining a token to a real listed ticker needs a lookup table this pipeline does not have. Private companies have no ticker at all.
- Every field can be absent. A dash means the source does not say, and is never rendered as zero. Missing values are skipped in aggregates.
Glossary: what the market terms mean here
- Liquidity
- The USD value of the reserves sitting in the token's DEX pools (Jupiter's aggregate over Raydium, Orca and Meteora). It measures depth that can absorb a trade. It does not count trades. A centralised exchange never reports it, so a token that trades mostly on a CEX can show heavy volume and almost no liquidity.
- Volume 24h
- USD traded in the last 24 hours, across all Jupiter routes.
- Organic volume and organic share
- The part of that volume Jupiter classifies as non-bot flow, and organic divided by total. A low organic share means the volume is there but almost none of it looks like real demand.
- Trades 24h
- The number of buys plus sells. Volume is their USD size.
- Traders 24h
- Distinct trading wallets. Summed per token address, so in a programme's row one wallet that traded two of its tokens is counted twice.
- Trades per trader
- Trades divided by traders. A high value points to wash trading: a handful of wallets producing thousands of trades. Above 25 the row is flagged.
- Holders
- Token accounts with a balance, as reported by Jupiter. One person can own many accounts.
- Top-10 %
- The share of supply held in the ten largest accounts.
- Venues
- Distinct DEX ids (from DexScreener pairs) plus exchange markets (from CoinGecko tickers) where the token has a pair.
- Venue spread
- The gap between the lowest and highest price for the same token across venues that traded in the last two hours with real depth (DEX pools ≥ $10k liquidity, exchange markets ≥ $5k 24 h volume); a persistent gap is an arbitrage opportunity, a one-off gap is usually a stale quote.
- Last trade
- The most recent
last_traded_atacross a token's CoinGecko tickers. It is a per-venue timestamp. Shown as a relative age, with the exact time on hover. - Not collected
- Per-trade on-chain history; counterparty or wallet-level analysis; order-book depth on centralised exchanges; exact trade timestamps on DEXs. Nothing on this page can tell you who traded, or when a specific on-chain swap happened.