Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature]: Add a check on start-up that all RPCEndpoints are talking to archival nodes #11153

Closed
wwestgarth opened this issue Apr 18, 2024 · 0 comments · Fixed by #11197
Closed
Assignees
Labels
arbitrum feature new feature to be developed spike technical research typically required to prove a concept, validate an approach or better understand

Comments

@wwestgarth
Copy link
Contributor

wwestgarth commented Apr 18, 2024

Feature Overview

In order to make sure Validators are using Ethereum/Arbitrum nodes that allow calls to eth_getLogs()
We will add some check at startup that the configured RPCEndpoints point to archival node
So that validators cannot start unless they can contribute to event forwarding

Its not clear what the best way to do this is as it doesn't look like there is an API to just ask the node's state.

One idea is that on startup/snapshot-loading to call eth_getLogs() on the deployment block of the multisig control contract and get that they can see the event for the original default signer.

Specs

  • Link to spec or section within a spec

Tasks

A checklist of the tasks that are needed to develop the feature and meet the acceptance criteria and feature test scenarios.

  • [ ]
  • [ ]

Feature test scenarios

Detailed scenarios that can be executed as feature tests to verify that the feature has been implemented as expected.

GIVEN (setup/context)
WHEN (action)
THEN (assertion) For example...
See here for more format information and examples.

Additional Details (optional)

Any additional information that provides context or gives information that will help us develop the feature.

Tasks

Preview Give feedback
No tasks being tracked yet.
@wwestgarth wwestgarth added spike technical research typically required to prove a concept, validate an approach or better understand feature new feature to be developed arbitrum labels Apr 18, 2024
@wwestgarth wwestgarth added this to the 🏛️ Colosseo milestone Apr 19, 2024
@wwestgarth wwestgarth moved this to In Progress in Core Kanban Apr 19, 2024
@wwestgarth wwestgarth self-assigned this Apr 22, 2024
@wwestgarth wwestgarth moved this from In Progress to Todo in Core Kanban Apr 22, 2024
@wwestgarth wwestgarth moved this from Todo to In Progress in Core Kanban Apr 25, 2024
@vega-issues vega-issues moved this from In Progress to Waiting Review in Core Kanban Apr 26, 2024
@vega-issues vega-issues moved this from Waiting Review to Approved in Core Kanban Apr 26, 2024
@github-project-automation github-project-automation bot moved this from Approved to Merged in Core Kanban Apr 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arbitrum feature new feature to be developed spike technical research typically required to prove a concept, validate an approach or better understand
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant