Skip to content

Remove blocking dependency on etherscan #31

@SidestreamColdMelon

Description

@SidestreamColdMelon

Goal

Spell process is not blocked in case etherscan is down/not available

Context

As per the parent issue #29, currently there are multiple places in process which refer to etherscan as place to check something. But as etherscan is a centralised tool, we have to expect a possibility that 1) it is down 2) it is compromised and prepare accordingly.

Places where we refer to etherscan

Proposed circumvention

Use multiple different services to verify the source code.

Tasks

  • Extend the verification script
    • Send flattened code to multiple services (potentially using forge verify-contract instead of making raw requests)
    • Ensure requests to services are non-blocking (in case one service is down)
  • Editing checklists
    • Replace "etherscan" with "at least 2 trusted block scanners"
    • Define/refer to a "list of trusted blocks canners" (used by the verification script)
    • Get priority fee from a more decentralised source (or otherwise make it a recommendation)
  • Replace or remove automatic check of the source code

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions