Token-listing petitions
Propose a token for supported markets and follow the governance process.
Why listings exist#
The chain-read templates can ask about any listed token's supply. The reporter reads a token's supply with a call it cannot change; what needs deciding is which tokens are worth reading. That is decided in public, on the listings page, rather than by whoever knows someone.
The three states#
- Petitioned. Anyone puts a token in front of governance by naming its address and a label. The listing notice period is seven days. A token that has already been petitioned cannot be petitioned again.
- Backed — or opposed. Accounts with locked RINO attach their weight to either column. One account, one stance, any size; changing your mind is a withdrawal followed by the other stance.
- Seated. After the notice, governance may seat the token. The contract first proves the address has code and answers a supply read. Governance may also remove a seated token at any time.
Backing is a signal that cannot bind. Governance is not obliged to seat a token because it was backed, and the page says so rather than implying a vote.
Weight#
The weight an account contributes is
min( effective locked balance, 250,000 RINO )
and an account needs an effective balance of at least 1,000 RINO to count at all. The effective balance is the vault's seven-day average, so weight cannot be borrowed for a block. See RINO token and tiers.
Because the weight is snapshotted when you take a stance, anyone may resync a stale entry, and moving your RINO out of the vault removes your backing. The listings page prints accounts backing and RINO backing side by side and never merges them: a single number would let one large holder look like a crowd.
The same machine for questions#
The registry runs the identical mechanism for market requests — a proposed question for the curated calendar template, committed as a hash — with the same notice, the same weights and the same caps. See Propose a question.
The interface#
The listings page has two fields and one button for a new petition, one button each for backing and opposing, a queue ordered in daylight, and a countdown per petition read against the chain's own clock. Where the registry is not deployed on the build's chain, every control is in preview mode and shows the exact call it would make.
