Skip to content
This repository has been archived by the owner on Jun 9, 2022. It is now read-only.

Capture state changes resulting from hard forks #8

Open
brianmcgee opened this issue Feb 6, 2020 · 0 comments
Open

Capture state changes resulting from hard forks #8

brianmcgee opened this issue Feb 6, 2020 · 0 comments
Labels
Priority: Critical Size: Atomic An atomic piece of work with a single associated PR Status: Available Type: Bug Something isn't working

Comments

@brianmcgee
Copy link
Member

There are certain state changes as a result of hard forks that we currently do not capture. An example would be the refunds introduced in block 1.92 million for the DAO issue.

We need a strategy to define and emit the hard coded state changes at a given block. There is a similar pattern worth reviewing which is already implemented within Besu for handling protocol changes at specific blocks.
@brianmcgee brianmcgee added Priority: Critical Status: Available Type: Enhancement Improvements or additions Type: Bug Something isn't working and removed Type: Enhancement Improvements or additions labels Feb 6, 2020
@brianmcgee brianmcgee added the Size: Atomic An atomic piece of work with a single associated PR label Apr 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Priority: Critical Size: Atomic An atomic piece of work with a single associated PR Status: Available Type: Bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@brianmcgee