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
getdgpinfocommand - Add Optional usage of blockheight in
getdgpinfocommand - 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
- 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.