feature: governance portal functionality

[okjintao]

Summary

Badger will launch the timelock contract into production. The new timelock allows numerous parties to submit proposed transactions, for those proposals to be vetoed, then ratified or rejected, and ultimately executed. The individuals in these roles will need to have this utility in the governance pages.

Requirements

• New UI mock up to support the following requirements

• Proposal History

  • display a paginated view of all proposals, displaying the most recent or active first
  • display information for a given proposal for front page
    • status
    • title
    • time of last update + update action
  • breakdown of addresses with permission per role

• Proposal Summary (Click In)

  • same information available as in history item
  • proposal detail
    • break down of calls made
    • potentially in text summary of proposal code submitted by proposer
  • proposal history (event occurred at)
    • proposed
    • vetoed
    • executed
  • proposal can have a predecessor tx proposed which is a condition for the current one to be able to execute despite of reaching the deadline, ability to intertwine txs if they have a predecessor condition and displaying their status

• Support for Role Actions

  • enable 'veto proposal' functionality for address with the role vetoer
  • enable 'create proposal' functionality for address with the role proposer
  • enable 'execute proposal' functionality for address with the role executor
  • enable 'cancel proposal' functionality for address with the role cancellor
  • enable supreme court functionality for address with such role, which enable them to reject vetoed tx or agrees with the vetoers

Resources

https://user-images.githubusercontent.com/49598030/156919403-76cdfeb2-4a72-4e8a-9456-61c4b0661ef6.png

Initial design work included a figma prototype similar to this, the current columns are not ideal and do not fully display probably what a short summary item can have. We will end up having a click in with a simple details page instead.

https://tx.eth.samczsun.com/ethereum/0x665c4db0b7dcf44eb2ead3d455b12bfb244de9a2d3239d756ca3fbdbf21817bb

Example of transaction breakdown app, not quite words or simple but a visual breakdown via text.

Challenges

• decoding arbitrary requests into potentially readable description
• centralized / decentralized or automated creation of proposal details

Examples

• Compound Governance

[petrovska-petro]

as discussed yesterday, contract has being deployed in arbitrum to allow ui testing:

contract address - verified

• schedule tx 1: https://arbiscan.io/tx/0x8dfe1a474202a3f7bb75655628ad7958ee37dfb87dcdc180f5223d2018f6da43. 3 days delay, action represents a deposit into a sett

• schedule tx 2: https://arbiscan.io/tx/0xea39d031f98d8234c397a1fc982208525f1974faf51f1782260644b1c9b489c3. 6 days delay, action represents a withdrawAll from a sett

• schedule tx 3: https://arbiscan.io/tx/0x8fa7f69fecfa63b469d7c1d388ccfe64b35fbeb85b02fce9bf5aab5439a6834c. 9 days delay, acton represents a partial withdraw from a sett

• dispute tx 3: https://arbiscan.io/tx/0xe1cffd42eb412c1fd39f6565539ddec7775f3d23f9ffe7e5384c81a0843beec5

[petrovska-petro]

add another tx, which has a predecessor: https://arbiscan.io/tx/0x24b987313945097a69f4e135e984a8fd203a8beedf093150bdedbfd37a7fc19a

[petrovska-petro]

schedule batch tx sample: https://arbiscan.io/tx/0xdb286638e5dc3a62c2c814fe61016ad0e49349bbba0fcce2b36640a42b70cac3

• 1 month delay
• actions are setGuardian(0xC69Fb085481bC8C4bfF99B924076656305D9a25D) & setStrategist(0xE8eA1D8B3a5A4CEC7E94AE330fF18E82B5D22fA6)

[ZKProf]

Here are the Figma design and prototype links:

Layouts:
https://www.figma.com/file/AB5enNOx2W8EGZoNq47Rc1/app-governance-timelock?node-id=0%3A1&t=JWmvEcbsbYpeSRrB-1

Proto:
https://www.figma.com/proto/AB5enNOx2W8EGZoNq47Rc1/app-governance-timelock?page-id=0%3A1&node-id=306%3A3163&viewport=709%2C-503%2C0.41&scaling=min-zoom&starting-point-node-id=306%3A3163