[ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay]

[alex_vigorskiy]

but they do not update several currencies. I asked you this. Not very conscientious.

[seeksilence1]

Lots of information. Just shutdown the pool and wait for the new wallet.

[abraxsis]

but they do not update several currencies. I asked you this. Not very conscientious.

We can't control what Yobit does.

[andresteves]

Thanks for all the info guys. I was about to start mining but decided to have a read first. Glad it pays to read first. Keep up the good work Magi team!

[trader03]

嗨朋友, then could we say that we are in the process of HF right now? since the developers are solving a problem that was encountered in block # 1606986, minerclaim reported that this was the problem of the blockchaim network

 

[cryptonomicon25]

Be patient, everyone. Magi is a great coin with a great team and community so the problems will be fixed as soon as they can be.

[auskevin]

This just gives me a chance to setup for more Mine slaves! 

[blajlehliu]

Be patient, everyone. Magi is a great coin with a great team and community so the problems will be fixed as soon as they can be.

My m-wallet does no longer sync! It is stuck at block number 1606987 generated 5 hours again?

Is it a problem with the network? Is this the HF announced before on this board?

Best

[vicelikedust]

My Wallet too is stuck on 1606987

[joelao95]

We'll publish an updated version in minutes.

[shroomzcoin]

We'll publish an updated version in minutes.

will the mining also be back up or is this just for a wallet fix?

[trader03]

Be patient, everyone. Magi is a great coin with a great team and community so the problems will be fixed as soon as they can be.

My m-wallet does no longer sync! It is stuck at block number 1606987 generated 5 hours again?

Is it a problem with the network? Is this the HF announced before on this board?

Best

Yo creo que ya estamos en pleno proceso de hard-fork.
Estos han sido las últimas noticias en MinerClaim:
Update: 01/06 07:45AM (UTC+1) - Identified an issue on block #1606986 that we can't fix on pool side. This is a blockchain issue. Coin Magi developers are currently working on a fix at that moment.
Update: 01/06 06:30AM (UTC+1) - We are working on fixing the wallet issues on server side.

Las Billeteras están atascadas porque se esta solucionando las fallas justo en estos momentos.

[shroomzcoin]

Be patient, everyone. Magi is a great coin with a great team and community so the problems will be fixed as soon as they can be.

My m-wallet does no longer sync! It is stuck at block number 1606987 generated 5 hours again?

Is it a problem with the network? Is this the HF announced before on this board?

Best

yeah seems there was a problem when reaching the hardfork, fix will be soon, my wallet is stuck on the same block

[111magic]

Magi removed the bug!😉

[jjude80]

Fantastic!!!

[joelao95]

m-wallet version v1.4.5.3

v1.4.5.3
=============
Bug fix in difficulty adjustment algo, i.e., "MagiQuantumWave"; the bug manifests as an improper data conversion when carrying out a time-domain average because of the trival time difference between blocks.

Qt-Wallet and Daemon:

https://github.com/magi-project/magi/releases
http://m-core.org/download/

Source code: https://github.com/magi-project/magi/

Windows: http://m-core.org/bin/m-wallet-1.4.5.3/m-wallet-1.4.5.3-win.zip
Linux: http://m-core.org/bin/m-wallet-1.4.5.3/m-wallet-1.4.5.3-linux.tar.gz
Mac OS X: http://m-core.org/bin/m-wallet-1.4.5.3/m-wallet-1.4.5.3-osx.zip
FreeBSD: http://m-core.org/bin/m-wallet-1.4.5.3/m-wallet-1.4.5.3-freebsd.tar.gz

Latest Block chain (1603558): http://m-core.org/bin/block-chain/


=============
Regarding this version: we have initial scheduled hard fork here: https://asktom.cf/index.php?topic=735170.msg27192013#msg27192013. We passed the fork point but stuck at 1606987; it was found improper data conversion that is used to deal with difficulty adjustment gets zero when handling small number; diff-adjust takes place using average over a time domain. Many blocks emitted between 1606950 - 1606987 causes tiny difference between their block time, that then hits on the bug.

[buckonz]

So v1.4.5.3 is now out. I went through all this pain compiling the previous version.
Can the previous version be "upgraded" it do I need to go through the whole recompile fiasco again?
And If I do need to recompile, do I just do this like the previous version wasn't there, or do I need to "remove" the old version first?

[joelao95]

So v1.4.5.3 is now out. I went through all this pain compiling the previous version.
Can the previous version be "upgraded" it do I need to go through the whole recompile fiasco again?
And If I do need to recompile, do I just do this like the previous version wasn't there, or do I need to "remove" the old version first?

It is compatible with the prior version so you don't remove except running the latest. You can also download binaries.

[realbagdad]

Anyone know a working pool?

[jiyef002]

Thanks for this new version and for your hard work!
Could you please create the tag/release on github so that I can checkout and build on my RPI3?

Thanks!

m-wallet version v1.4.5.3

v1.4.5.3
=============
Bug fix in difficulty adjustment algo, i.e., "MagiQuantumWave"; the bug manifests as an improper data conversion when carrying out a time-domain average because of the trival time difference between blocks.

Qt-Wallet and Daemon:

https://github.com/magi-project/magi/releases
http://m-core.org/download/

Source code: https://github.com/magi-project/magi/

Windows: http://m-core.org/bin/m-wallet-1.4.5.3/m-wallet-1.4.5.3-win.zip
Linux: http://m-core.org/bin/m-wallet-1.4.5.3/m-wallet-1.4.5.3-linux.tar.gz
Mac OS X: http://m-core.org/bin/m-wallet-1.4.5.3/m-wallet-1.4.5.3-osx.zip
FreeBSD: http://m-core.org/bin/m-wallet-1.4.5.3/m-wallet-1.4.5.3-freebsd.tar.gz

Latest Block chain (1603558): http://m-core.org/bin/block-chain/


=============
Regarding this version: we have initial scheduled hard fork here: https://asktom.cf/index.php?topic=735170.msg27192013#msg27192013. We passed the fork point but stuck at 1606987; it was found improper data conversion that is used to deal with difficulty adjustment gets zero when handling small number; diff-adjust takes place using average over a time domain. Many blocks emitted between 1606950 - 1606987 causes tiny difference between their block time, that then hits on the bug.