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

Protocol Upgrade: Superchain Registry 2.0

Voting ended 12 months agoSucceeded

The Citizens’ House may veto any Protocol Upgrade approved by the Token House.

In Voting Cycle #32, the Token House approved Protocol Upgrade: Superchain Registry 2.0

Citizens may veto this Protocol Upgrade by casting a “Veto” vote on this Protocol Upgrade #12: Veto #12 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 30 “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
27 VOTE100%
I do not feel confident enough
0 VOTE0%
Quorum:2700%
Download mobile app to vote

Discussion

Citizens' HouseProtocol Upgrade: Superchain Registry 2.0

Timeline

Feb 05, 2025Proposal created
Feb 06, 2025Proposal vote started
Feb 12, 2025Proposal vote ended
Feb 12, 2025Proposal updated