🌀 Welcome to the #Avalanche Interoperability Age 🌀
Today, the pre-release code for a proposed upgrade to the Avalanche Network (AWM Support on C-Chain) was published and will activate on the Fuji Testnet at 11 A.M. ET on Tuesday, February 13th, 2024.
github.com/ava-labs/avalanchego/releases/tag/v1.11.0-fuji
This proposed upgrade, codenamed Durango, consists of Avalanche Community Proposals (ACPs):
[23] P-Chain Native Transfers: github.com/avalanche-foundation/ACPs/blob/main/ACPs/23-p-chain-native-transfers.md
[24] Activate Shanghai EIPs on C-Chain: github.com/avalanche-foundation/ACPs/blob/main/ACPs/24-shanghai-eips.md
[25] Virtual Machine Application Errors: github.com/avalanche-foundation/ACPs/blob/main/ACPs/25-vm-application-errors.md
[30] Integrate Avalanche Warp Messaging into the EVM: github.com/avalanche-foundation/ACPs/blob/main/ACPs/30-avalanche-warp-x-evm.md
[31] Enable Subnet Ownership Transfer: github.com/avalanche-foundation/ACPs/blob/main/ACPs/31-enable-subnet-ownership-transfer.md
[41] Remove Pending Stakers: github.com/avalanche-foundation/ACPs/blob/main/ACPs/41-remove-pending-stakers.md
[62] Disable `AddValidatorTx` and `AddDelegatorTx`: github.com/avalanche-foundation/ACPs/blob/main/ACPs/62-disable-addvalidatortx-and-adddelegatortx.md
You can read more about the proposed Durango Upgrade here:
avax.network/blog/durango-avalanche-warp-messaging-comes-to-the-evm
As a reminder (have heard some confusion about this lately), AWM messages are not sent through the P-Chain.
The P-Chain just serves as a key registry that is used by nodes to lookup signers for a source Subnet to verify messages (from their local database).
Here is a good diagram that explains AWM from a presentation I gave at the @initc3org Winter Retreat in January 2023:
(Message delivery/signing % is up to the Subnets to specify...all AWM is concerned with is verifying that signers from one Subnet authenticated a message)
You can read the unrolled version of this thread here: typefully.com/_patrickogrady/jGYfnjR