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

EVM Gateway Hardening #6539

Open
1 of 11 tasks
Tracked by #6577
j1010001 opened this issue Oct 5, 2024 · 0 comments
Open
1 of 11 tasks
Tracked by #6577

EVM Gateway Hardening #6539

j1010001 opened this issue Oct 5, 2024 · 0 comments
Assignees
Labels
Execution Cadence Execution Team

Comments

@j1010001
Copy link
Member

j1010001 commented Oct 5, 2024

Why (Objective)

  • We need to stabilize the EVM GW - it intermittently stops ingesting blocks and need to be restarted manually, after oncall is alerted.
  • The demands on EVM GW are growing as more partners are onboarding to FLOW. The EVM GW is relying on Access and Execution nodes to get execution state data, executing trace calls and getting debug traces, which is inefficient (was implemented as short-term work-around) and pushes ANs and ENs to their limits. We need to enable partners to run their own EVM GW with customs config, so we can take the load from the ANs and ENs by enabling dry-run on the EVM GW itself. EVM GW implementing dry-run also enables partners to customize the GW to provide only those debug tracers they require for their workflow.

How will we measure success (Key Results) ?

  • EVM GW runs without block ingestion stalls for 4 weeks.
  • Dry-run - ANs and ENs are no longer loaded by dry-run & other queries / calls.
  • Enables adding custom debug_trace to the EVM GW when re-executing Txs.
  • Alexar is able to deploy [30] their own GWs with minimal support from FF.
  • Alchemy endpoints are unblocked after the dry-run is deployed on FF-run GW.

Effort Estimate

DACI

EVM GW stabilization

Role Assigned
Driver Technical: @janezpodhostnik , EM: @j1010001
Approver @Kay-Zee
Consulted @ramtinms, @zhangchiqing, @peterargue
Informed Flow Protocol engineering

Dry-run feature

Role Assigned
Driver Technical: @ramtinms, EM: @j1010001
Approver @dete
Consulted @zhangchiqing, @peterargue, @janezpodhostnik
Informed Flow Protocol Engineering

Stabilization

  1. Bug
    janezpodhostnik

Dry-run (reducing the GW dependency on the AN)

  1. Compatibility EVM Feature
    m-Peter
  2. Feature Feedback

Operationalizing the EVM GW for partners

  1. franklywatson vishalchangrani
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Execution Cadence Execution Team
Projects
None yet
Development

No branches or pull requests

4 participants