š ļø š ļø #Avalanche Durango 4 is out: github.com/ava-labs/avalanchego/releases/tag/v1.11.4 š ļø š ļø
This version (v1.11.4) is backwards compatible to v1.11.0. It is optional but recommended for all node operators.
š Focus: P-Chain Block Cleanup + MerkleDB Memory Optimizations + Interval Tree Bootstrapping
ā
Compatibility Check: VM Interface (v35) ā
Durango 4 does NOT modify the VM interface. If you are running a Custom VM on v1.11.3 (like Subnet-EVM@v0.6.3), it will work with v1.11.4.
github.com/ava-labs/subnet-evm/releases/tag/v0.6.3
š§ P-Chain Block Cleanup š§
During startup, operators will see elevated disk IO for ~15 minutes as P-Chain blocks are rewritten to disk without their accompanying consensus status.
github.com/ava-labs/avalanchego/pull/2869
P-Chain Block Cleanup (cont.)
Because AvalancheGo only writes accepted blocks to disk (as of v1.10.x), there is no need to store the distinction between different types of persisted blocks.
MerkleDB Memory Optimizations
Over the past 2 weeks, ~24 MerkleDB memory optimization PRs have been merged to main (massive shoutout to @stephenbuttolph for driving this).
MerkleDB no longer performs any memory allocations during hashing š
github.com/ava-labs/avalanchego/pull/2902
Interval Tree Bootstrapping
As part of an ongoing effort to reduce Avalanche Mainnet sync times, the legacy jobs queue was replaced with an interval tree that performs much less disk IO during bootstrapping (which is faster š).
github.com/ava-labs/avalanchego/pull/2756
ICYMI there are a TON of interesting ACP convos rn:
* github.com/avalanche-foundation/ACPs/pull/73 ( @AaronBuchwald )
* github.com/avalanche-foundation/ACPs/discussions/68 ( @AaronBuchwald )
* github.com/avalanche-foundation/ACPs/pull/75 ( @joshuagkim )
* github.com/avalanche-foundation/ACPs/discussions/71 ( @Michael_Kaplan1 )
* github.com/avalanche-foundation/ACPs/discussions/69 ( @Abenegia )
You can read the unrolled version of this thread here: typefully.com/_patrickogrady/UKwjrLf