Sounder Liquidity

$SOUNDER is live on Solana.

CA: DBhWAqpAJFNM1A9XY6DDb1SJVkNCv87hRdYCoCoypump

Same team, same tool, now on a chain with a market. The engine follows once the rewrite is scoped.

Thank you for coming with us.

New: Raydium, read.

Two more pool layouts on Solana are now read from account state and matched to Jupiter to the unit. Three venues on the board: PumpSwap, Raydium’s classic AMM and Raydium’s CPMM. Where a mint has more than one pool, the venue that pays most is named at every size.

Each layout keeps its reserve differently, and each had to be learned from the chain. The classic pool holds part of it in an OpenBook open-orders account and owes part of its vault as accrued PnL, so the curve runs on vault + open orders − PnL owed. The CPMM keeps protocol and fund fees inside the vaults, so those come off, and takes its fee from a shared config account in parts per million.

WIF on Raydium v4: 0.00 bps against Jupiter at 0.1, 1, 5 and 25 SOL. USELESS on the CPMM: 0.00 bps. A venue is marked read only when it matches to the unit on live pools. Orca, Raydium CLMM and Meteora stay listed as unread until their tick walks are built.

sounderliq.app/solana

Up next on Solana. Step one is live; this is what is on the bench.

Now: finishing the reading. Raydium’s classic and CPMM pools, two more constant-product layouts read from their vaults. Then the concentrated pools: Orca Whirlpools, Raydium CLMM, Meteora DLMM, with tick arrays and bins walked exactly, the way v3 and v4 are walked on Robinhood Chain. The rule for each venue is the same: it is marked read only when our number matches Jupiter’s for the same pool within a basis point, at every size, across live pools.

Then: the scoreboard. The identical order through Jupiter and through us, simulated on chain, every hour, kept whichever way it goes. On Robinhood Chain that honesty cost us 6,480 published losses. It also told us exactly what to build.

After: the executor as a Solana program, then the audit on that code, then the app and the SDK.

Order, not dates. sounderliq.app/solana

Roadmap, step one: done. The reading is live on Solana.

sounderliq.app/solana sounds any mint from account state. The pool’s vaults, the virtual quote reserve the curve actually prices off, and the fee tier chosen by market cap are read from the chain, and your size is pushed through the curve for the fill at 0.1, 1, 5 and 25 SOL.

What the chain taught us on day one: the curve does not price off the vault. SOUNDER’s pool holds 6 SOL and the curve counts 24. Miss that and every reading is four times wrong. We did not miss it: beside every rung sits Jupiter’s quote for the same pool and size, and on SOUNDER the difference is 0.00 bps at every size.

PumpSwap first. Raydium and the concentrated pools are listed on the page as unread until they are read. Then the scoreboard against Jupiter. Order, not dates.

DBhWAqpAJFNM1A9XY6DDb1SJVkNCv87hRdYCoCoypump

Finally here: the roadmap. In order.

Shipped, on Robinhood Chain: the reading of every pool from storage, the executor with the floor enforced on chain, limit orders, an hourly scoreboard against every other router, an API, an SDK, an MCP server, an Android build, signed readings, and the audit scoped and budgeted in public.

Now: $SOUNDER is live on Solana. The CA is on the site, the Robinhood holders are snapshotted, and the Robinhood deployment stays up and readable.

Next, in order, on Solana:

1. The reading. Every pool from account state.
2. The scoreboard. The same orders through Jupiter and through us, both on chain, kept whichever way it goes.
3. The executor as a Solana program, then the audit on that code.
4. The app and the SDK, same instrument.

Not on the list: custody, a pause switch, an admin key, or a date we cannot keep. Each step ships when it is measured.