aere-node

aere-network/aere-node

Fork 0

Commit Graph

Author	SHA1	Message	Date
Aere Network	b7669355eb	Correction 2026-08-19: the per-block Falcon quorum armed at 14,050,000 is retired in the shipped code; what is enforced is the anchor certificate (>=3 of 9 seals every 32nd block). Patches 0003/0004/0005 regenerated with Apache 4(b) notices and upstream headers visible; 0004 message now states the floor fork is active since 10,141,734	2026-08-19 14:14:57 +03:00
Aere Network	600a716070	Patch 0005: the import proof was attempted, and it found what no green test had A from-genesis sync of a patches-only build stopped at block 9,189,161, the futureEipsTime activation, with a stateroot mismatch. Two causes, one patch: upstream bases futureEips on the unreleased amsterdam definition while chain 2800 isolates it on Osaka, and the fleet activates EIP-2935 history storage in the same fork, one system state write per block that a build without this patch never performs. With 0005 applied the same node, same data directory, crossed the activation and keeps importing. The fleet's optional Block-STM wiring is deliberately omitted and the omission is stated in the patch header.	2026-08-15 16:07:02 +03:00

Author

SHA1

Message

Date

Aere Network

b7669355eb

Correction 2026-08-19: the per-block Falcon quorum armed at 14,050,000 is retired in the shipped code; what is enforced is the anchor certificate (>=3 of 9 seals every 32nd block). Patches 0003/0004/0005 regenerated with Apache 4(b) notices and upstream headers visible; 0004 message now states the floor fork is active since 10,141,734

2026-08-19 14:14:57 +03:00

Aere Network

600a716070

Patch 0005: the import proof was attempted, and it found what no green test had

A from-genesis sync of a patches-only build stopped at block 9,189,161, the
futureEipsTime activation, with a stateroot mismatch. Two causes, one patch:
upstream bases futureEips on the unreleased amsterdam definition while chain
2800 isolates it on Osaka, and the fleet activates EIP-2935 history storage in
the same fork, one system state write per block that a build without this
patch never performs. With 0005 applied the same node, same data directory,
crossed the activation and keeps importing. The fleet's optional Block-STM
wiring is deliberately omitted and the omission is stated in the patch header.

2026-08-15 16:07:02 +03:00

2 Commits