Reading the chain
Contract
Every number on this site comes from contracts other people deployed, read straight from their storage. We have shipped no code to chain 4663, so there is no address of ours to verify and none is claimed.
not read yet — the largest known gap
0x8366a39cc670b4001a1121b8f6a443a643e40951The only contract Almight intends to deploy. It does no routing, promises no speed, and saves nobody from a bad market. It checks one condition nobody else checks, and reverts.
You pass a ticker, a size and a tolerance in basis points. The contract reads the attested reference, computes the basis at the moment of execution, and refuses the trade if it falls outside. A reference older than your own limit is not interpolated and not guessed — it reverts too.
// don't let me buy NVDA at 150 bps over the stock hallmark.buy({ token: NVDA, spend: 5_000 USDG, maxBasis: 150, // bps vs reference maxRefAge: 90 // seconds }); // 01:47 ET, market closed, reference 4h old revert StaleReference(14_820s > 90s)
A guard is only as good as the reference behind it. Today that reference is fetched at render time and labelled with its age — good enough to publish a number, not good enough to enforce one with somebody else’s money. The attestation has to be signed and posted on chain first. Shipping the contract before that would be selling a promise the plumbing cannot keep.
The chain leg is reproducible. Point any RPC for chain 4663 at the block named on the board, call slot0() on the pools listed under a ticker, square the sqrtPriceX96, and you get the mids this site publishes. If you get something else, this site is wrong.