Global kill-switch

[facuspagnuolo]

Idea

User story

• As an application developer, I want to be able to notify our users that a critical event happened and that they must upgrade their applications to the latest version to avoid being affected.

• As a security auditor, I want to inform users of a potential issue with a contract they're using and recommend them from using the current version of the contract.

• As as user, I want to be able to choose whether to switch my application off upon being notified that an upgrade is strongly recommended.

Implementation

• Research possible approaches - doc (sprint 12)
• Proof of concept PR 516 (sprint 12)
• Initial review and discuss edge cases (sprint 13)
• MVP implementation of aragonOS contracts - PR 518 (sprint 13)
• Review recoverability proposal described here (sprint 14, sprint 15)
• Sync on scope for KillSwitch and recoverability (sprint 16)
• Emergency upgrades path proposal - PR (sprint 18)
• Final review
• Discuss terminology and write inline documentation

---

Exposing this to users through an UI implementation will likely follow as a separate issue.

[luisivan]

Next step: Have a call to discuss edge cases

[luisivan]

Next step: @izqui and @sohkai to make a final call on the implementation during Sprint 14

[sohkai]

This was researched and an idea spiked. As we won't be making protocol-level changes at this moment, we will stage and re-consider this in the future.