You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue focuses on feature documentation for the Election Cycle process on DIVA Governance Dashboard.
The election cycle is a process through which DIVA token holders can choose a new protocol owner to take over the responsibilities of future protocol development.
An election cycle can be triggered if any wallet has more DIVA tokens staked than the current protocol owner. Under this condition, the candidate can trigger the election cycle from the dashboard.
The election cycle is divided into two parts
Showdown period - which will last 30 days since the election cycle triggers. During this period people can still continue to stake/unstake DIVA tokens for any candidate.
Claim submission period - this will last for 7 days after the showdown period has ended, and during this period people cannot unstake their DIVA tokens from a candidate until the chosen candidate has claimed its ownership.
If for some reason the chosen candidate does not claim its ownership within a period of 7 days then the next highest DIVA token staked candidate will be chosen to become protocol owner and will be able to claim its ownership.
UI Design Specs
Show the Trigger election button next to the Stake button for the candidate whose stake balance is more than the current protocol owner's balance
This button will only be visible to the candidate who is eligible to trigger an election and will show when the wallet is connected.
Once the election cycle is initiated show election cycle details below the protocol owner details as present in the design. This will contain the following details:
Showdown period progress bar: show countdown timer inside progress bar
Ownership claim submission: show countdown timer inside progress bar (reactive until showdown period is over)
Election triggered by: show candidate address who triggered the election cycle
Leading candidate: show address of the next leading candidate
Once the election cycle is over the candidate can see Claim ownership button to claim ownership of the protocol
Acceptance Criteria
The design matches with mockup provided
The app functionality is according to the specs provided
Context
This issue focuses on feature documentation for the Election Cycle process on DIVA Governance Dashboard.
The election cycle is a process through which DIVA token holders can choose a new protocol owner to take over the responsibilities of future protocol development.
An election cycle can be triggered if any wallet has more DIVA tokens staked than the current protocol owner. Under this condition, the candidate can trigger the election cycle from the dashboard.
The election cycle is divided into two parts
UI Design Specs
Show the Trigger election button next to the Stake button for the candidate whose stake balance is more than the current protocol owner's balance
This button will only be visible to the candidate who is eligible to trigger an election and will show when the wallet is connected.
Once the election cycle is initiated show election cycle details below the protocol owner details as present in the design. This will contain the following details:
Showdown period progress bar: show countdown timer inside progress bar
Ownership claim submission: show countdown timer inside progress bar (reactive until showdown period is over)
Election triggered by: show candidate address who triggered the election cycle
Leading candidate: show address of the next leading candidate
Once the election cycle is over the candidate can see Claim ownership button to claim ownership of the protocol
Acceptance Criteria
Design Mockup
Link to design - https://www.figma.com/file/CqOXnCH2EMUKRfVxfnUccz/DIVA-Governance-Dashboard?node-id=143%3A3139&t=YHfIfNuIXO53R9EB-4
Dashbaord with Trigger election button
Dashbaord - Election triggered
Dashbaord - Claim ownership
The text was updated successfully, but these errors were encountered: