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

Support full spork history across across HCU version boundaries (PoC) #6540

Open
6 tasks
franklywatson opened this issue Oct 7, 2024 · 0 comments
Open
6 tasks
Labels
Epic Preserve Stale Bot repellent

Comments

@franklywatson
Copy link
Contributor

franklywatson commented Oct 7, 2024

Why

When Flow performs HCU updates the current design of Access Nodes mandates that previous history cannot be served from prior to that version because of the risk of returning different results for older blocks. This limiter to previous spork history is a major issue for EVM users/builders who expect full fidelity access to the spork history regardless of any HCUs.

How will we measure success

  • Changes to enable this deployed on mainnet
  • EVM GW history support works as builders expect

DACI

D: Jordan, Yurii, SCE
A: Alex, Peter
C: Dete
I: Vishal

Problem definition

EVM builders and users cannot tolerate segmented or missing blockchain history and our EVM equivalence credentials require us to hide Flow specific version details from the EVM experience.

Task breakdown

@franklywatson franklywatson added Preserve Stale Bot repellent Epic labels Oct 7, 2024
@franklywatson franklywatson changed the title [Epic] Support full spork history across across HCU version boundaries Support full spork history across across HCU version boundaries Oct 10, 2024
@franklywatson franklywatson changed the title Support full spork history across across HCU version boundaries Support full spork history across across HCU version boundaries (PoC) Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Epic Preserve Stale Bot repellent
Projects
None yet
Development

No branches or pull requests

1 participant