š ļø š ļø #Avalanche Durango 5 is out: github.com/ava-labs/avalanchego/releases/tag/v1.11.5 š ļø š ļø
This version (v1.11.5) is backwards compatible to v1.11.0. It is optional but strongly recommended for all operators.
š Focus: X/P/C Bootstrapping Optimization + Beta Consolidation + Consensus Engine Fixes
ā
Compatibility Check: VM Interface (v35) ā
Durango 5 DOES NOT modify the VM interface. If you are running a Custom VM on v1.11.3-v1.11.4 (like Subnet-EVM@v0.6.3), it will work with v1.11.5.
github.com/ava-labs/subnet-evm/releases/tag/v0.6.3
X/P/C Bootstrapping Optimization
Durango 5 now fetches blocks in parallel for the Primary Network using an Interval Tree: github.com/ava-labs/avalanchego/pull/2752
Coupled with an improved peer selection algorithm for fetching, this reduces fetch time by 80%: github.com/ava-labs/avalanchego/pull/2946
Beta Consolidation
To prepare for the implementation of Error-Driven Snowflake (as outlined in Frosty), @AaronBuchwald consolidated VirtuousBeta and RogueBeta behind a singular Beta in the consensus engine.
github.com/ava-labs/avalanchego/pull/2949
Consensus Fixes
During a consensus refactor, @stephenbuttolph discovered a bug in the handling of votes (that could lead to some to be incorrectly dropped) and a bug in the handling of block issuance (which could lead to blocking on an already decided block).
Consensus Fixes (cont.)
The fix for the first issue (vote handling) is to ensure we properly track the in-degree of dependencies: github.com/ava-labs/avalanchego/pull/2965
The fix for the second issue (block issuance) is to ensure we abandon decided blocks: github.com/ava-labs/avalanchego/pull/2968
ICYMI Frosty is OUT:
twitter.com/andrewlewispye/status/1785277538803044429?s=46
ICYMI (Bonus): @stephenbuttolph, @AaronBuchwald, and I joined @Lightspeedpodhq to discuss all the architectural changes recently proposed for Avalanche:
twitter.com/Lightspeedpodhq/status/1785350486800969973
You can read the unrolled version of this thread here: typefully.com/_patrickogrady/isPsVCL