State
What is real here, part by part
Printed per part rather than as one disclaimer at the bottom. "Nothing here is deployed" tells a reader nothing about which half to trust.
| Part | State | What that means |
|---|---|---|
| census | measured | every figure is counted from Approval logs read off Robinhood Chain, with no vendor and no key |
| breach | executed | each exposure is proved by running the spender’s own transferFrom in eth_call — a simulation that moves nothing |
| contract | executed | compiled and run on Robinhood Chain through an eth_call state override, every build |
| properties | executed | each property is an on-chain call whose result is checked, and each sabotage must be caught |
| app | live | deploys and transacts from your own wallet on Robinhood Chain mainnet |
| deployment | none | no canonical Postern vault is deployed — deploying costs gas from a wallet and this repository holds no key |
| audit | none | not audited by anybody; the sabotage suite is a self-review and says so |
| trace | computed | the hero is a visibility solve over a bastioned trace, held to its own geometry at build time |
Provenance
Where each number came from
| Source | Read at | Cost |
|---|---|---|
| Approval census | block 56,794,300 | 1,916 calls, 380s, 167 throttles |
| Property run | block 56,798,152 | 24 + 13×24 executions |
| Geometry solve | build time | 23,404 sampled points, 26 traces, 24 stand-down orders |
No API key, no proxy and no vendor. The public Robinhood Chain node answers the browser preflight with access-control-allow-origin: *, which is why the breach page and the app are pages rather than serverless functions. Its rate limiter answers a burst with a header a browser cannot read, so a throttle arrives in a page looking exactly like an unplugged cable — every page here says so rather than implying the chain is broken.