This project idea is related to reducing the security burden and risk of ex-core being the only knowledgeable people in the protocol architecture. Anyone should be able to do this. The project is essentially split into two parts: research and writing, and then making a system based off that.
[ ] Add 1-2 more people in the multisig minimum, to improve signature time
[ ] Write a guidebook on multisig reaction → anyone can write, it’s all open. See below
[ ] Write a warning system which warns in case of protocol work deviations
→ make a DAO proposal on what issues can be found
→ this in turn will complete the Risks and T&C page
TASK: Write coherent instructions on how to pause the system and change the settings to fix the protocol - this can be seen in the contracts & available documentation already.
This makes sure that if Mikael is offline, he can still fix things: if an oracle malfunctions, what and how to do, if some other case happens, what and how to do; how to unpause in certain cases. It is better to be able to test any transaction in a fork, to test what it does in case it goes through (needs an environment) like how many CAs will get liquidated as a result
turning off (blocking) tokens - what to choose?
→ forbid (but doesn’t allow to turn back on currently)
→ LT to close to 0 or fully 0
turning off fast-checks
turning off contracts (adapters)
turning off credit managers fully
pausing all contracts or separately, what and when
what to do when someone sends a token and doesn’t get counted to HF: interface warning, a docs FAQ, or changing in contracts later on. If a token that is not on the list gets sent to a CA, then multisig needs to do soemthing, because this is something only a multisig can do.
changing fees minimum / maximum (what for though? need cases/scenarios)
Draft: