the register.

LW14685623

0x504a34499D967169bb1f16d52d3cd8CAE9AB3F80 · Base Sepolia · chain 84532

Stage
no stage
not a failure — the gate could not be observed
Conformance
4 / 13
9 failed · 14 never produced a verdict
Gate
Not observable
zero supply — nothing to move
Implementation
0x5a520e99
unique to this token
Identity registry
none
credential substance is unverifiable without one

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

?
Can a stranger observe this token's transfer gate reach a decision?
unknown — not observed
✓
Does the contract answer basic ERC-20 reads, proving it is live?
yes

Stage 1 — Credential substance is checked and the terms are stated. not reached

?
Is an address holding no credential actually refused?
unknown — not observed
✗
Is the credential checked for substance — KYC, expiry — not just existence?
no
?
Are the insolvency waterfall and price basis stated on-chain?
unknown — not observed

Stage 2 — Refusals are durable and exit is proven. not reached

?
Does a refusal survive its own transaction, with the rule named?
unknown — not observed
?
Can a holder exit — redeem, or transfer to a reachable counterparty?
unknown — not observed
?
Is the issuer unable to pause, freeze, seize or upgrade?
unknown — not observed
The gate could not be observed, so no grade is defensible. This is a statement about our access, not a failure by the token.

Conformance detail

4 passed · 9 failed · 14 not observable · 0 not applicable. Verdict NON_CONFORMANT.

Failing vectors:

Every vector cites the ERC-3643 clause it derives from, and carries its own grade for whether it can fail at all. See the ruler →

What else runs this code

This contract runs implementation 0x5a520e9992d30416c33e2dcdc2d8f3befce426da (erc1967-proxy (target unreadable), 122 bytes), and it is the only token here that does. Its result stands on its own.

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)

This is a record of transfer-control conformance. It is not an audit of the issuer, the asset, custody or reserves, and it is not a rating — the report says so itself, in its own limits section.

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 0x504a34499D967169bb1f16d52d3cd8CAE9AB3F80 \
  --rpc https://base-sepolia-rpc.publicnode.com