Verify formats locally
TapeID is not deployed. These tools check supplied data; they do not prove a live name, card, record or anchor.
What can be checked
# Open the browser verifier for synthetic or supplied records https://tapeid.xyz/verify # Run the local verification test path when dependencies are available pnpm verify:local # Run the ERC-8412 draft conformance vectors (23 supplied cases) pnpm verify:vectors # A future registry may expose this read shape; no address is supplied today cast call <registry> 'owner(bytes32)(address)' <node> --rpc-url <rpc> # A future card may use this text-record key tapeid.card
A merkle root can be recomputed from records and compared with supplied anchor data. That proves internal consistency only. TapeID currently has no anchor transaction.
Checking TapeOut-shaped evidence
The design distinguishes a circuit's execution result from the evidence about its author and delivery. A future checker would first obtain the circuit and task data from their authoritative sources, then bind those exact observations into a TapeID criteria, bundle and attestation package. The following illustrates the public read shapes; it is not a configured TapeOut integration and has no working TapeOut address or RPC supplied here.
# Against the particular TapeOut deployment being examined cast call <processor> 'netlist(uint256)(bytes)' <circuit-id> --rpc-url <rpc> cast call <processor> 'eval(uint256,bytes)(bytes)' <circuit-id> <inputs> --rpc-url <rpc> # Save the exact returned bytes and the input/output observations. # Compute their commitments, then verify the assembled local package: node packages/verify/dist/cli.js case.json # Check a supplied 128-byte anchor payload against a records array: node packages/verify/dist/cli.js \ --anchor-data <tag-root-count-timestamp> --records batch.json
Re-running eval can check execution for the supplied circuit and inputs. It does not establish circuit ownership, name control, evidence completeness or the honesty of the verifier. The current local verifier checks the record documents and their decision rule; it does not fetch or execute TapeOut circuits. See the record mapping and the sourced protocol details.
Current limits
| Area | Status |
|---|---|
| Deployment | None; registry and gateway are unconfigured in the fallback. |
| TapeOut | No integration. TapeOut is a separate circuit execution and acceptance protocol; the record format is designed to carry that kind of work — see the mapping. |
| Names and cards | Local interfaces only; zero issued or published by TapeID. |
| Records and anchors | Zero; examples are not production history. |
| Sales and sponsorship | No live sale, free-name offer or gas sponsorship. |
Not true yet
| Claim we do not make | Why |
|---|---|
| “Independently verified.” | No independent production verifier is deployed. |
| “Records cannot be altered.” | No TapeID record contract or anchor exists. |
| “Audited.” | No external audit is claimed. |
Current counts are published at /numbers, including the zeroes.