Revere · Origin
Where Revere came from
A graded card's cert number is the one thing every grader, vault and marketplace agrees on. Yet an offer on a slab could only be made inside whichever venue held it, on that venue's terms. Holders were left with company rules instead of the reality of the situation: the card is theirs.
I built Revere so that a holder can be reached by any buyer, through any wallet, without asking a marketplace for permission. It's my gift to holders everywhere. It is open and permissionless on purpose, and it will stay that way.
So far
- 1 October 2026. The standard was first published and the first escrow went live on Polygon. That morning a 1 USDC offer on a Garchomp ex CGC 10 was accepted in a single transaction.
- 3 October 2026. The standard was tightened (v0.2), the escrow moved to its second version, and the library went to npm as
@reverefi/sdk.
The record
- On Polygon: an authorship attestation naming the designer and the publisher, with fingerprints of the standard as first published. It can't be edited or revoked.
- In Bitcoin: the standard and the list of evidence, timestamped with OpenTimestamps.
- Everything else — commits, deployments, verifications — is in PROVENANCE.md. Each item can be checked without asking us.
Build on it
The standard, the escrow and the library are MIT-licensed. Implement it, fork it, improve it. If you build on the standard, say so; the name Revere refers to this one.
— Chad Neal