Outline blocking dependencies on centralised tools (e.g. etherscan) #29
Description
Goal
Checklists do not enforce processes that are blocked in case a single service is down
Context
Recently, spell team experienced downtime of etherscan, which caused a multi-hour delay in the spell handover and later confusion among delegates on why contract is not verified on etherscan. The delay was resolved by unanimous agreement within the spell team to proceed with an alternative verifier service and later still use etherscan to verify contract and resolve the confusion. Another reason to not depend on a single service is of course security: it's much easier to compromise a single crucial service documented in the process, than try to attack multiple independent services at the same time.
In order to prepare to such events, we should 1) evaluate existing dependencies 2) evaluate potential circumventions 3) proceed with removing dependencies one-by-one.
Todo
- List existing dependencies found in the checklists / known processes
- List potential circumventions (general or applicable to each specific dependency)
- Create first specific issue to remove dependency on etherscan