V4.2.0.1

Metrix Core v4.2.0.1

Bugfix Update

This update addresses an issue where the vm.log file can grow to huge sizes if left unattended. The daemon will now trim this file on startup to prevent this excessive bloat.

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

• Added shrink for the vm.log on daemon startup.

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.1.md

Full Changelog: 4.2.0.0...4.2.0.1

---

V4.2.0.0

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.

4.1.1.0

Metrix Core v4.1.1

Bugfix Update

This is a bugfix revision update in response to an issue encountered with sync from genesis once migrated to DGPv2.

Failure to upgrade after activation of MIP3 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

• Bugfix to ensure governance winner validation occurs in contract after the DPGv2 migration.
• Increment version 4.1.1.0

4.1.0.0

Metrix Core v4.1

Major Update

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

Failure to upgrade after activation of MIP3 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
  • In response to a prior issue caused by a bad Governor address that cannot be unenrolled from the contract.
  • Update the DGP Contracts used by the network after a block version consensus vote passes.
• Use newly deployed, updated DGP Contracts across the network after fork.
• Increment version 4.1.0.0
• New protocol version 70023
• Improve sync speed during blocks which require legacy validation lookup
• Corrected subsidy for > 12 year reduction
• Add DGP contracts to getdgpinfo command
• Add Optional usage of blockheight in getdgpinfo command
• Corrected references to Metrix RPC port

• Ensure gov contract verification on these blocks by @nibbles83 in #190
• Governance contract upgrade by @nibbles83, @SeqSEE, @squidicuzz in #191
  • Update qtumDGP.h by @SeqSEE in #192
• Governance contract update by @squidicuzz in #193

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.1.0.0.md

Full Changelog: 4.0.9.1...4.1.0.0

Known Caveats and Details

• Due to the nature of the prior issues encountered within the chain for the Decentralized Governance Protocol; Migrations from DGP version 1 to version 2, are a manual process.

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

FAQ

Why is the migration manual?

Due to the nature of the bug found in the DGPv1 contracts, DGPv1 governors can never be unenrolled automatically. DGPv1 governors can be unenrolled at any time by calling the contracts.

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

Yes! Enrolling in the DGPv2 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 DGPv1 proposals?

Any DGPv1 proposals that have not passed or been completed will need to be re-created in the DGPv2 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.1.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 DGPv2.

When does the upgrade/fork occur?

The fork will occur after 95% of miners/minters have upgraded to Metrix Core version 4.1.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 MIP3 activation.
Once all miners are ready and the upgrade locks in (it takes some time), there will be approximately 2016 blocks before it finally truly activates. Upon activation, the network will switch over to using the DGPv2 contracts, and any peers that are below protocol version 70023 will be disconnected from the network.

---

V4.0.9.1

Mandatory update

• This immediately replaces v4.0.9.0 which contained an unexpected bug. However the release contains the same fixes.

Hardfork Update

• Hardfork - In response to an issue caused by a bad Governor address that cannot be unenrolled from the contract. Fork occurs at 685000, there is also sync fixes to ensure sync from genesis after the bad gov got introduced at block 681822.
• Increment version 4.0.9.1
• New protocol version 70022

Notes

Its expected that between block 681822 and 685000 a full sync will be very slow. This may result in high CPU and if using Altitude, an unresponsive client. Its best to simply wait and let it get past these blocks even if the client appears locked, as the daemon will still be syncing in the background.

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.0.9.0.md

V4.0.9.0

This release has been superseded by V4.0.9.1

V4.0.8.2

Bugfix update

• Bugfix - Prevent staker from also receiving the gov reward, in very rare cases this causes consensus issues and unexpected forks.
• Increment version 4.0.8.2
• New protocol version 70021

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.0.8.2.md

V4.0.8.1

Bugfix update

• Bugfix - Fix random Segfault of wallet caused by inability to get the fee rates from contract
• Bugfix - Fix sync stuck on block 518401 due to unexpected tx in AAL
• Increment version 4.0.8.1
• New protocol version 70020
• Update checkpoints to guide nodes
• Update nMinimumChainWork & defaultAssumeValid

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.0.8.1.md

V4.0.8.0

Bugfix update

• Add checkpoints to guide nodes.
• Fix incorrect subsidy reduction time.
• Add config to bury MIP1 when locked in.
• Port bugfix updates from Qtum 0.19.1.
• Upgrade Metrix core to BTC Core 0.19.1.

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.0.8.0.md

V4.0.7.0

Mandatory Update

Once the MIP1 protocol version update is active, protocol versions prior to 70018 will be disconnected from the network.
MIP1 block signalling starts on 28 August 2021 13:10 GMT, and requires 95% of the blocks created after to lock_in and activate, protocol versions prior to 70018 will no longer be able to sync with updated wallets once this activation occurs.

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.0.7.0.md

This update also includes the return of the Qt wallet for users/developers that require access to contract creation functionality. You will find it in the qt directory within each of the archives below.