taiko-geth v2.7.0

This consensus-sensitive release fixes EIP-4788 system-call handling when building Unzen blocks, aligning block building and import with alethia-reth. It also removes Masaya network support.

Consensus and compatibility

• Run the EIP-4788 beacon-root system call before executing transactions when building Unzen blocks, matching the block import path.
• Set the canonical zero parent beacon root before execution, and reject non-zero roots during block building and header validation.
• Reject Unzen headers with a missing parent beacon root during block assembly instead of filling it in after execution.

These changes prevent state-root mismatches between block building and import when the EIP-4788 beacon-roots contract is present. See #601.

Network support

• Remove built-in Masaya network support, including its chain configuration, fork schedule, and genesis allocation. Masaya (chain ID 167011) is no longer supported. See #598.

Upgrade notes

All node runners still using taiko-geth are strongly encouraged to upgrade to v2.7.0 as soon as possible. This includes nodes deriving blocks from L1, not only block producers. The EIP-4788 fix must be in place before the beacon-roots contract is deployed on your network.

We also encourage all node runners to switch to alethia-reth for ongoing node operation. See the alethia-reth releases and getting-started instructions. If you are not switching immediately, upgrade taiko-geth to v2.7.0 first.

Full changelog: v2.6.0...v2.7.0