Add network upgrade config #3207
Conversation
aaronbuchwald
force-pushed
the
refactor-upgrade-schedule
branch
from
d6720a2
to
a2ffd04
Compare
|
This is failing due to https://github.com/ava-labs/coreth/pull/613/files#r1694251921 |
|
I think that 1) passing the full upgrade struct around as needed instead of individual upgrade times including adding it to |
aaronbuchwald
requested review from
danlaine,
joshua-kim and
StephenButtolph
as code owners
There was a problem hiding this comment.
how do we pass this new config to VMs? For instance Subnet-EVM also has a overridable config that depends on avago's values for networks. I'm not sure if this is strictly required to be correctly supported since this is only for custom networks (I assume for testing).
There was a problem hiding this comment.
I think we can even disable this option if we're running any subnet.
There was a problem hiding this comment.
This will be added to the snow.Context in a followup.
…nchego into refactor-upgrade-schedule
Co-authored-by: Stephen Buttolph <stephen@avalabs.org>
This PR replaces the constants/per-networkID getter functions for network upgrade timestamps with a network upgrade schedule struct and a single function to retrieve the corresponding upgrade schedule.