Topic: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] - page 481. (Read 2375638 times)
Where linux version? No new release on github.
its upto 3980 now but wont go past it
Same problem here
its upto 3980 now but wont go past it
Same problem here
its upto 3980 now but wont go past it
i did
Hmm ok. Looks like Joe mentioned block 1443980.Iam updating also at this moment. Will see if it works for me.
i did
new wallet wont sync past 1443963
Follow the steps above from dev Joe than i will be ok! Good job, joe!
The pool http://104.207.149.217 is back to normal.
Cleaned the database to remove the bad blocks.
Well done Seeksilence. Good things pools are coming back online! The pool http://104.207.149.217 is back to normal.
Cleaned the database to remove the bad blocks.
new wallet wont sync past 1443963
Good job, joe!
The pool http://104.207.149.217 is back to normal.
Cleaned the database to remove the bad blocks.
The pool http://104.207.149.217 is back to normal.
Cleaned the database to remove the bad blocks.
Thanks Joe for the quick fix.
Any chance a win 32 version will soon be out? Most of the time I stake on a win 7 32bit laptop.
Have to say this event was educational for me as I learned a new term.
Never had heard of splitting before but it makes sense.
Any chance a win 32 version will soon be out? Most of the time I stake on a win 7 32bit laptop.
Have to say this event was educational for me as I learned a new term.
Never had heard of splitting before but it makes sense. Hey Guys,
I'm pretty green to all of this. I've noticed that none of my pool miners have been working the last few days. Can someone explain what's up? I see some commotion going on here, but I can't quite make it out.
... The other side of this is that my POS mining has been going nuts ( in a good way) for the last day, and I see the word "reversing" thrown around here quite a bit. So is this a too-good-to-be-true thing and it'll get reversed, or whats up? genuinely confused over here lol.
I'm pretty green to all of this. I've noticed that none of my pool miners have been working the last few days. Can someone explain what's up? I see some commotion going on here, but I can't quite make it out.
... The other side of this is that my POS mining has been going nuts ( in a good way) for the last day, and I see the word "reversing" thrown around here quite a bit. So is this a too-good-to-be-true thing and it'll get reversed, or whats up? genuinely confused over here lol.
What happened is the block chain started spitting (forking) and the pools and exchanges shutdown the coin pending a fix.
Reversing means the block chain will be rolled back to prior to the splitting. This means that all transactions that took place after that point will in essence be erased.
Hope this helps you understand whats going on.
The wallet has been synchronized，
Good job Joe. Really fast done! Awesome
Thanks Joe!!
Any 32bit version?
Any 32bit version?
The wallet has been synchronized，
We updated the wallet version to v1.4 to enable a fix to the splitting. I'll give more description regarding the fix. There is splitting around block 1443980; it wasn't confirmed that is necessary a fork from pool, as the inconsistent block is a PoS block based on a comparison of two chains available. Given that, the fix is to start from that point. Procedure to startup on a clean chain:
1) Download the wallet v1.4.0 (will push other versions into that):
http://coinmagi.org/bin/m-wallet-1.4.0/
2) Backup wallet.dat;
3) The prior blockdata must be removed before launching the new wallet:
Remove everything under the Magi or .magi folder except for wallet.dat:
Windows: %appdata%\Magi
Linux: ~/.magi
4) If you wish to redownload blockchain from scratch, skip to 7)
5) Download block chain from:
http://coinmagi.org/bin/block-chain/
and unzip the file;
6) Place all of the contents under "m-blockchain" into Magi or .magi;
7) Launch the new wallet.
Source:
https://github.com/magi-project/magi
I'll update relevant docs and web once I get a chance back on the stuffs, and some more descriptions.
Nodes:
1) Download the wallet v1.4.0 (will push other versions into that):
http://coinmagi.org/bin/m-wallet-1.4.0/
2) Backup wallet.dat;
3) The prior blockdata must be removed before launching the new wallet:
Remove everything under the Magi or .magi folder except for wallet.dat:
Windows: %appdata%\Magi
Linux: ~/.magi
4) If you wish to redownload blockchain from scratch, skip to 7)
5) Download block chain from:
http://coinmagi.org/bin/block-chain/
and unzip the file;
6) Place all of the contents under "m-blockchain" into Magi or .magi;
7) Launch the new wallet.
Source:
https://github.com/magi-project/magi
I'll update relevant docs and web once I get a chance back on the stuffs, and some more descriptions.
Nodes:
Code:
connect=104.128.225.215
connect=216.189.151.56
Personally I am strongly against a hard fork to revert the split in principle. Is there no way just to role out the fix on top of the current chain?
F/D: I mined a few of those 43 XMG blocks
F/D: I mined a few of those 43 XMG blocks
That seems the way to go for a reverse. I'll post updates soon.
Personally I am strongly against a hard fork to revert the split in principle. Is there no way just to role out the fix on top of the current chain?
F/D: I mined a few of those 43 XMG blocks
F/D: I mined a few of those 43 XMG blocks
Something happened at block 1444278 it seems.
My daemon and backup daemon crashed at that block, likely someone is trying to fool around which a manipulated (stake) block
I can/will reopen the pool once the daemon is fixed
My daemon and backup daemon crashed at that block, likely someone is trying to fool around which a manipulated (stake) block
I can/will reopen the pool once the daemon is fixed
Thanks, we'll get back ASAP.
Please post some info what is the plan. Thx.
There was a splitting in the chain. We'll reverse to where it happened. The reason is that after splitting, there are local network mining within which coin generation has been raised up quite a lot since the difficulty cannot catch up the global network that should be excluded. We're testing the fix and should be able to post it out soon.
To All,
Let me know your concern regarding the above plan.
Good plan
Thank you!
I do agree on this.
Remember this coin is for everyone and it need to be equal for everyone to be able to get it.
Therefore I think it is absolute most correct to revert back to where the issue started so none have a benifit out of the error.
And Joe, of course I hope that the fix can prevent such issue in the future too.
Joe, what will happen with, for example, these adresses:
9QXx6w1CHeGL9RiVQCtUuPkktGoBywds4M
9RmhVZoWDfqNotHMoepE3ErZ4iWMGZMc1J
9QJrYit43h2mwy774nk3Fhkv3AQgSqfNPA
https://www.mupload.nl/img/erxsctzysfjov.jpg
Those 43.245 blocks are from mining.
They are from : https://chainz.cryptoid.info/xmg/#!extraction
9QXx6w1CHeGL9RiVQCtUuPkktGoBywds4M
9RmhVZoWDfqNotHMoepE3ErZ4iWMGZMc1J
9QJrYit43h2mwy774nk3Fhkv3AQgSqfNPA
https://www.mupload.nl/img/erxsctzysfjov.jpg
Those 43.245 blocks are from mining.
They are from : https://chainz.cryptoid.info/xmg/#!extraction
Blockchain will start again from block where multiple split was (around 1444k block). Those tx will not exist in new chain.
Jump to: