Docs
Block is a dark pool for large memecoin trades on Solana. You seal an order, an attested engine matches it with an order on the other side, and both legs settle in one transaction, without touching the pool. The chart does not see the trade.
How it works
- Seal. You choose side, size and a limit relative to the pool price, for example "not below pool -5%". Your wallet encrypts size and limit to the engine's key and deposits the tokens (to sell) or SOL (to buy) into a new order account owned by the Block program.
- Match. The engine, running inside an Intel TDX enclave, reads the sealed orders. Nobody else can: not the team, not validators, not the RPC. It pairs buyers and sellers whose limits both contain the current price.
- Settle. The engine signs the match. The program checks the signature against the attested key and moves both legs atomically: tokens to the buyer, SOL to the seller, the fee to the protocol. Either everything moves or nothing does.
- Rest. Whatever did not match stays sealed. You can cancel it at any time, or send it to the pool yourself, at the pool's price.
The price
A match fills at the pool's average price over the last few minutes (time-weighted), and only if that price is inside the limits of both orders. Block never invents a price; it borrows the pool's recent one, so a single block of trading cannot set it.
Because the trade settles between the two order accounts and never goes through the pool, the pool price does not move and there is nothing on the curve to front-run.
Where the money is
- Every order has its own account, owned by the program. There is no shared vault.
- Only your signature can cancel an order; cancel returns the deposit to your wallet in the same transaction.
- Only a match signed by the attested engine key can settle an order, and only inside its limit.
- Settlement is atomic. A partial fill moves exactly the filled part; the rest stays in your order account.
The engine and attestation
The engine runs in an Intel TDX confidential VM. Its signing key is generated inside the enclave and bound to a measurement, a hash of the firmware, kernel and engine binary. The program stores that measurement and accepts match signatures only from the key it vouches for.
Check it yourself
- Build the engine from the public source with the reproducible build. You get a hash.
- Fetch the enclave's attestation quote, signed by Intel, and read the measurement in it.
- Compare them. Same hash: the enclave runs the code you read. The home page shows this check as a demo.
Parameters
| Fee | 0.3% of the filled value, paid by each side. Only when an order fills. |
|---|---|
| Price | Pool time-weighted average over the last few minutes, inside both limits. |
| Limit | Relative to the pool: sells set a floor (e.g. pool -5%), buys set a cap (e.g. pool +3%). |
| Cancel | Any time before a match, by the order owner only. |
| Unmatched rest | Stays sealed, can be cancelled, or sent to the pool by its owner. |
| Who can read orders | Only the attested engine. Orders are encrypted to its key in your wallet. |
Risks, plainly
- No counterparty, no fill. A dark pool only works when the other side shows up. A large order may wait or fill partly.
- Deposits are public. The chain shows that an order account holds a deposit. Size and limit are sealed, but the deposit tells the world something; deposit more than you want to trade if that matters.
- Average price is not a good price. Attestation proves which code runs, not that a fill is good for you. Your limit is the guard: set it.
- Hardware trust. TDX enclaves rely on Intel and have had attacks in the past. If the enclave were broken, sealed orders could be read; funds still move only by your cancel or a match inside your limit.
- Liveness. If the engine is down, nothing matches. Cancelling does not need the engine.
- Smart contract risk. The program can have bugs. It will be audited before mainnet; that lowers the risk, it does not remove it.
What is live
This site shows how Block works. The book, the ticket and the verification on the home page are demos that run in your browser on simulated orders. The program, the engine and the live attestation come next; the CA is posted on the home page at launch.