While in the past, Keystore API was already safeguarded against such attacks using a username and password combination, this new change extends protection to other private APIs, including the Admin API
Disclaimer: Cortina 3 does not alter the VM interface.
This means if you're currently operating a Custom VM on v1.10.1, rest assured it will seamlessly work with the new v1.10.3.
Introduction of Push Query on Build
This update ensures that push queries, which disseminate information about the block a node is investigating, are exclusively sent by the block builder.
This strategic move drastically minimizes the transmission and reception of superfluous… twitter.com/i/web/status/1…
In the past, AvalancheGo used to dispatch a PushQuery every time it authenticated a new block, targeting 10 validators chosen based on stake weight.
However, it was frequently observed that the peers receiving the block gossip from AvalancheGo already possessed the block. This… twitter.com/i/web/status/1…
- Build Elimination of VersionDB from MerkleDB
We've made a significant change in our database management - VersionDB has been removed from MerkleDB.
Previously, MerkleDB used to record all pending writes into an instance of the VersionDB to ensure write atomicity. However,… twitter.com/i/web/status/1…
For a more detailed understanding, check out the pull request here:
This is part of our continuous efforts to streamline and optimize Avalanche's operations.
We've carried out a vital update concerning the retrieval of BLS Keys in the platformvm.GetValidatorSet.
In the past, if a validator chose to unstake and then restake within a certain time frame, the platformvm.GetValidatorSet would fail to return a BLS key for that particular… twitter.com/i/web/status/1…
For a more comprehensive understanding, you can review the pull request at this link:
This bug had the potential to hinder a Subnet from verifying a new AWM (liveness), although it wouldn't have permitted incorrect verification of an AWM (safety).
This issue came to light during the finalization of Teleporter, our solution for EVM<>EVM AWM support.
@chainlink functions allow anyone to connect a smart contract to any Web2 API, unlocking a new frontier of Web3 and Web2 integrations
And they are live on the @avax Fuji testnet - let’s dive into what you can build 👇
Previously, Web3 developers couldn't connect their smart contracts to existing Web2 APIs, and Web2 developers couldn't leverage their existing infrastructure when building a Web3 app
Chainlink Functions aim to solve this issue.
Smart contract developers in the Avalanche ecosystem can now use Chainlink Functions to connect Web2 APIs and cloud services in their smart contracts
Chainlink Functions also act as a decentralized compute runtime to test, simulate, and run custom logic off-chain for Web3… twitter.com/i/web/status/1…
In our journey around the world of @avax, we are constantly being introduced to new revolutionary technological primitives that it’s hard to keep track
Let’s delve deeper into the novel blockchain communication system introduced back in Banff 5 - Avalanche Warp Messaging (AWM)
Imagine a world where the Avalanche network is the entire globe, and the subnets are individual countries, each with their own unique culture, rules, and language
Within these countries, there are cities, which represent different blockchains operating each with their own openly… twitter.com/i/web/status/1…
In the past, if one country (subnet) wanted to communicate or trade with another, they had to build a bridging solution
This was like constructing a massive international highway or a transcontinental railway - a huge, costly, and time-consuming project
Avalanche consensus is the most fast, scalable, secure, and energy efficient Consensus mechanism out today
Let’s play a game to visualize how it works 👇🏽
Imagine we're playing a game, and in each round of this game, each player (which we'll call a 'validator') has to ask a few other players (let's say, K players) about their preferred choice
The players they ask are chosen randomly from all the players, but those with more… twitter.com/i/web/status/1…
Now, let's use a visual example
Think of a group of 64 players, who have to choose between the colors Blue or Yellow
The number of players each validator asks (the K we talked about) is 5 - Let's zoom in on the player in the top left corner, who initially prefers Yellow
This version maintains backward compatibility with v1.10.0 but while optional - upgrading is highly recommended.
This release includes major improvements to P-Chain API Latency. It has seen significant reductions, with platform.getStake latency reduced by a whopping 90%!
This is due to substantial enhancements in P-Chain caching, boosting the efficiency and response times of P-Chain APIs.
The X-Chain migrating to Snowman++ moves the entire network to a single consensus engine, enabling faster development and more broadly-applicable innovation.
The linearization of the X-Chain unblocks the integration of Avalanche Warp Messaging (AWM) and makes it much easier for exchanges to support the X-Chain, which will contain many of the staking tokens used on Elastic Subnets.