Governance and DAO
The armor token is deployed at https://etherscan.io/address/0x1337def16f9b486faed0293eb623dc8395dfe46
The vArmor token is deployed at https://etherscan.io/address/0x5afeDef11AA9CD7DaE4023807810d97C20791dEC
The Timelock contract is deployed at https://etherscan.io/address/0x5AFeDEF13Bd7B3e363db724420D773cAa8B88763
The Governor contract is deployed at https://etherscan.io/address/0x5aFeDeF1454CDd11d4705c06aa4D66Aa396343f6
DAO and RCA Guardian
The DAO and RCA Guardian located at https://etherscan.io/address/0x1f28eD9D4792a567DaD779235c2b766Ab84D8E33
Authority of the DAO
The DAO will have authority over the following scenarios
- Verifying Liquidation Quantities per vault
- Establishing new RCA vaults
- Managing vault profit model
- Treasury allocations under $X
- 400MM $Armor token disbursement in Timelock address
- Change the address of RCA Guardian
Authority of the Multisig
The Guardian multisig, or Admin is a multi-signature wallet that has the authority over the following scenarios:
- Recognize Hack to Ecosystem
- Set Reserved Percentages of RCA Vaults (up to 50%)
- Veto of proposals in the 2 day timelock
- Treasury allocations over $X
Areas for Discussion
There are multiple places in which the user base can interact with to participate in discussion related to governance:
These are discourse powered forums that allow users to exchange ideas in a less formal manner related to governance proposals. There are currently two relevant categories Ideas and Proposals.
Ideas – is for a more casual exchange of ideas between governance participants
Proposals – This is where discussion from the Ideas category take more organized form to garner more critical feedback
This is the front-end for the governor contract where formal proposals are submitted on-chain. All proposals and voting through this front-end will be a transaction directly on the Ethereum network.
The Proposal Process
For a user to propose ideas on the forums, they do not need to even be a token holder. Discussion of ideas is open to anyone to promote a positive and open space for public discourse.
Armor to vArmor
For a user to participate in the proposal process they must navigate to and transfer Armor tokens into vArmor. For a how-to, please visit this article: . This is in place to ensure only active users participate in governance, and to prevent large entities such as exchanges from participating in the process.
When a proposal is finally put to vote on chain there are a few requirements that are required
For a wallet to call the Propose() function the address must have a total delegation of votes equaling 1 Million vArmor tokens, these can be delegated directly by the wallet address or to the wallet by other users.
When the proposal function is called, it enters a voting period of 3 days.
For the vote to pass, a quorum of 30 MM votes must be reached. A majority of those votes must be cast in the affirmative
Once the voting period ends, if the proposals passed it will enter a time lock for 2 days.
During the timelock the multisig treasury can act as a veto guardian to prevent the proposal from passing. This is in place to help prevent governance attacks against the protocol.
After the timelock period passes, the proposal will execute.
Glossary of Terms
Delegation: Token holders cannot vote or create proposals until they call the delegate() function and assign their voting power to a wallet address. This can be changed at any time and does not remove the tokens from the original wallet address. This value is recorded as a proposal goes live, so a wallet’s delegated votes will not be recorded if done so after a proposal is launched.
Voting: When a proposal is active users can vote using their delegated EASE tokens to vote for or against the proposal. This is done through the CastVote() function. Only votes delegated before the proposal became active our counted
Voting Period: The time in which a user can vote on a proposal before results are called. It is currently set to 3 days but is able to be changed through the proposal process.
Proposal: A proposal is a piece of executable code that can alter the functionality of the deployed EASE contracts. A user must have 1 million EASE tokens delegated to their wallet address before creating a proposal on chain. A proposal then enters a 3 day voting period, if at any time during this period the proposer’s wallet address drops below the required delegate threshold. The proposal will fail.
Quorum: The required minimum number of votes needed in order for a vote to be considered valid. 30 million votes need to be submitted with a majority in the affirmative to pass a proposal.
Timelock: Any passing proposal will experience a 2 day delay before being executed. This is in place to ensure the safety of the protocol by allowing time for a veto to occur from the multisig guardian in the event of a governance attack.
$gvEase tokens: See the gvEase announcement here.