PeerDAS gs partial messages timeline

timeline.md

title	sub_title	author
PeerDAS Gossipsub Partial Messages timeline	September 26, 2025	Raúl Kripalani

PeerDAS / Fusaka / BPO planning

Timeline

• Client releases: earliest September 22
• Fusaka fork // Holesky: earliest September 29
• Fusaka fork // Sepolia: earliest October 13
• Fusaka fork // Hoodi: earliest October 27
• Fusaka fork // Mainnet: earliest December 1
• BPO1 // Mainnet: earliest Dec'25
• BPO2 // Mainnet: earliest Jan'26

Source: ethereum/pm#1716

Proposed BPO schedule

Fork	Target	Max
Fusaka	6	9
BPO1	10	15
BPO2	14	21

Partial messages planning

Tentative BPO schedule

Continuing from Fusaka BPO schedule (BPO_next):

Fork	Target	Max	Mainnet deployment	Notes
BPO3	18	24	Feb'26	Small parameter bump to ensure all looks nominal
BPO4	24	32	Mar'26	Probes for bigger increments by enabling larger spikes
BPO5	32	48	Mar'26
BPO6	48	64	Apr'26
BPO7	64	72	Apr'26

Engineering and deployment milestones

Phase	Status	Milestone	Date	Teams
Prototyping	Done	First version of design made public	September 2025	P2P
	Done	Prysm prototype ready	September 2025	P2P
	In progress	Lighthouse prototype ready	October 2025	SP
		Smoke interop tests in small devnets	October 2025	P2P, SP
		Battletesting in large devnet (Prysm + Lighthouse)	October 2025	SSL, PO, P2P, SP
		Iteration and refinements	October 2025	P2P, SP
		Publish final design + results	October 2025	P2P
Implementation		Engine API GetBlobsV3 shipped in all execution clients (*)	November 2025	P2P, EL
		Nimbus / Teku / Lodestar begin implementation	November 2025	ST, CON, CS
		Nimbus / Teku / Lodestar implementations ready	December 2025	ST, CON, CS
		Prysm and Lighthouse production-grade	December 2025	P2P, SP
Testing		Full interop + fusaka-devnet-5 battletesting	December 2025	Everyone
		2 week buffer for fixes	December 2025	Everyone
		BPO_next schedule proposed	December 2025	P2P
Deployment		BPO_next schedule committed	January 2026	Everyone
		All CL client releases shipped	January 2025	Everyone
		BPO_next // Sepolia	+ 1 week	Everyone
		BPO_next // Hoodi	+ 2 weeks	Everyone
Mainnet		BPO3 activates	2026-02-14
		BPO4 activates	2026-03-01
		BPO5 activates	2026-03-15
		BPO6 activates	2026-04-01
		BPO7 activates	2026-04-30

(*) Abandoned PRs already exist for most implementations.

Team legend

• P2P: EF P2P Networking team
• SP: Sigma Prime
• OFL: Offchain Labs
• SSL: Sunnyside Labs
• PO: PandaOps
• EL: All EL teams
• ST: Status
• CON: ConsenSys
• CS: ChainSafe

Risks and timesinks

• October seems quite packed.
• Devconnect / Thanksgiving / vacation, etc. not modelled yet.
  • Marco off: mid October for 1wk; Thanksgiving + Devconnect in November.
• Nimbus / Teku / Lodestar coordination =>
• Kurtosis pain => pairing with SSL (they're well versed in Kurtosis)
  • Specifically implementing the Kurtosis scenarios.

Known unknowns

• Lighthouse implementation timeline => Pawan
  • Mitigate by running Prysm-only large-ish testnets.
• Mainnet propagation data to influence the Kurtosis test scenarios.
• Which Kurtosis test scenarios do we need?
  • Need a scenario spec.