BLOCKFollow

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

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Example from the home page model: a constant-product pool holds 25.6% of the supply. Selling 5% of the supply into it prints a -30% candle and fills at -16.3% on average. The same 5% matched in Block fills at the pool average, less the 0.3% fee, and the chart stays where it was. This assumes a buyer of that size is sealed in the book.

Where the money is

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

  1. Build the engine from the public source with the reproducible build. You get a hash.
  2. Fetch the enclave's attestation quote, signed by Intel, and read the measurement in it.
  3. Compare them. Same hash: the enclave runs the code you read. The home page shows this check as a demo.

Parameters

Fee0.3% of the filled value, paid by each side. Only when an order fills.
PricePool time-weighted average over the last few minutes, inside both limits.
LimitRelative to the pool: sells set a floor (e.g. pool -5%), buys set a cap (e.g. pool +3%).
CancelAny time before a match, by the order owner only.
Unmatched restStays sealed, can be cancelled, or sent to the pool by its owner.
Who can read ordersOnly the attested engine. Orders are encrypted to its key in your wallet.

Risks, plainly

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.