• © Goverland Inc. 2026
  • v1.0.1
  • Privacy Policy
  • Terms of Use
Citizens' HouseCitizens' Houseby0x4ce779965d55f14BaF650f86758420BAE27AA3f10x4ce7…A3f1

Protocol Upgrade #9: Veto #9

Voting ended over 1 year agoSucceeded

The Citizens’ House may veto any Protocol Upgrade approved by the Token House. In Voting Cycle 23b, the Token House approved Protocol Upgrade #9 Citizens may veto this Protocol Upgrade by casting a “Veto” vote on this Fjord Upgrade Proposal. If you do not wish to veto but would like to register your participation in this voting cycle, you may select “No Veto”. A veto requires 45 “Veto” votes. A third option “I do not feel confident enough to vote” has been added to help the Collective begin to measure the level of understanding among voters.

Casting a veto is a serious decision. If a proposal approved in the Token House is vetoed by the Citizens' House, the proposal will not be enacted. In the case of Protocol Upgrades, vetoing may have serious consequences on engineering timelines and milestones. Proposals that may be vetoed by the Citizens' House have already been evaluated and approved by the Token House, which has been entrusted with primary responsibility over that proposal type. A Citizens' House veto may be appropriate if a proposal is believed to be malicious or to have been passed by a compromised Token House (either captured or acting out of self-interest rather than the Collective interest.)

If you choose to cast a “Veto” vote, please share your rationale with the community as a comment on the Protocol Upgrade proposal on the forum.

Off-Chain Vote

Veto
0 VOTE0%
No Veto
50 VOTE100%
Not Confident Enough to Vote
0 VOTE0%
Download mobile app to vote

Discussion

Citizens' HouseProtocol Upgrade #9: Veto #9

Timeline

Jun 18, 2024Proposal created
Jun 20, 2024Proposal vote started
Jun 26, 2024Proposal vote ended
Jun 26, 2024Proposal updated