Gate BPO hardfork support by L2 block number#121
Conversation
karlb
force-pushed
the
karlb/bpo-hardforks
branch
from
c07fbd5 to
26fe8b4
Compare
See https://github.com/celo-org/celo-kona/actions/runs/21671900641/job/62481683195?pr=121: ``` error[vulnerability]: Integer overflow in `BytesMut::reserve` ┌─ /github/workspace/Cargo.lock:97:1 │ 97 │ bytes 1.11.0 registry+https://github.com/rust-lang/crates.io-index │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected │ ├ ID: RUSTSEC-2026-0007 ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0007 ... ```
This is only a partial revert of ca04a72, but the change described in the title is fully reverted. The BPO-stripping is done by the guest anyway, so we don't have to do it on the host. See also celo-org/celo-kona#121.
There was a problem hiding this comment.
LGTM, I'm wondering if we need to choose BPO activation block to exactly align with the L2 block at which a game is created (e.g. 1800, 3600, ...), so that ideally proving remains successful across all games even during the BPO activation? For example, if one game is for L2 block 120 and the previous game is for 100, and the BPO activation happens on 110, proving for the game targeting L2 block 120 could potentially break, since actually 100 ~ 110 range is not BPO activated but this logic regards the whole range 100 ~ 120 as BPO activated. If it's the case, we need to keep that in mind.
…" (#108) This is only a partial revert of ca04a72, but the change described in the title is fully reverted. The BPO-stripping is done by the guest anyway, so we don't have to do it on the host. See also celo-org/celo-kona#121.
Good point, this really is something to watch out for! |
When Ethereum L1 activates Fusaka, the BPO blob schedule changes the blob base fee calculation. For Celo chains, we missed that and now have to keep using the Prague blob parameters until Jovian activates on L2. This matches celo-org/celo-kona#121. Closes celo-org/celo-blockchain-planning#1301
2 participants
It works on Sepolia if used along with celo-org/op-succinct#107. To test the bpo enabled case, I need a post-Jovian block (e.g. on Chaos).
See also https://github.com/celo-org/celo-blockchain-planning/issues/1301