mirror of
https://github.com/OffchainLabs/prysm.git
synced 2026-02-13 06:25:06 -05:00
10e73cc7c1
This PR moves consolidation and withdrawal request processing into neutral package: `beacon-chain/core/requests`, such that they can be shared between fork Why? Today our core packages are mixed between two workflows: older forks calling into newer forks, and newer work calling back into older fork code. No matter which direction we settle on long-term, a clear first step is to move shared cross-fork functionality into a neutral place so we can reuse it later such that if fork A and fork B interleave each other, they can become clear abstractions Why git mv wasn’t used for consolidations? Withdrawals lived in a clean, dedicated file so it was moved with git mv. Consolidation logic was interleaved with other Electra code and needed extraction/refactor, so a pure git mv would not have preserved meaningful history
Prysm Testing
Special bazel tags:
"CI_race_detection": Apply this tag to test targets that want to run with race detection in CI.