Repository navigation
Conversation
|
@ZhiyuCircle gentle ping on this one when you have time. |
|
One additional regression would help verify the fork wiring, not just the precompile-map branch: the current tests construct Because precompile registration is selected per block, please consider testing a pre-Zero6 block and the first Zero6-active block using chain-spec-derived activation (or the closest integration-level fixture). Zero6 is active from genesis on mainnet, but activated later on testnet and devnet; historical execution of pre-activation blocks must retain the earlier precompile set. This also guards against a future change that accidentally makes PQ registration unconditional. |
|
Thanks, good point. Added |
24e6932 to
ba2a57b
Compare
|
Thanks, this closes the key wiring gap: the test derives Zero6 from the block environment and checks both factory construction paths on either side of the activation boundary. One optional follow-up, if production chain-spec fixtures are readily available, would be to assert the configured boundary for each network (including mainnet’s genesis activation and pre-activation historical blocks on networks where it activates later). That would protect the network schedules as well as the factory wiring; if those schedules are already covered elsewhere, the localdev block-9/block-10 regression looks well scoped for this PR. |
Summary
Testing
Fixes #293