The ladder, walked
Each requirement is a binary question answerable from public state. An unknown blocks the stage exactly as a failure does — but it is shown differently, because they are different facts.
Stage 0 — The gate is observable. not reached
Stage 1 — Credential substance is checked and the terms are stated. not reached
Stage 2 — Refusals are durable and exit is proven. not reached
Conformance detail
4 passed · 9 failed · 14 not observable · 0 not applicable. Verdict NON_CONFORMANT.
Failing vectors:
- IFACE-IDENTITY-REGISTRY
- IFACE-COMPLIANCE
- IFACE-PAUSED
- IFACE-IS-FROZEN
- IFACE-FROZEN-TOKENS
- IFACE-ONCHAINID
- IFACE-VERSION
- IFACE-OWNER
- IFACE-IS-AGENT
What else runs this code
This contract runs implementation 1dca316569dd175e (direct, 1,995 bytes). 9 other tokens on Base Sepolia run byte-for-byte the same code. Whatever this page says about the code, it says about all of them — so treat these as one piece of evidence, not 10.
The record an issuer can hand upward
The table answers a reader's question. This answers a supervisor's: a dated, content-addressed record of exactly what was checked, what the answer was, and what could not be checked and why — stated in the same voice as the findings, because a gap an auditor has to discover is a gap that was hidden.
It carries the sha256 of its own findings, so an edited copy stops matching. It names the block and the RPC, so it can be re-run rather than believed. And every vector in it carries the grade of the check that produced it — nobody is asked to weigh a verdict without knowing whether that check has ever been able to fail.
Download the audit record (JSON)
Re-run this yourself
The exact endpoint this measurement was taken from, so the command runs as written rather than needing a value filled in.
python conformance/conform.py \ --token 0x090e7c1dccaa7a9eb624b374ce0113d1dcf83412 \ --rpc https://base-sepolia-rpc.publicnode.com