🌀 The Avalanche Interoperability Era Starts at 11 AM ET on 3/6 🌀
Today, the production code (AvalancheGo@v1.11.0) for the proposed Durango Upgrade was published. If sufficient stake supports Durango, it will activate on Mainnet at 11 AM ET on Wednesday, March 6th, 2024.
Durango contains ACPs that are not compatible with < v1.11.0 (Cortina).
If Durango activates and you do not upgrade your node **before** the activation time, your node will be unable to process new blocks and will be marked as offline by other nodes (impacting uptime).
🚧 Compatibility Check: VM Interface (v33) 🚧
Durango introduces VM Interface v33. If you are running a Subnet, make sure to upgrade your Custom VM to v33 (subnet-evm@v0.6.0) before running it with v1.11.0.
You can download the Durango release here: github.com/ava-labs/avalanchego/releases/tag/v1.11.0
You can learn more about Durango here: avax.network/blog/durango-avalanche-warp-messaging-comes-to-the-evm
You can track support for ACP-23, ACP-24, ACP-25, ACP-30, ACP-31, ACP-41, and ACP-62 (included in Durango) on @snowpeerio:
snowpeer.io/acps
If you run a node on Fuji and already upgraded to v1.11.0-fuji, you should upgrade your node to v1.11.0 by **11 AM ET on Wednesday, March 6th, 2024**.
The production release (v1.11.0) contains some optimizations and fixes found during the Durango activation on Fuji that activate at the same time as the Mainnet activation.
If you run a Fuji Subnet, please wait for the subnet-evm@v0.6.0 release to upgrade your nodes to v1.11.0 (the VM Interface, as mentioned above, is now 33).
ICYMI AvalancheJS@v4 is now out (includes some massive performance upgrades and support for BLS staking transactions):
twitter.com/dhrubabasu_/status/1758224145916326318?s=20
You can read the unrolled version of this thread here: typefully.com/_patrickogrady/OJQotli