Robinhood Chain · free while in testnet

A receipt for
every byte.

Your releases, your files, your model outputs: a receipt anyone can check on-chain, instead of a badge you have to trust.

Your cursor is the verifier. Every byte it passes gets hashed; the one it lands on lights up.

01 · The problem

Old code, new exploits.

The worst breaches hit code everyone already trusted. Reviewed many times over, and still carrying a flaw for years. Age and reputation are not evidence. A check you can repeat at every release is.

Release · trusted
Years on · exploited

8 bytes nobody questioned · exploited after years in production

Shellshock · Bash

A command-injection flaw sat in Bash for about 25 years; mass scanning began within hours of disclosure.

Heartbleed · OpenSSL

A missing bounds check in the main TLS library leaked server memory, private keys included, for two years.

Log4Shell · Log4j

A lookup feature added in 2013 let a single log line run remote code, in software nearly every Java team ran.

xz · liblzma

A backdoor reached release tarballs that did not match the public source. Nobody compared the bytes.

regreSSHion · OpenSSH

A bug fixed in 2006 came back in a 2020 release and opened unauthenticated root code execution.

Ronin · bridge

Five of nine validator keys were enough to sign withdrawals; about $600M left before anyone noticed.

02 · Commit

Lock the inputs before anyone sees the answer.

The release, the files, the spec, the model id. Hashed into one commitment and written on-chain first. From here nothing can quietly change.

Files
src/Vault.sol · foundry.toml
Spec
audit-v1
Model
claude-opus-5-5 · temperature 0
Commitment
…

keccak256 of the lines above, computed live in your browser. Then commit() on Robinhood Chain.

03 · Lock the seed

Tie the dice to a block nobody has seen yet.

The seed comes from the commitment and a block five blocks in the future. Neither you nor we can re-run until the answer is the one we want. One seal per commit. No re-rolls.

Chain
Robinhood Chain
Latest block
…
Target
…
Seed
H(commitment ‖ blockhash(target))

The contract refuses a seal before the target block and after 256 blocks. Read it live, the numbers above are real.

04 · Run and record

Record the answer, byte for byte.

Your tool, your CI job or your model runs off-chain. Its output is hashed and sealed against the commit. We do not claim the run itself is re-executable today; we prove the output was fixed after the inputs and the seed, and never changed.

{
  "summary": "One high-severity issue, two lower.",
  "findings": [
    { "severity": "high", "title": "Withdraw lacks owner check",
      "file": "src/Vault.sol", "line": 142 },
    { "severity": "medium", "title": "Unchecked fee multiplication",
      "file": "src/Vault.sol", "line": 96 }
  ]
}
Output hash
…
05 · Receipt

Sign it into a log nothing leaves.

Every stub is a transaction signed by its issuer, stored in a contract with no owner, no upgrade and no delete. The chain is the log: anyone can replay it from the first block.

Stubs contract · append-only
#0 stamp#1 commit#1 seal#2 stamp…
issuer = tx signerno ownerno admin key

Contract: not deployed yet

06 · Verify

Check it yourself. In your browser.

Every check runs against the public RPC. Nothing taken on trust from our server.

What a receipt proves

The inputs were committed before the seed existed; the output was recorded once and never changed; the issuer signed it.

What it does not prove

That the code is safe. A receipt proves the work ran as stated, not that it is correct.

    Scan something.

    A token contract on Robinhood Chain. No wallet, no account.