-
Notifications
You must be signed in to change notification settings - Fork 932
fusaksa-devnet-2 clean up and fixes
#7722
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
fusaksa-devnet-2 clean up and fixes
#7722
Conversation
d8a3429 to
c84b1d3
Compare
|
Some required checks have failed. Could you please take a look @jimmygchen? 🙏 |
98bc903 to
86cebb6
Compare
|
@pawanjay176 I've addressed the comments and fixed the tests 🤞 Please re-review, thanks! |
| chain_spec.deneb_fork_epoch = Some(Epoch::new(4)); | ||
| chain_spec.electra_fork_epoch = Some(Epoch::new(5)); | ||
| chain_spec.fulu_fork_epoch = Some(Epoch::new(6)); | ||
| chain_spec |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
might be good to assert that the latest fork's fork_epoch is set or we will need to remember to update this for each fork
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added in 555fb61
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Thanks
Issue Addressed
Clean ups for #7655, mostly just adding doc comments and small refactors, no functionality change.
The original PR renamed some of the
fork_*field names todigest_*, e.g.digest_epoch,duration_to_next_digestetc - it reads a bit strange at first, BPO forks are technically still hard forks - I think calling them forks instead of digests are a bit easier to understand. But I'd like to hear thoughts before proceeding with making this change.