Scheduled: Story Mainnet & Aeneid – Upgrade story-geth to v1.1.1 for Prague fork activation

Scheduled Maintenance Report for QuickNode

Completed

The scheduled maintenance has been completed.

Posted Jun 26, 2025 - 12:56 UTC

In progress

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Posted Jun 26, 2025 - 12:00 UTC

Scheduled

We will be upgrading our story-geth clients on both the Story Mainnet and Aeneid to version v1.1.1 on 2025-06-26 at 12:00 UTC.

This upgrade is mandatory to enable support for the upcoming Prague fork, which introduces consensus and EVM-level changes that are not backward compatible. All nodes must be upgraded prior to fork activation to remain in sync with the network.

We are upgrading:
• Mainnet: from v1.0.2 → v1.1.1
• Aeneid: from v1.1.0 → v1.1.1

Failure to upgrade will result in the node falling out of consensus and becoming incompatible with the post-fork network.

⸻

📦 Key changes in this release include:
• Full support for the Prague hard fork
• Updates to protocol rules and transaction processing
• Unified versioning across Mainnet and Aeneid

🔗 Release Notes:
https://github.com/Layr-Labs/story-geth/releases/tag/v1.1.1

⸻

📊 Key changelogs and comparisons:
• 🔄 Mainnet diff (v1.0.2 → v1.1.1):
https://github.com/Layr-Labs/story-geth/compare/v1.0.2…v1.1.1
• 🔄 Aeneid diff (v1.1.0 → v1.1.1):
https://github.com/Layr-Labs/story-geth/compare/v1.1.0…v1.1.1

Posted Jun 19, 2025 - 09:17 UTC

This scheduled maintenance affected: Story (AENEID — JSON-RPC API, AENEID — Websockets API, Mainnet — JSON-RPC API, Mainnet — Websockets API).