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
We want to demonstrate that governance can pause offers in the Kread dapp to take control in emergency situations.
Description of the Design
Add a governance wrapper around the Kread app (/~https://github.com/Kryha/KREAd/tree/develop/ ). At this point, it doesn't appear that they need any governed params beyond the electorate.
Security Considerations
The goal is assurance that the contract is governable.
Scaling Considerations
Not an issue.
Test Plan
A test that shows that governance can (selectively) suppress exercise of invitations.
In particular, governance consisting of one or more addresses chosen by Kryha (based on discussion with @ivanlei who talked with Kryha about this a few weeks back)
Much like oracle operators or EC members, the addresses go into the proposal to be confirmed by BLD stakers.
What is the Problem Being Solved?
We want to demonstrate that governance can pause offers in the Kread dapp to take control in emergency situations.
Description of the Design
Add a governance wrapper around the Kread app (/~https://github.com/Kryha/KREAd/tree/develop/ ). At this point, it doesn't appear that they need any governed params beyond the electorate.
Security Considerations
The goal is assurance that the contract is governable.
Scaling Considerations
Not an issue.
Test Plan
A test that shows that governance can (selectively) suppress exercise of invitations.
Upgrade Considerations
use upgradable governance. (#5200)
The text was updated successfully, but these errors were encountered: