Recall
A GIP is in 'under discussion'. What does that tell you?
Anyone can write a GIP, so its existence means somebody wrote it down. Reading a proposal as a decision is the single most common way to misread this ecosystem.
The Council is a six-of-ten multisig. What follows for a GGP vote?
The threshold is the multisig itself rather than a separate rule layered on top of it.
Why can the protocol not verify indexers' work on chain?
So claims are made comparable rather than verified, and disagreement triggers a human process. Arbitration is where the protocol genuinely depends on people rather than incentives.
Which is NOT grounds for a dispute?
Downtime costs revenue, which is the network's way of handling it. Disputes are for false claims, and keeping bad service and false claims in separate categories is deliberate.
Burns exist mainly to:
Curation entry and query sending are both actions that could be spammed. Burning rather than redistributing means no constituency benefits from encouraging them, which is a weaker benefit and a much more robust one.
0 of 5 answered
Practical task
Follow one proposal all the way through. GIP-0089 is the best specimen available because it completed recently and changed numbers you have seen elsewhere in this site.
Ticks are stored in this browser only. No account, no server, nothing sent anywhere.
A closing thought
That last item is the point of this path. Governance is not a spectator activity here: proposals are public, discussion is open, and the people writing GIPs are reachable.
The realistic contribution most people can make is not writing a proposal. It is reading one carefully and saying, publicly, where it is wrong. Somebody running infrastructure who spots a mechanism flaw during discussion is worth a great deal more to this protocol than any amount of commentary afterwards.
Where next
- The mechanisms these decisions govern: indexers, curators, delegators.
- Every number on this site, with its source and the date it was read: parameters.
- What changed recently and when we noticed: changelog.