ICP Proposal Forum

Proposal ID: 138380

# [Ωmega-vote](https://dashboard.internetcomputer.org/neuron/18363645821499695760) **Ωmega-vote** is one of the 3 options provided by the **[ALPHA-Vote neuron automation system](https://forum.dfinity.org/t/alpha-vote-secure-your-stake-never-miss-a-vote/56826)**. ALPHA-Vote ensures the NNS gets the best out of its voters, while allowing voters to get the most out of the NNS. Voters who intend to **sometimes** step in and vote on a specific topic should consider following Ωmega-vote. This ensures a diligent vote is cast by default (if D-QUORUM has voted), but also gives the follower the ability to vote manually for the vast majority of the voting period (should they decide to). If they end up not voting manually, D-QUORUM’s vote will be copied by Ωmega-vote within the last 3 hours of the proposal deadline (which will then trigger your neuron to vote the same way). If D-QUORUM didn’t vote either, then a default rejection will be triggered (in the same way as Ωmega-reject). ### What problem does ALPHA-Vote aim to solve? There are notable examples where diligent voters have lost followees simply for missing an occasional vote. This dynamic is not helpful for encouraging high-quality due diligence and decentralization. This tendency of followers has been used as reasoning to diminish the size of the voting quorum of well-known neurons, including adding hotkeys which grant individuals unilateral control over otherwise community-controlled neurons. ALPHA-Vote aims to provide an alternative approach that does not compromise on security and decentralization. This solution allows diligent voters to take their time during reviews, safe in the knowledge that they will not accidentally miss the deadline in a way that leads to lost voting rewards. Followers commonly value knowing that their followee neuron will always vote, **no matter what**. ### How does ALPHA-Vote ensure a vote is never ever missed? ALPHA-Vote has multiple degrees of redundancy and fault tolerance built in. The system is spread across numerous different subnets, including the fiduciary subnet, so if one subnet stalls the others will pick up the slack. ### How does ALPHA-Vote deliver highly secure votes? ALPHA-Vote is deployed on the fiduciary subnet which is composed of 34 nodes. There are also fallback canisters that reside on smaller subnets, but these canisters are required to reach consensus before they can affect the final vote. This means multiple 13-node subnets would need to be attacked in order to affect the behavior of ALPHA-Vote, provided the 34-node fiduciary subnet has also been successfully attacked or stalled at the same time. Once ALPHA-Vote is finished, the main canister (on the fiduciary subnet) will be controlled by a large quorum of developers, notable governance participants and DFINITY engineers who are required to come to consensus in order to deploy updates. There is no anticipated need to deploy updates, except for unanticipated API changes that may occur in the future. The fallback canisters on the smaller subnets will be blackholed. Each of these control their own set of neurons, which each contribute to the final vote of the known neurons. If these blackholed canisters ever break (as a result of unanticipated API changes), the known neurons can be reconfigured to follow a fresh set of fixed blackholed canister controlled neurons. In the meantime, no votes would be missed as the blackholed canisters simply serve as an edge-case backstop (the main canister on the fiduciary subnet is capable of catching proposals and triggering votes by itself). Advanced users who would prefer immutable behavior (with the risk that it may break at some point in the future) can follow the blackholed canister neurons directly. ### How can I monitor the behavior of ALPHA-Vote canisters and neurons? Once the known neurons are adopted you can track the votes like any other known neuron, on the dashboard and via the governance canister. [All canisters](https://github.com/aodl/ALPHA-Vote/blob/master/canister_ids.json) also have publicly visible logs. -------- For more information about blackholing, decentralization and discussion about future developments (including autonomous perpetual cycles for added resilience), please visit the forum -> [ALPHA-Vote: Secure Your Stake, Never Miss a Vote ✅](https://forum.dfinity.org/t/alpha-vote-secure-your-stake-never-miss-a-vote/56826)