Durango Network Upgrade v1.11.1

Durango Network Upgrade v1.11.1

Metal Blockchain is scheduled to activate the Durango upgrade on May 6th, 2024.

Metal Blockchain is scheduled to activate the Durango upgrade on May 6th, 2024.

Apr 24, 2024

Metal Blockchain is scheduled to activate the Durango upgrade on May 6th, 2024. This upgrade is significant as it introduces several important enhancements to the functionality of the blockchain. In this article, we will delve into the details of these enhancements and their implications.

For validators on Metal Blockchain, it is crucial to take the necessary steps to upgrade your nodes to v1.11.1 before 8 AM UTC, May 6th 2024! To assist you in this process, we have compiled an FAQ at the end of the article, specifically tailored to answer common questions regarding node upgrades.

Cross-Subnet Messaging Activated on Metal C-Chain

This new cutting-edge technology is designed to seamlessly facilitate communication and collaboration across multiple subnets, creating an interconnected environment for cross-chain interactions and is now also activated on the Metal C-Chain.

Now, with Cross-Subchain Messaging, the Metal Blockchain opens up new avenues for decentralized applications and protocols to interact, collaborate, and leverage each other's strengths. The rapid and secure exchange of data and assets across different subnets fosters a dynamic and robust ecosystem, empowering users with greater possibilities and opportunities.

In our blog post on Cross-Subnet Messaging, we will delve deeper into this fascinating new feature.

Activation Of Shanghai EIPs on Metal C-Chain

The Ethereum Improvement Proposals (EIPs) mentioned here were successfully implemented on the Ethereum mainnet during the Shanghai upgrade. The Durango upgrade has also integrated these EIPs into the Metal C-Chain. This approach ensures continued compatibility with existing Ethereum Virtual Machine (EVM) tools, infrastructure, and developer workflows, including Solidity compilation and deployment.

Enable Subnet Ownership Transfer

Subnet operators now have the capability to transfer ownership to a new entity for a variety of purposes. Such transitions could involve implementing periodic rotations of the Subnet's control key(s).

Remove Pending Stakers

Prior to the Durango upgrade, stakers were required to specify a start time for their participation, which imposed a computational burden on the P-Chain.

However, following the Durango upgrade, stakers are automatically initiated upon joining, eliminating the need for manual start times. 

This streamlined approach simplifies system management by eliminating the necessity for validators to continuously perform additional checks. Consequently, validation processes are expedited, enhancing the efficiency of rule enforcement. 

As a result, the waiting list system has been rendered obsolete, marking a significant improvement in the network's operations.

Virtual Machine Application Errors

Virtual Machines (VMs) can construct their own peer-to-peer application protocols using fundamental elements such as AppRequest, AppResponse, and AppGossip.

AppRequest denotes a message type that necessitates a corresponding AppResponse to affirm a successful outcome. However, in scenarios where an AppRequest cannot be fulfilled, there was previously no inherent mechanism for a peer to indicate an error condition prior to the Durango upgrade. 

Consequently, VMs relied on timeouts in such failure instances, wherein a client initiating a request would resort to flagging it as unsuccessful after a designated timeout period had elapsed.

With the implementation of a native application error type within the Durango upgrade, all clients are now assured of receiving an AppError message in response to an unsuccessful AppRequest. This enhancement mitigates the need for clients to depend solely on timeouts, thereby substantially reducing latency in rectifying unsuccessful requests.

Disable AddValidatorTx and AddDelegatorTx

The Banff (v1.9.0) upgrade introduced AddPermissionlessValidatorTx and AddPermissionlessDelegatorTx to the Metal Blockchain, enabling Subnet creators to activate Proof-of-Stake validation using their own token on their Subnet.

These new transaction types offer functionalities similar to AddValidatorTx and AddDelegatorTx but come with additional fields. AddPermissionlessDelegatorTx includes a Subnet field alongside the existing fields found in AddDelegatorTx. Similarly, AddPermissionlessValidatorTx includes Subnet and Signer fields in addition to the fields present in AddValidatorTx. 

Furthermore, RewardsOwner has been divided into ValidationRewardsOwner and DelegationRewardsOwner, allowing validators to channel rewards from delegators separately.

By discontinuing support for AddValidatorTx, new validators on the Primary Network are required to use AddPermissionlessValidatorTx and register a BLS key with their NodeID. 

As more validators adopt BLS keys, future upgrades leveraging these keys can be activated through the ACP process. BLS keys facilitate efficient signing of a common message via Public Key Aggregation, enabling various applications such as:

  • Arbitrary Subnet Rewards: Elastic Subnets can define their own reward curve and conditions with sufficient BLS key adoption, allowing for more flexibility in reward distribution.

  • Subnet Attestations: Elastic Subnets can provide attestations of their state using BLS Multi-Signatures, enabling clients to access Subnet information without syncing the entire Subnet. This can be particularly useful for Subnet-Only Validators to demonstrate information about the C-Chain.

Validator FAQ

Do I have to upgrade my node?

Yes, it is essential to upgrade your validator to  v1.11.1 before the Mainnet activation date, May 6th, 8AM UTC. Failure to upgrade may result in your node being marked as offline, which can have a negative impact on both your staking rewards and the rewards of your delegators. This is because other nodes will report lower uptime for your node, potentially leading to decreased rewards for all parties involved.

How do I upgrade my node?

To upgrade to MetalGo v1.11.1, you can follow the same process as any other upgrade. If you build from source, run the build script as you normally would. If you use pre-compiled binaries, invoke them as usual. If you use the installer script, continue using it as before.

Once you have started MetalGo v1.11, there is no further action required. For more detailed information on updating your node, you can refer to our upgrade guide. It is also recommended to have a backup of your staking key/certificate and BLS key as a best practice.

Are there any changes in hardware requirements?

No, there are no changes in hardware requirements for this update.

Will updating decrease my validator's uptime?

No, updating to v1.11.1 will not impact your validator's uptime.

Featured In

Featured In

Blockchain for Banks.

A BSA-Compliant, Layer 0 Blockchain for Finance.

in support of Metal Blockchain.

© 2024 Metallicus, Inc. All rights reserved.

Blockchain for Banks.

A BSA-Compliant, Layer 0 Blockchain for Finance.

in support of Metal Blockchain.

© 2024 Metallicus, Inc. All rights reserved.

Blockchain for Banks.

A BSA-Compliant, Layer 0 Blockchain for Finance.

in support of Metal Blockchain.

© 2024 Metallicus, Inc. All rights reserved.