Sale price
Cost to sweep
Cumulative active listings at or below each level. Listings already marked buying are shown separately.
Listed rares
Active listings from the top 1,000 collection ranks.
Proof of Supply
A running comparison of the public collection against a saved original copy.
What is checked
The first snapshot records token IDs 1–10,000. For every ID it stores the image reference, rarity rank, rarity score and the complete trait set returned by the market feed. Each record is hashed with SHA-256; those hashes are combined into one collection root.
Every five minutes the full market feed is downloaded again and compared with that baseline. A new ID, a missing ID, or any changed field produces a different root.
A separate deep pass downloads /api/snarks/:id and the final PNG from /api/art/:id. It hashes normalized metadata and the exact image bytes. Once the first archive is complete, the deep comparison runs every six hours.
If an NFT is replaced under an old number
Suppose the server keeps ID #234, but changes its traits, metadata or artwork. The new hash for that ID will no longer match the saved hash.
- The status at the top turns red and stays red.
- The alert names the affected ID and whether the feed, metadata, artwork, or several of them changed.
- The newly observed feed or files are saved with a UTC timestamp in a separate change record.
- The original baseline is kept intact, so the old and new versions can be compared.
Limits
This proves changes to data exposed publicly by Zilkroad. It cannot prove a hidden ownership reassignment if the public token, metadata and image remain identical. The marketplace also hides buyer and seller addresses in its public sales feed, so this page does not claim that a developer has never sold.