21 NAND Docs 中文

Check it yourself

You don't have to trust us: recompute the website files, circuits and models on chain with your own commands. The first four you can do right now.

What you need

1. A file matches the fingerprint recorded on chain

What it checks: any file on this site. Against what: the sha256 recorded on chain for each file.

Read the size and sha256 recorded on chain
cast call 0xd006ffdd5ae313b17729621a00999cd3c71ce5e6 \
  "fileInfo(address,string)(uint32,string,bytes32,uint40,uint256)" \
  0x39d97ab281f04a5bc3aCc562f8DeA3f0b4266aA3 home.css \
  --rpc-url https://bsc-rpc.publicnode.com
Download the same file and compute it yourself (on macOS use shasum -a 256)
curl -s https://282-732.aihashrate.stream/home.css | sha256sum

2. Run a circuit on chain

What it checks: the result circuit #279, "21 gates that drive", gives on chain. Needs Foundry's cast.

Call circuit #279 on the TapeOut CPU
cast call 0x6Fb4089e7Cbaa9660Fd11056274Cbd8117EE5B38 \
  "eval(uint256,bytes)(bytes)" 279 0xff7f \
  --rpc-url https://bsc-rpc.publicnode.com

A read-only call, free of charge. For contract addresses see Contract addresses.

3. Check in your browser

4. Check the Bard's design files without a gateway

See "Method three" in Fetch the design files from the chain: use cast to read, straight from X Layer, the sha256 recorded for the two file parts.

5. Check everything at once with tapemule (once the repository is public)

The repository of the tapemule command-line tool is not public yet, so these two checks can only be run once it is. Its advantage is that it checks everything in one go: readings are pinned to a finalized block, and a result only counts when at least 2 independent nodes agree.
Get the command-line tool (once the repository is public)
git clone https://github.com/BruceLanLan/tapemule.git
cd tapemule
npm ci

The Hub contracts are the pinned implementation

What it checks: the Hub contracts on three chains. Against what: the code on chain and the implementation address match the ones pinned in tapemule.

Check the Hub on BNB Chain
npm run tape -- hub bnb
Check the other two chains
npm run tape -- hub base && npm run tape -- hub xlayer

Every file of a site

What it checks: the container, holder and activation status of a .tape site, and the bytes of every file. Against what: the sha256 recorded on chain for each file.

Check every file of 282.732.tape
npm run tape -- open 282.732.tape --files

Where you have to trust someone else

Check 1 compares the file you downloaded with the sha256 recorded on chain. The record itself depends on a contract, so here is who controls it.

Read at a block number (get the latest block first, use the same one on both nodes)
B=$(cast block-number --rpc-url https://bsc-rpc.publicnode.com)
cast call 0xd006ffdd5ae313b17729621a00999cd3c71ce5e6 \
  "fileInfo(address,string)(uint32,string,bytes32,uint40,uint256)" \
  0x39d97ab281f04a5bc3aCc562f8DeA3f0b4266aA3 home.css \
  --block $B --rpc-url https://bsc-dataseed.bnbchain.org

The market contract used for buying and selling circuits is a different contract. It can also be upgraded; the right to upgrade sits with a wallet shared by several keys, where 3 of 5 keys must sign (read-only check, 2026-11-12).

Checks whose scripts are not public yet

The scripts for these checks are not public yet. Below we only say what each checks, against what, and what you see when it passes.
What it checksAgainst whatWhen it passes
TapeBoot test vectors for canonical form, signing and fetching (C version)A fixed set of test vectors, no private keysAll pass, 0 failures
The same vectors (TS reference client)Same as above14 pass
Netlists of 11 circuits on chainA three-way sha256 comparison: the one stored on chain, the one in the burn transaction, and the copy we keepOne "match" line per circuit, exit code 0

The third check covers these circuits: 279.732 to 287.732 and 290.732 on BNB Chain, and 3.2.245 on X Layer. Changing a single byte makes it report a mismatch, exit code 1.