Skip to content

V4.2.0.0
Compare
Choose a tag to compare
@nibbles83 nibbles83 released this 10 Jul 14:37
· 5 commits to master since this release
4.2.0.0
670266c
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Metrix Core v4.2.0.0

Major Update

This is a major protocol upgrade in response to an issue discovered within the (v2) DGP contracts.
This upgrade will enable usage of newly created DGP contracts after consensus is reached.

Failure to upgrade after activation of MIP6 will result in disconnection from the greater Metrix network.

Bug Reporting

Please report bugs using the issue tracker at github: https://github.com/thelindaproject/metrix/issues

How to Upgrade

Shut down Metrix, wait until it has completely shut down (which might take a few minutes
for older versions), then just copy over the appropriate metrixd file.

What's Changed

  • Softfork using BIP9 consensus vote
  • Bugfix to ensure governance winner validation occurs in contract after the DPGv3 migration.
  • Disable legacy validation method once MIP6 activates, this will reduce CPU used by the daemon after the activation block.
  • Increment version 4.2.0.0
  • New protocol version 70026
  • Implementation of MIP4
  • Implementation of MIP5
  • Implementation of MIP6

Wallet

You can find our wallet here: github.com/TheLindaProjectInc/Altitude/releases/latest

Release Notes

For the release notes please see the git repository:
github.com/TheLindaProjectInc/Metrix/blob/master/doc/release-notes/release-notes-4.2.0.0.md

Full Changelog: 4.1.1.0...4.2.0.0

Known Caveats and Details

  • This update will require governors to migrate to the new v3 governance contract to continue receiving governance rewards and participate in budget proposal voting..

  • Please refer to our documentation site for detailed information and instructions regarding the process for migrating a Governor.

FAQ

Will I need to wait for my governor to mature again?

Yes! Enrolling in the DGPv3 contracts will require all new governors to wait for 1920 blocks (~48 hours) to receive governor rewards and 26880 blocks (~28 days) to be eligible to vote on budget proposals or DGP blockchain parameter proposals.

What happens to any DGPv2 proposals?

Any DGPv2 proposals that have not passed or been completed will need to be re-created in the DGPv3 contracts.

If I don't have a Governor, do I have to do anything special to prepare for the fork?

As long as you upgraded your wallet/node and are running version 4.2.x of Metrix Core (or latest Altitude); No, you will not have to do anything else. Your wallet will continue to function as normal before, and after the fork. This should be a seamless upgrade to DGPv3.

When does the upgrade/fork occur?

The fork will occur after 95% of miners/minters have upgraded to Metrix Core version 4.2.0.0 and are signaling to the network a ready status. This is accomplished by a miner minting a BIP9 versioned block which signals the readiness of the node for MIP5 activation.
Once all miners are ready and the upgrade locks in (it takes some time), there will be approximately 6720 blocks before it finally truly activates. Upon activation, the network will switch over to using the DGPv3 contracts, and any peers that are below protocol version 70026 will be disconnected from the network.

Huge thanks to @SeqSEE and @squidicuzz for their work on this.

Contributors

squidicuzz and SeqSEE
Assets 6