v1 state

row

Everything a caller needs about one request, on one line. Fields are separated by "|" rather than "," because a reason may well contain a comma; it may not contain "|" or a newline, which Propose enforces.

ListProposals

ListProposals pages newest first, which is the order anybody actually wants to read them in.

parseKey

GetProposal

CountProposals

HasVoted

HasVoted lets the page grey out a button instead of letting somebody sign a transaction that is certain to be rejected.

CanTakePart

CanTakePart answers the one question the page needs before it offers any of this: does this address hold a name.

Roster

Roster is the raw material for the leaderboards: one line per name, owner first, so the caller can aggregate however it likes. It lives here rather than in nslogic because this realm is being deployed anyway and nslogic is not — adding it there would have cost a fresh deployment of the largest realm we have, for a read. Paged, and the page walks every name in it. That is fine at the scale this registry is at and it will not be fine at fifty thousand names; at that point the aggregate belongs somewhere it is kept as it changes rather than recomputed on every read.

Version

Version lets a caller find out what it is talking to BEFORE it sends a transaction that would be rejected for having the wrong number of arguments. v1 has no such function, so a nil answer is itself the answer: an older realm. That is cheaper and more honest than the site assuming the newest shape and failing at signing time, which is exactly what happened when Propose grew a \`kind\`.

Proposal

Two things get asked for here, and they are not the same request. domain a new *domain to sell names under chain a new blockchain to accept an address for on profiles The kind is stored rather than inferred from the label, because "solana" is a plausible request of either sort and guessing wrong files somebody's vote under the wrong question.

proposals

// id (zero-padded) -> \*Proposal

votes

// id + "/" + voter -> "y" | "n"

nextID

maxReason

maxPage

assertHolder

A name is the ballot. Not a token balance and not a GNOT balance: holding a name is the one thing that cannot be borrowed for an afternoon, and it is the population this actually concerns.

assertNoSend

assertNoSend refuses coins, on every entry point. types.gno states "It holds no funds, at any point, for anybody" — and until now nothing enforced it. This package contained no banker, no OriginSend and no withdrawal path of any kind, so ugnot attached to a Propose or a Vote landed at the realm's address and stayed there forever, unreachable even by a successor realm. Nobody would do it on purpose; a fat-fingered wallet or a script reusing a payment helper would. The early return matters: a call arriving from another realm carries no OriginSend of its own to inspect, and treating that as an error would break composition for a check that has nothing to look at.

assertIsAdmin

The admin is READ FROM THE VAULT rather than stored here. Two copies of "who is in charge" is how a revoked admin keeps power somewhere nobody remembered to look.

key

Sortable keys, so paging is in creation order rather than the order the strings happen to compare in. 000000001 sorts before 000000010.

voteKey

assertLabel

The same shape a domain must have. A chain is asked for by its ticker, which fits the same rule, so one check covers both — and it keeps a proposal from asking for something that could never be created.

Propose

Propose asks for a domain or for a chain. Anyone holding a name may ask. The proposer pays the storage for their own proposal, and nothing else. That cost is the whole of the spam control: it is small enough that a real request is nothing to think about and large enough that filling the tree with rubbish is not free.

Vote

Vote records a yes or no. One per address per proposal, and it cannot be changed: a vote that can be switched turns the count into a race against whoever is watching, and there is no deadline here to make that fair.

Withdraw

Withdraw closes a request the proposer no longer wants. The votes already cast stay: deleting them would refund their storage to whoever called this, which is not the person who paid it.

Resolve

Resolve records what was decided. It does NOT create the domain — that stays a separate, deliberate call in nslogic. A vote is advice, and the vault has no undo.

Purge

Purge deletes a closed request and its votes, releasing the storage. The refund goes to WHOEVER SIGNS THIS, which is not the people who paid — so it is admin-only and it is not a tidying operation to run casually. It exists because a registry that can only ever grow is worse, not because reclaiming somebody else's deposit is free money.