One batch, start to finish
Work through the numbers
"Filled, 2.1 SOL in, 61% crossed off-curve." That row is mine until 14:02:15 UTC tomorrow. Then anyone can check it.

of that fill crossed a seller at spot and never touched the curve
Output
pump.funthe curve the net trade hits
Solscanevery net trade, linkedHelius Privacy Ringsprivate transfers and payoutsDefault Ringasset and amount encrypted
Solflareopens your Ring keyMeasured against sending the same order straight to the pump.fun curve.
Computed in your browser with the clearing code the engine runs, on a coin fresh on the pump.fun curve (30 SOL and 1,073,000,000 tokens of virtual reserves), before curve fees.
ORDER: ENCRYPTEDBuy or sell any pump.fun coin from your Ring. The limit and expiry ride inside the transfer, so a limit can wait for its price without anyone seeing it.
Send a dark order
Every fill goes back by private multi-transfer, amounts encrypted. Your row shows the crossed share, the price and the fee.
How fills are priced
{
"fills": 9,
"crossed_sol": "4.82",
"net": {
"side": "buy",
"sol": "0.80",
"tx": "5uQx…9fLe"
},
"check": "fills = crossed + net"
}The engine publishes each payout's viewing key a day later. Your browser decrypts every fill and checks the batch adds up.
Open the batches
pump.fun
SolscanCoin and size. Encrypted in the Ring transfer. A wallet that sends an order shows it sent something to the engine, not which coin or how much.
Side, limit and expiry. 54 bytes in the memo of the engine's UTXO, encrypted to the engine's viewing key, so only the engine can read them.
Your Ring address. Public, as on every Default Ring transfer. Sender and recipient are visible; asset and amount are not.
The net trade. One public pump.fun trade per coin per window, from the engine. It carries the difference, never the orders behind it.
Fills. Paid into your Ring with amounts encrypted, 15 per proof. The viewing keys are published 24 hours later for anyone to check.
The engine operator. Decrypts every order to cross it, so it sees each order during the window. After 24 hours every fill is public by key.
One engine key receives orders, crosses them, sends the net trade and pays the fills. A keeper key claims the fees, burns, pays holders and refills the gas tank. No program of ours sits between you and the curve: the engine composes a Ring withdraw, the pump.fun trade and a deposit back into its Ring in one transaction.
How a batch worksper window, aligned to UTC, one batch per coin
distinct Rings at least, or the coin's orders wait
until a batch's viewing keys are published and every fill can be checked
Close of the current 15-second window, 15 s from now
The engine opens once its Ring key is funded and its prover access is set. Every batch it clears will be listed here from its on-chain record.

"Filled, 2.1 SOL in, 61% crossed off-curve." That row is mine until 14:02:15 UTC tomorrow. Then anyone can check it.

of that fill crossed a seller at spot and never touched the curve
It runs a batch auction for pump.fun coins. Orders arrive as private Ring transfers to the engine. Every 15 seconds, for each coin with orders, the engine crosses buyers against sellers at the curve's spot price and sends only the difference to the curve as one trade. Fills go back into each trader's Ring with amounts encrypted.
That your wallet sent something to the engine's Ring, and when. Not the coin, the side, the size or the limit. On the curve they see one trade per coin per window from the engine. After 24 hours the engine publishes the viewing keys of each batch's payouts, and from then on every fill is readable next to its recipient address.
The engine operator. The engine has to decrypt an order to cross it. You trust the engine with that window, which is why every batch is published for audit 24 hours later.
A batch with one or two Rings would show their orders by subtraction. Below three distinct Rings, a coin's orders wait for the next window, up to their expiry. Orders that reach expiry are refunded privately into the same Ring.
0.5% of each fill's SOL value. 40% of that buys and burns $DRING, 40% is paid to $DRING holders in hSOL every Monday at 00:00 UTC, and 20% stays in the gas tank that pays for order, refund and payout proofs.
Yes. An agent opens a Ring with its own Ed25519 key and posts orders over the HTTP API or the MCP tool. The order is the same 54 bytes a person sends from the order ticket.
Open your Ring with the wallet you already use. The order ticket quotes the curve and builds your order in the browser.
Open app