Upgrade Proposal #13: OPCM and Incident Response improvements

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

In Special Voting Cycle #34, the Token House approved Upgrade Proposal #13: OPCM and Incident Response improvements

Citizens may veto this Protocol Upgrade by casting a “Veto” vote on it. 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 forum