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

[goldlabel]

Joe is testing the changes he made and if thats all oke you guy`s will be the first to know

[1714525840]

1714525840

[frphm]

A bit off topic, but why are you guys here and not on Slack? It's so much easier to have a conversation on there.

[111magic]

A bit off topic, but why are you guys here and not on Slack? It's so much easier to have a conversation on there.

Thats right. But for me i use bitcointalk for some time and its easy for me. Slack i need to learn more about it.
 

[GKar]

A bit off topic, but why are you guys here and not on Slack? It's so much easier to have a conversation on there.

I need an invite for slack. 

This forum here is still a good place for info.

[111magic]

A bit off topic, but why are you guys here and not on Slack? It's so much easier to have a conversation on there.

I need an invite for slack. 

This forum here is still a good place for info.

If you send me your email PM i will send invite tonight

[goldlabel]

WOW 1 BTC = $4086.0675 how high will Bitcoin go

[xinwao]

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

Thanks, we'll get back ASAP.

Please post some info what is the plan. Thx.

[joelao95]

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

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.

[starmman]

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

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.

The solution sounds fine to me Joe - thanks for looking into it at the weekend =)

[xinwao]

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

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.

Thank you

[goldlabel]

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

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.

Sounds like a great plan

[Vitalik_Pedik]

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

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.

Thank you for your work.
This fix you make, will it eliminate possibility of future splitting?

[The Frisian]

Something happened at block 1444278 it seems.
We'll reverse to where it happened.

Frow when will it reversed, Bittrex send me some coins on block 1444311



--

[yate]

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

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!

[111magic]

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

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!

Good idea Joe! I say lets go for it!

[marauder093]

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.

[The Frisian]

Joe, what will happen with, for example, these adresses:

9QXx6w1CHeGL9RiVQCtUuPkktGoBywds4M
9RmhVZoWDfqNotHMoepE3ErZ4iWMGZMc1J
9QJrYit43h2mwy774nk3Fhkv3AQgSqfNPA




Those 43.245 blocks are from mining.

They are from : https://chainz.cryptoid.info/xmg/#!extraction

[Vitalik_Pedik]

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

Blockchain will start again from block where multiple split was (around 1444k block). Those tx will not exist in new chain.

[tommyrsk]

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

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!

Good idea Joe! I say lets go for it!

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.

[K1lo]

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