Skip to content

chore(seismic)!: bump enclave, seismic-reth and summit to current heads - #82

Merged
samlaf merged 1 commit into
seismicfrom
sl/bump-enclave-reth-summit
Oct 19, 2026
Merged

samlaf merged 1 commit into
seismicfrom
sl/bump-enclave-reth-summit

Conversation

@samlaf

@samlaf samlaf commented Oct 19, 2026

Copy link
Copy Markdown
Contributor

seismic-reth bc40907 brings stock Ethereum headers (seismic-reth#512): timestamp is unix seconds and the sub-second part is the first two bytes of extraData. That changes the genesis hash, which is the !. The dev genesis it ships starts extraData with 0x0000, which the new reth requires, and no longer activates Osaka (seismic-reth#513).

The other two pins follow it:

  • summit 69ca74d (summit#469) drives reth's Engine API with stock payloads, through reth-seismic-engine-types pinned at seismic-reth#512.
  • enclave a87993e: enclave#291 makes the admission freshness gate read reth's finalized header timestamp as seconds. With the old enclave the new timestamps would read as stale, and with the new enclave the old ones as always fresh. enclave#281 comes with it: GCP TDX admission. The Azure verification path is unchanged, but the attestation service now resolves its platform from DMI at start and fails closed if DMI names none.

sources.yaml's header now records both pairings.

Every flag reth.service and summit.service pass still exists at the new revs, and summit's genesis schema is unchanged.

seismic-reth bc40907 brings stock Ethereum headers (seismic-reth#512):
`timestamp` is unix seconds and the sub-second part is the first two
bytes of `extraData`. That changes the genesis hash, which is the `!`.
The dev genesis it ships starts `extraData` with 0x0000, which the new
reth requires, and no longer activates Osaka (seismic-reth#513).

The other two pins follow it:
- summit 69ca74d (summit#469) drives reth's Engine API with stock
  payloads, through reth-seismic-engine-types pinned at
  seismic-reth#512.
- enclave a87993e: enclave#291 makes the admission freshness gate read
  reth's finalized header timestamp as seconds. With the old enclave the
  new timestamps would read as stale, and with the new enclave the old
  ones as always fresh. enclave#281 comes with it: GCP TDX admission.
  The Azure verification path is unchanged, but the attestation service
  now resolves its platform from DMI at start and fails closed if DMI
  names none.

sources.yaml's header now records both pairings.

Every flag reth.service and summit.service pass still exists at the new
revs, and summit's genesis schema is unchanged.
@samlaf
samlaf requested a review from a team as a code owner October 19, 2026 14:23
@samlaf
samlaf merged commit e52ce15 into seismic Oct 19, 2026
5 checks passed
@samlaf
samlaf deleted the sl/bump-enclave-reth-summit branch October 19, 2026 14:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant