Here is the Exact message on Bitcointalk. It seems that they have indeed disabled the wrong coin. LOL
Re: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay]
December 30, 2017, 06:28:57 AM
Reply with quote #21545
m-wallet version v1.4.5.1
Hard fork will take place at block #1606950. See below for the details of hard fork.
Qt-Wallet and Daemon:
https://github.com/magi-project/magi/releaseshttp://m-core.org/download/http://m-core.org/bin/m-wallet-1.4.5.1/Source code:
https://github.com/magi-project/magi/Windows:
http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-win.zipLinux:
http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-linux.tar.gzMac OS X:
http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-osx.dmgFreeBSD:
http://m-core.org/bin/m-wallet-1.4.5.1/m-wallet-1.4.5.1-freebsd.tar.gzBlock chain:
http://m-core.org/bin/block-chain/v1.4.5.1
=============
This release schedules a hard fork at block #1606950 as a solution to the current mining issue that miners cannot mine blocks:
- The PoW / PoS block generation rule is disabled.
- Difficulty adjustment algo switches back to MQW at #1606948.
- Block drift time is limited within 5 min.
- Remove IRC and add DNS seeds.
Quick guide:
- Windows: unpack the files and run the wallet directly;
- Mac OS: unpack the files and copy to the Application folder, and then run the wallet directly;
- Linux: unpack the files and run the wallet directly.
Quick startup I (without touching the block-chain):
0) Backup wallet.dat;
1) Launch the new wallet.
Quick startup II (replacing the block-chain):
0) Backup wallet.dat;
1) Download block-chain data from here:
http://m-core.org/bin/block-chain;2) Delete all of the contents under the .magi (unix-like system) or Magi (OS X or Windows) folder, except for wallet.dat and magi.conf;
3) Unzip the file and copy the folders under "m-block-chain" into the .magi (unix-like system) or Magi (OS X or Windows) folder;
4) Launch the new wallet.
Note to v1.4.5.1
---------------------
v1.4.5.1 is compatible with the current block chain.
Things explained..
Firstly, I admit what's going on isn't good to the situation, and I do see there are needs of further works to fulfill the purpose of the coin.
There is no rollback. I learned few requests about actions on the miners who mined (future) blocks that the generic miners can't mine, and for that, rollback is one of the approaches. However, taking into account the overall situation that time to time transactions are involved, especially exchanges, there will be more damage to the coin when we cease the chain or perform a rollback.
As explained shortly in previous post, what happens is associated with the PoW / PoS rule in combination with the fact that 2-hour future blocks allowed as in the original design. I do see in this rule weakness because of the PoW block generation capable of being on a 10-min pattern without the PoS blocks. The another feature of MAGI's network that is intentionally kept at low hash rate comes a likability that one with a reasonable amount hash can launch a future block attack, the chance of this is increased by a fact that generic users can't make valid blocks owing to the PoW / PoS rule; these blocks are supposed to reset the block time.
By overviewing the situation, I see there is a difficulty in maintaining low-hash rate network, as individuals can always acquire big hash rate. In contrast, advantage lies in a network with huge amount of hash that individuals can't compete with. Nevertheless, it's not our intention to compromise the purpose because of the weakness. The PoS is supposed to dilute such weakness; I'm seeing the merit of the PoW / PoS rule when used beautifully. We shall make efforts on this aspect.
Let us know any questions / suggestions.
