Alleysira abe7ca20a9 fix(network): clear ENR nfd field when no next fork is scheduled during runtime transitions (#9131) ...

No. But related to #9009 and #8996


  - Change the `ForkContext::next_fork_digest()` to return `[u8; 4]` (returning `[0u8; 4]` for "no next fork").
- Update the initialization path and runtime fork transition path accordingly.

Added tests:
- [x] `test_next_fork_digest` — existing test passes with non-Option return type
- [x] `test_next_fork_digest_returns_zero_when_no_next_fork` — init at last BPO fork returns `[0u8; 4]`
- [x] `test_next_fork_digest_zero_after_runtime_transition_to_last_fork` — simulates `update_current_fork` to last fork, then verifies zero


Co-Authored-By: alleysira <1367108378@qq.com>

Co-Authored-By: Alleysira <56925051+Alleysira@users.noreply.github.com>

Co-Authored-By: chonghe <44791194+chong-he@users.noreply.github.com>

2026-06-05 20:16:28 +00:00

..

src

fix(network): clear ENR nfd field when no next fork is scheduled during runtime transitions (#9131)

2026-06-05 20:16:28 +00:00

tests

Rust 1.95 lints (#9142)

2026-04-16 23:50:20 +00:00

Cargo.toml

Update libp2p (#9331)

2026-06-05 14:50:19 +00:00