š ļø š ļø #Avalanche Durango 2 is out: github.com/ava-labs/avalanchego/releases/tag/v1.11.2 š ļø š ļø
This version (v1.11.2) is backwards compatible to v1.11.0. It is optional but strongly recommended for all node operators.
š Focus: Redesign Push Gossip on the X/P/C-Chain
š§ Compatibility Check: VM Interface (v34) š§
Durango 2 adds support for message-specific gossip parameters to the VM interface (used in the push gossip redesign).
If you run a Subnet, you must update your VM to v34 for v1.11.2 compatibility.
Last week, there was a "Block Finalization Stall" on the Avalanche Mainnet where a bug led to each node saturating their stake-weighted bandwidth allocation on peers with useless transaction gossip (preventing consensus messages from being processed).
status.avax.network/incidents/qmx0s7zk6gkm
Following the recovery of block finalization, the Platform Group at @AvaLabs shipped a full redesign of the gossip mechanism used in the P2P SDK (used in the X/P/C-Chain).
github.com/ava-labs/avalanchego/pull/2772
This new mechanism relies more heavily on transaction issuers to propagate transactions they care about through the network instead of validators. It takes inspiration from the optimization work that went into the Avalanche HyperSDK and Vryx.
hackmd.io/@patrickogrady/rys8mdl5p
Note to Operators:
Validators should see a reduction in AppGossip egress bandwidth and anyone running a Public API will see an increase in AppGossip egress bandwidth.
If you want to learn more about these changes (outside of what is detailed in the related PRs), stop by the next Avalanche Developer Community Call (which should happen next week).
Last but certainly not least, make sure your nodes are updated for the upcoming Durango Upgrade on 3/6. To avoid downtime (and potential loss of staking rewards), make sure to upgrade **BEFORE** the activation time:
twitter.com/_patrickogrady/status/1760421358612390132?s=20