You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The content you are editing has changed. Please copy your edits and refresh the page.
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
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
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
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
The text was updated successfully, but these errors were encountered: