Track 2 · What you can do5 of 6
Project registry
The real owner of a project declares, on-chain, exactly which tokens are officially theirs, so wallets and explorers can show a verified “official” badge and counterfeits stand out.
Anyone can issue a token with a familiar name. The project registry lets the genuine owner of a project state plainly, on the chain itself, which tokens really belong to it, so the official ones carry a verified badge and the impostors don't.
How a project proves what's official
A project starts by issuing one token that stands for its identity: the project's name, on-chain. The owner then publishes a list of the tokens that officially belong to the project, and signs that list from the project's own address. Anyone can check the signature, so only the genuine owner can bless a token as a member.
Built from primitives you already have
There is no special “project” transaction. A registry is just three existing actions used together (issuing the identity token, publishing the list, and signing the link between them), so it required no change to the protocol at all.
Updatable, and always owner-signed
Projects grow. The owner can publish a new list and re-sign it at any time; the most recent signed version always wins, and the old one is superseded. Membership is simply whatever the current owner has most recently attested.
What it isn't
A registry is curation by the project, not a mutual handshake: a project recognizes the tokens it chooses to. It is also same-chain: a list only carries authority on the chain where the project's identity token lives. And tokens that didn't yet exist when a list was published are simply ignored.
What you can build
A verified directory for an art series or brand, an anti-counterfeit badge for a community's tokens, or an official roster collectors can trust: all provable straight from the chain.