I want to propose a change to how CRP nominations are collected, and I want to be upfront that it only works if Tezos Commons is willing to adopt it. So this is two things at once: a request to TC to buy in, and a request to the community to help design it.
First the ask to TC directly. Will you engage with this, and if the community builds something solid, will you use it? If the answer is no, tell me now. Everything below assumes you’re at least open to it.
Here’s the problem. Right now people nominate by posting a list of handles under #tezoscrp, or by filling out the TypeForm. The public posting is what people like. They tag everyone they want to recognize, across every category, in one shot. But X bans accounts for mass-tagging, the posts get spread across X, Reddit, Discord, and Telegram, and someone at TC (Cryptonio) has to gather them all by hand each month. The form works for people who prefer it, and I’m not proposing we remove it.
My proposal: build a web UI where you fill out one nomination covering as many categories and as many people as you want, submit once, and mint it as an NFT. The nomination data lives in the token metadata, with a shareable “CRP mm/yy” image. Because it’s on-chain, the month’s nominations aggregate directly from chain data. No cross-platform collection, no lost entries, no bans.
This is additive. Keep the form, keep the hashtag. On-chain just becomes the primary method, and if it’s better, people move to it over time on their own.
The reason to do it this way is simple. We’re a chain. Running our own recognition program on our own tech, with native minting and native sharing, is us using what we build. Once nominations are on-chain, badges, contributor history, access, and eventual on-chain voting all become straightforward to add later.
I don’t have a finished spec, on purpose. I want to settle the standard with the community first. Open questions:
Dedicated nomination token, or agreed conventions in FA2 metadata keys?
How to model one nomination that spans multiple categories, each with multiple nominees?
Required fields. My starting list: category, nominee, nominator, cycle, optional note. What’s missing?
Identity: people nominate by social handle today. Addresses, .tez or hack.tez names, DID, or a bridge between them?
Who indexes and aggregates, and where does the tally surface for TC’s monthly review?
Sybil resistance, weighting, eligibility: how much does any of it matter here?
The nine categories are settled and I don’t want to touch them. The work is the metadata format, since that’s the durable part every future front-end reads.
Devs, designers, anyone with opinions on how this should work, jump in. And TC, the one thing I need to know is whether you’ll use it. The rest we can figure out together.