deed inspector

Paste the deed
you're debugging. See exactly what failed.

Every stage stays visible, including the ones that passed, so a lapsed tenant behind a perfectly good signature reads as exactly that, not as one flat rejection. There's nothing to look up by address — your authority lives in the deed you're holding, so paste it and this page takes it apart, live.

Nothing here leaves this page

Your deed never leaves this page. Verification is local wasm; the only network traffic is public-registry reads that carry no deed data — open devtools and watch. Nothing stored, nothing logged, no analytics.

Loading config…

Chain Chain id RPC URL Registry address

Deed (paste the raw JSON your holder presented)

Challenge

Policy

Discovery document (optional — paste it, and matching fields below pre-fill)

curl "https://your-rp.example/.well-known/grantor-deed"

Tenant Audience Origin (what THIS checker is — never taken from the deed) Max TTL (seconds)

RPs configure this ceiling; a deed rejected as Expired at mint-plausible times may just exceed YOUR ceiling — raise it to match your RP's.

Verify as of

now (the real clock) the deed's own window (just before it expired)

Not an error

See the capabilities guide →

Denied —

See this code in the errors guide →

Live public facts, read straight off the registry contract — status, tenants, and (with a cohort label) delegationEpoch.

Tenant id Cohort label (optional, bytes32 hex)

What this tab can't show you

No member lists — the chain holds commitments, and membership is only ever proven in zero knowledge.

No tenant→domain mapping — deliberately never published, so nobody can enumerate who uses Grantor.

What this tab shows is everything there is to see.

No analytics on any of this — the chain and npm are the only metrics, as everywhere on this site. See a code you don't recognize? The errors guide has the full reference table.