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
Copy file name to clipboardExpand all lines: README-yearnBorg.md
+61-6Lines changed: 61 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -79,22 +79,77 @@ all coming operations listed above will require approval of both `ychad.eth` and
79
79
80
80
### Future On-chain Governance Transition
81
81
82
-
Yearn's Snapshot governance will be replaced with an on-chain governance at some point (ex. `YearnGovExecutor`).
83
-
`YearnGovExecutor` (or its adapter) must satisfy the following requirements to integrate with the co-approval process:
84
-
- Each proposal must include generic transaction fields (`target`, `value`, `calldata` or their equivalents) to enable `YearnGovExecutor` to execute the proposal upon approval
85
-
- Proposals involving `ychad.eth`[Restricted Admin Operations](#restricted-admin-operations) must be executed solely by `ychad.eth` to enforce co-approval requirements
82
+
Yearn's Snapshot-based governance will transition to an on-chain governance system (ex. `YearnGovernance`).
83
+
An adapter (`YearnGovernanceAdapter`) will be implemented by MetaLex to manage the implementation details on co-approval process.
84
+
To integrate successfully, `YearnGovernance` must meet the following requirements:
85
+
86
+
- Each proposal has an unique ID (ex. `proposalId`)
87
+
-`YearnGovernanceAdapter` can read the proposal's voting result and verify it is passed
88
+
-`YearnGovernanceAdapter` can extract the admin operation (ex. `target`, `value`, `calldata` or equivalent) from the proposal
86
89
87
90
The transition process from Snapshot to on-chain governance is listed as follows:
88
91
89
-
1. A final Snapshot proposal will be submitted to replace `Snapshot Executor` with `YearnGovExecutor` by transferring ownership of `SudoImplant` and `EjectImplant` to `YearnGovExecutor`
90
-
2. Once co-approved and executed by `ychad.eth`, the transition process is complete
92
+
1. A final Snapshot proposal will be submitted to grant `YearnGovernanceAdapter` ownership of the implants
93
+
2.`ychad.eth` to co-approved and executed the proposal
94
+
3. The first on-chain proposal will be submitted to revoke `SnapShotExecutor` ownership of the implants
95
+
4.`ychad.eth` to co-approved and executed the proposal. The transition is now complete
91
96
92
97
After the transition, the co-approval process will become:
93
98
94
99
1. Operation is initiated on the MetaLeX OS webapp
95
100
2. An on-chain proposal will be submitted to `YearnGovExecutor`
96
101
3. Once the vote passed, `ychad.eth` will co-approve it by executing the operation through the MetaLeX OS webapp
97
102
103
+
Below shows the changes of BORG architectures before/after on-chain governance transition:
classDef todo fill:#191918,stroke:#F09B4A,stroke-width:2px,color:#F09B4A;
143
+
class ejectImplant borg;
144
+
class sudoImplant borg;
145
+
class snapshotExecutor borg;
146
+
class oracleAddr borg;
147
+
class yearnGovernanceAdapter borg;
148
+
class ychad yearn;
149
+
class yearnDaoVoting yearn;
150
+
class yearnGovernance yearn;
151
+
```
152
+
98
153
### Module Addition
99
154
100
155
New Modules grant `ychad.eth` privileges to bypass Guards restrictions, therefore it requires DAO co-approval via [Co-approval Workflows](#co-approval-workflows).
0 commit comments