You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* chore: MadhugiriPro hf
* params: use stable tag
* chore: set new HF heights
* Reinforce Precompile Check on any new HF (ethereum#1881)
* Include missing check of P256 on Amoy (ethereum#1877)
* checks p256 instruction
* lint fix
* reinforce precompilers check
---------
Co-authored-by: Lucca Martins <[email protected]>
// If this test failed, it likely means a new HF were introduced and is very likely that PreCompiles got changed (by introducing new ones, changing olds ones or removing).
464
+
// Please follow the instructions here to properly handle this new HF
465
+
//
466
+
// 1. Make sure if p256Verify were properly set on this Hardfork, it was introduced by us in PIP-27
467
+
//
468
+
// 2. Double check all the changes on the preCompiles of the current HF and the new one.
469
+
// You should also pay attention for any params changes like in &bigModExp{eip2565: true, eip7823: true, eip7883: true}
470
+
// Make sure all changes reflects the Ethereum's new proposals while reflecting the changes we did internally. Currently just PIP-27
471
+
//
472
+
// 3. Check if Erigon reflects the exact same configuration for the PreCompiles, including also the same params for precompiles
473
+
//
474
+
// 4. Runs a e2e test which includes all the preCompiles in a single transaction. If a new preCompile were introduced, please reflect the new one on the tests
475
+
// The test must run on a multiclient network, including both Erigon and Bor. The test is available in our e2e repository.
476
+
//
477
+
// 5. After all checks done, you can increase insert the NewHF on the expected list to make the test pass
0 commit comments