L1BlockInfoTx
for a new Hardfork.
This example is very verbose.
To grok required changes, view this PR diff
which introduces Isthmus hardfork changes to the
L1BlockInfoTx with a new variant.Required Genesis Updates
The first updates that need to be made are tokona-genesis
types, namely the RollupConfig and HardForkConfig.
First, add a timestamp field to the RollupConfig. Let’s use the
hardfork name “Glacier” as an example.
RollupConfig to provide a way of checking whether the
“Glacier” hardfork is active for a given timestamp. Also update the prior hardfork
accessor to call this method (let’s use “Isthmus” as the prior hardfork).
HardForkConfig.
Protocol Changes
Introduce a newglacier.rs module containing a L1BlockInfoGlacier type
in kona_genesis::info module.
This should include a few methods used in the L1BlockInfoTx later.
L1BlockInfoEcotone
for reference.
Next, add the new “Glacier” variant to the L1BlockInfoTx.
L1BlockInfoTx::try_new to construct the L1BlockInfoGlacier
if the hardfork is active using the RollupConfig::is_glacier_active.
Also, be sure to update L1BlockInfoTx::decode_calldata
with the new variant decoding, as well as other L1BlockInfoTx
methods.
Once some tests are added surrounding the decoding and encoding of the new
L1BlockInfoGlacier variant, all required changes are complete!
Now, this example PR diff introducing the Isthmus changes should
make sense, since it effectively implements the above changes for the Isthmus
hardfork (replacing “Glacier” with “Isthmus”). Notice, Isthmus introduces
some new “operator fee” fields as part of it’s L1BlockInfoIsthmus type.
Some new error variants to the BlockInfoError are needed as well.