š ļø š ļø #Avalanche Cortina 16 is out: github.com/ava-labs/avalanchego/releases/tag/v1.10.16 š ļø š ļø
This version (v1.10.16) is backwards compatible to v1.10.0. It is optional but recommended.
š Release Focus: Optional Tx Indexing on C-Chain + Concurrent Trie Prefetching + Track All Subnet Validator Sets
Compatibility Check: VM Interface (v30)
Cortina 16 does NOT modify the VM interface. If you are running a Custom VM on v1.10.15, it will work with v1.10.16.
Reminder: Check Your Free Disk Space!
Make sure to periodically check how much disk space you have on your Validator and allocate more space if you're running low: docs.avax.network/nodes/run/third-party/aws-node#increase-volume-size
(fixing a Validator that runs out-of-space is harder than increasing space beforehand)
Optional Tx Indexing on C-Chain
Over the last few days, a number of validators reached out wondering if they needed to index the transactions on the C-Chain.
The answer is NO š .
twitter.com/smyyguy/status/1726338591125647496
Optional Tx Indexing on C-Chain (cont.)
With Cortina 16, you can disable transaction indexing by adding the following flag to your Validator's C-Chain Configuration: docs.avax.network/nodes/configure/chain-config-flags#c-chain-configs
{
...
"skip-tx-indexing":true
}
github.com/ava-labs/coreth/pull/399
Concurrent Trie Prefetching
After a series of experiments, @AaronBuchwald/I determined that C-Chain block verification time could be reduced by extending the existing trie prefetcher to concurrently fetch+wait for intermediate nodes before root gen.
github.com/ava-labs/coreth/pull/372
Concurrent Trie Prefetching (cont.)
Following more benchmarking/testing, we plan to upstream this code to go-ethereum: github.com/ethereum/go-ethereum/issues/28266
This approach is similar to the mechanism introduced recently in the MerkleDB (used by the HyperSDK):
twitter.com/_patrickogrady/status/1714401648641298523
Track All Subnet Validator Sets
To improve the performance of #Avalanche Warp Messaging Support on the Primary Network, the Validator Manager was refactored to track all Subnet Validator Sets (instead of computing them on the fly for each msg).
github.com/ava-labs/avalanchego/pull/2253
ICYMI there are now 11 open discussions about different #Avalanche Community Proposals (ACPs).
You can check them out here: github.com/avalanche-foundation/ACPs/discussion
You can read the unrolled version of this thread here: typefully.com/_patrickogrady/qwXldHs