WritingDisabled
Written1 / 2000
Permanent0 / 2000
Block25,634,495

Contract state

Read at block 25,634,495 (2026-07-28 23:06:23 UTC).

NFT

address0x0000eC93127BAA929E58E97dd0095A2BFb38ec1D
nameidentity.md
symbolIDMD
totalSupply2000
MAX_SUPPLY2000
renderer0x3F559eF271B245E7e754fEAD7d50cd55aC981423
identityAllowedfalse
identityHash(id)"" for every id

Registry

address0x000008061ccac597a321a75e3470a3e8faf9dd2d
token0x0000eC93127BAA929E58E97dd0095A2BFb38ec1D
identityAllowedfalse
tokens with a hash1 / 2000
written as permanent0 / 2000

Identity events

The registry emits two events. Both topic hashes were confirmed against logs read from chain rather than derived from a guessed signature. Parameter names are not part of a topic0 preimage, so the names below are labels; the types and their positions are what were verified.

topic0signature
0x57c85cf86ae80c7b372281c7dd1b0f8b99de39e76d757725a32b6bd88f7ff1b6IdentityHashUpdated(uint256 indexed, string, bool)
0x5149bb8ac04701d1c7bef5aa11259c070730a951c3e615b60ea017b839aea132IdentityAllowedUpdated(bool)

The third parameter of IdentityHashUpdated is the only place a token's permanence flag is observable — no view function exposing it was identified on either contract. The Permanent count on this site is read from that parameter across the 1 decoded IdentityHashUpdated record, of which 0 carry true.

Method: identityHash was sampled across block heights by archive eth_call to locate each transition, then a 10-block eth_getLogs window was read around it. Alchemy's free tier caps eth_getLogs at 10 blocks per request, which is why the reads are targeted rather than exhaustive.

Written identities (1)

#0157 B retrieved

ipfs://bafkreihecsjwf4d56j75ragnja3bgzmfxcso7j5wztrywh6prwi577zqse

Exhaustive log sweep

Not run. The sweep visits every block in 10-block windows and is opt-in: npm run logs -- --full. The targeted reads described above cover the same events at a fraction of the request count.