fix: use parent timestamps for activation boundaries#3697

Closed

0x00101010 wants to merge 17 commits into

200msfrom

fix/parent-timestamp-semantics

Commits on Jun 22, 2026

perf(load-tests): pipeline B20 grant, mint, and burn submissions (#3641)

wlawt
and
OpenCode
authored
feat(consensus): Add Upgrade Countdown Metric (#3688)
refcell
authored
Add shared transaction event foundation (#3628)
niran
authored
feat(trie/rocksdb): implement TrieCursor and HashedCursor trait impls (#3576)
meyer9
authored
feat(proof): wire zk host worker loop (#3685)

mw2000
and
Codex
authored
feat(basectl): add txpool commands (#3636)
Pulsator01
authored
feat(upgrade-signal): wire execution upgrade signal observer (#3700)

authored
Prevent stale attestation proofs before registrar submission (#3672)

leopoldjoy
and
OpenCode
authored
refactor(load-test): simplify & harden metric reporting (#3695)
wlawt
authored
feat(trie/rocksdb): implement BaseProofsStore read methods and cursor factories (#3577)
meyer9
authored
fix: use parent timestamps for phase-1 activation checks

0x00101010
and
ampagent
committed
fix: consolidate activation logging semantics

0x00101010
and
ampagent
committed
refactor: simplify upgrade activation logging

0x00101010
and
ampagent
committed
refactor: unify first-block activation checks

0x00101010
and
ampagent
committed
refactor: simplify rollup activation helpers

0x00101010
and
ampagent
committed
refactor: reduce rollup activation helpers

0x00101010
and
ampagent
committed
fix: use safe head timestamp for jovian batch transition

0x00101010
and
ampagent
committed