feat: add emergency procedures #295
Conversation
storming0x
requested review from
saltyfacu,
Grandthrax,
lbertenasco,
a user,
fubuloubu,
banteg,
milkyklim,
dudesahn and
poolpitako
docs/EMERGENCY.md
Outdated
|
|
||
| This role will be in charge of coordinating comms and operations assistance as needed: | ||
|
|
||
| - Clear with war room what information and communication can be published during and after the incident |
There was a problem hiding this comment.
Start the voice channel and keep comms as clean as possible.
docs/EMERGENCY.md
Outdated
| | Communications | Telegram | Discord | | ||
| | Transaction Details | [Etherscan](https://etherscan.io/) | [EthTxInfo](https://ethtx.info/) | | ||
| | Debugging | Brownie | [Tenderly](https://tenderly.co/) | | ||
| | Transaction Builder | [ape-safe](https://github.com/banteg/ape-safe) | Backup if gnosis safe Api is not working?? | |
There was a problem hiding this comment.
@banteg is there any workaround if gnosis api is down?
Should the emergency-toolbox include interactions with the ms contract directly?
feat: check box for check list Co-authored-by: El De-dog-lo <3859395+fubuloubu@users.noreply.github.com>
storming0x
force-pushed
the
feat/emergency-docs
branch
from
163d993 to
a6b4eee
Compare
docs/EMERGENCY.md
Outdated
| 2. Bug in Vault/Strategy code that may cause loss of funds for users | ||
| 3. An exploit in an underlying protocol that a yearn strategy is utilizing that may lead to loss of funds for the users | ||
| 4. A bug in an underlying protocol that a yearn strategy is utilizing that may lead to loss of funds for the users | ||
| 5. A key role like a strategist having the private keys stolen |
There was a problem hiding this comment.
If web credentials are compromised, what is our contingency plan?
AWS full admins (all should use 2FA):
- x48
- nymmrx
- Luciano
- Facu
Domain admins
- x48
- Klim
There was a problem hiding this comment.
good point, what scope should we add here regarding website incidents? wondering if we need the exact same war room configuration for a website incident
There was a problem hiding this comment.
resolving this for now to merge the PR, it seems we can create a separate addendum for web related emergencies and later link it to this one.
This comment has been minimized.
This comment has been minimized.
lehnberg
force-pushed
the
feat/emergency-docs
branch
from
0839e40 to
ecea22c
Compare
|
@lehnberg please fix your commit to have a lowercase I on |
storming0x
force-pushed
the
feat/emergency-docs
branch
from
ecea22c to
843fbc8
Compare
|
@dougstorm good to merge? or needs more review? |
|
Apologies @fubuloubu, I struggled with the syntax for conventional commits. Thanks @dougstorm for fixing while I was afk. 🙏 |
* feat: add emergency procedures * feat: update docs/EMERGENCY.md feat: check box for check list Co-authored-by: El De-dog-lo <3859395+fubuloubu@users.noreply.github.com> * docs: incorporate comments and iterate on wording Co-authored-by: dougstorm <dougstorm@users.noreply.github.com> Co-authored-by: El De-dog-lo <3859395+fubuloubu@users.noreply.github.com> Co-authored-by: Daniel Lehnberg <daniel.lehnberg@protonmail.com>
* feat: add emergency procedures * feat: update docs/EMERGENCY.md feat: check box for check list Co-authored-by: El De-dog-lo <3859395+fubuloubu@users.noreply.github.com> * docs: incorporate comments and iterate on wording Co-authored-by: dougstorm <dougstorm@users.noreply.github.com> Co-authored-by: El De-dog-lo <3859395+fubuloubu@users.noreply.github.com> Co-authored-by: Daniel Lehnberg <daniel.lehnberg@protonmail.com>
Change Log: