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

[s0litaire]

Blockchain snapshot as follows:

https://m-core.org/bin/block-chain/m-block-chain-1813042.zip
https://m-core.org/bin/block-chain/m-block-chain-1813042.tar.gz

should we use this chain from now on or is it just for the tests of the new client 1.4.6.1?

For now I'm just using it for the test build, I've backed up everything just in case.

[1714882774]

1714882774

[1714882774]

1714882774

[1714882774]

1714882774

[1714882774]

1714882774

[WaifusAreLove]

Same.

And it is mining not minging xD

(Warning at the client)

[Iame3]

Blockchain snapshot as follows:

https://m-core.org/bin/block-chain/m-block-chain-1813042.zip
https://m-core.org/bin/block-chain/m-block-chain-1813042.tar.gz

Deleted old data, unpacked this one, synchronized. >200 XMG lost    How to fix?

[txwooley]

Same problem here.  Went from 206 XMG to 15 XMG.  I loaded a wallet backup from last week and only lost about 8 XMG.  Still frustrating.

[WaifusAreLove]

They mentioned a split in the chain a few posts before, probably your xmg was on the other chain and not in the current one.

[djm34]

Same problem here.  Went from 206 XMG to 15 XMG.  I loaded a wallet backup from last week and only lost about 8 XMG.  Still frustrating.

checkwallet, repairwallet (had the same issue with coins sent to myself for staking) if those coins weren't mined on the "wrong" fork (ie older than a day and half)

checkwallet showed the disvrepencies,
repairwallet (then restart the wallet) corrected the problem

[Iame3]

They mentioned a split in the chain a few posts before, probably your xmg was on the other chain and not in the current one.

Several months old coins on the other chain???  

[Iame3]

Same problem here.  Went from 206 XMG to 15 XMG.  I loaded a wallet backup from last week and only lost about 8 XMG.  Still frustrating.

checkwallet, repairwallet (had the same issue with coins staking) if those coins weren't mined on the "wrong" fork

How to use it, I could not find documentation? Edit: OK, wrote this in console, repaired, restarted the wallet, thanks, coins are back

[djm34]

Same problem here.  Went from 206 XMG to 15 XMG.  I loaded a wallet backup from last week and only lost about 8 XMG.  Still frustrating.

checkwallet, repairwallet (had the same issue with coins staking) if those coins weren't mined on the "wrong" fork

How to use it, I could not find documentation?

in the wallet, go to console and you need to type the commands
checkwallet then repairwallet (if checkwallet shows a problem)
there is also help command, which doesn't give much info tbh

[Jeremy450]

has anyone noticed
Minerclaim and xpoolx is on block 1813585

but wallet and other pools are on 1813645???

[djm34]

has anyone noticed
Minerclaim and xpoolx is on block 1813585

but wallet and other pools are on 1813645???

edit: minerclaim is on block 0... guess they can't be wrong with that

anyone knows which are the nodes of the wallets of the pools ?

[Vitalik_Pedik]

Joes node (104.128.225.215) continuously rewriting blocks, try to fight with my actions probably, but I am not doing anything for 12H+
Bad triggered algo)

Advice to all, especially for pools and POS miners: write "connect=104.128.225.215" to magi.conf to have only one connection to true chain. If you will have many connections, splitting will continue due to rewritings on Joes node.

[djm34]

Joes node (104.128.225.215) continuously rewriting blocks, try to fight with my actions probably, but I am not doing anything for 12H+
Bad triggered algo)

Advice to all, especially for pools and POS miners: write "connect=104.128.225.215" to magi.conf to have only one connection to true chain. If you will have many connections, splitting will continue due to rewritings on Joes node.

actually I tried, it doesn't even stay connected

[Vitalik_Pedik]

Joes node (104.128.225.215) continuously rewriting blocks, try to fight with my actions probably, but I am not doing anything for 12H+
Bad triggered algo)

Advice to all, especially for pools and POS miners: write "connect=104.128.225.215" to magi.conf to have only one connection to true chain. If you will have many connections, splitting will continue due to rewritings on Joes node.

actually I tried, it doesn't even stay connected

First download clean chain from link he posted. If it not help, probably ip ban (also fail) triggered. For example, one of my IP banned same way and can't directly connect to 104.128.225.215 node.

[Vitalik_Pedik]

About 100 blocks was deleted right now from dev node.

[djm34]

About 100 blocks was deleted right now from dev node.

some of which I mined... thanks our great dev

This is by the strangest coin ever, with a dev come and clean what he doesn't like...

[Vitalik_Pedik]

About 100 blocks was deleted right now from dev node.

some of which I mined... thanks our great dev

This is by the strangest coin ever, with a dev come and clean what he doesn't like...

And I donated to him, I am complete idiot)

[jonathin.r]

The dev node and two other pools (pom-m-hash.com and magi.trasmamod.com) seem to be in sync, but CryptoID seems to be about ~10 blocks ahead.
--

[bogec]

Why the heck would you use the chain provided by Joe and the single node from him for regular use and mining when it was clearly stated by him that it is ONLY for test use.
Get your act together guys and stop complaining till there is a fix and clarification over the chain.
And all this to fix the f..k up made by Vitalik. So try not to lose this info from sight.

[djm34]

Why the heck would you use the chain provided by Joe and the single node from him for regular use and mining when it was clearly stated by him that it is ONLY for test use.
Get your act together guys and stop complaining till there is a fix and clarification over the chain.
And all this to fix the f..k up made by Vitalik. So try not to lose this info from sight.

this the regular blockchain and regular node... not the test stuff. The real question is why he isn't asking to use testnet...
so tests are made on some nodes on the main net and he is asking people to help (while half the people "helping" will just mess up...).
This is a recipe for disaster... 

wondering how this coin has been able to survive 4 years with such practices