https://docs.base.org/base-chain/node-operators/base-v1-upgrade#activation-timeline
https://specs.base.org/upgrades/azul/overview
Hi Base Team,
First of all, huge thanks to the core engineers for working hard on the upcoming Azul (V1) upgrade. The target of 1 Gigagas/s and the architecture consolidation look amazing, and we are super excited to support it!
As a node operator on Base, I’m writing to friendly share some of our operational challenges regarding the activation timeline. We noticed that the target mainnet date has shifted a few times recently—from May 13th to late May, then to the 21st, 28th, and currently marked as "Tentative / TBD".
For us operators, preparing for a protocol-level hard fork requires a lot of coordination, such as planning engineering shifts, scheduling snapshot backups, and testing configurations. When the timeline changes frequently, it creates a bit of planning friction for our DevOps team.
To help us better align our maintenance schedule, could the team kindly share:
Are there any specific technical considerations or findings (like edge cases in TEE/ZK or audit updates) that caused the timeline to adjust?
Do you have a rough estimate on when a finalized activation block height or timestamp might be locked in?
We love being part of the Base ecosystem and just want to make sure our node upgrades go as smoothly and safely as possible. Thanks for your transparency and support!
Best regards,
A Base Node Operator
https://docs.base.org/base-chain/node-operators/base-v1-upgrade#activation-timeline
https://specs.base.org/upgrades/azul/overview
Hi Base Team,
First of all, huge thanks to the core engineers for working hard on the upcoming Azul (V1) upgrade. The target of 1 Gigagas/s and the architecture consolidation look amazing, and we are super excited to support it!
As a node operator on Base, I’m writing to friendly share some of our operational challenges regarding the activation timeline. We noticed that the target mainnet date has shifted a few times recently—from May 13th to late May, then to the 21st, 28th, and currently marked as "Tentative / TBD".
For us operators, preparing for a protocol-level hard fork requires a lot of coordination, such as planning engineering shifts, scheduling snapshot backups, and testing configurations. When the timeline changes frequently, it creates a bit of planning friction for our DevOps team.
To help us better align our maintenance schedule, could the team kindly share:
Are there any specific technical considerations or findings (like edge cases in TEE/ZK or audit updates) that caused the timeline to adjust?
Do you have a rough estimate on when a finalized activation block height or timestamp might be locked in?
We love being part of the Base ecosystem and just want to make sure our node upgrades go as smoothly and safely as possible. Thanks for your transparency and support!
Best regards,
A Base Node Operator