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

[111magic]

Network is not down. Transactions are confirming as usual. Just mining and staking are out of normal.
You can still transfer XMG from one wallet to another.

Can someone of the team confirm that we normally can send coins between wallets.
(it only takes a little longer).
Or are these transactions cancelled after the update?
When can we expect things will be normal again?
Please can Joe make a statement of these?

I can confirm that sending coins works. Did a test send from bittrex to one of my address ( https://chainz.cryptoid.info/xmg/block.dws?1597375.htm ) yesterday and now one today sending to 111magic with txid https://chainz.cryptoid.info/xmg/tx.dws?d3682e04de4a7b3917dd500e187b6256840dd1b00c86223446f2747ab0caa064.htm - Would be awesome if 111magic could reply that he actually got those coins here too

It's POS / PoW that is effected currently and the only effect it should have on transactions is the time it takes to confirm those transactions. Instead of normal transaction time it's 6 confirms x 10 min (less if POS block is actually found which has happend from time to time during this period)

Yes that works fine. Received the coins Ex33s!

[Godfather154]

Magi XMG back on bittrex again 
Let´s stay strong during fork and HODL.
Bought Magi in February and 35x in FIAT is amazing. Also can not understand complaints about BTC/XMG, Magi still outperformed BTC since beginning of 2017.
My first post here just want to share my experience with this coin.

[kuasenaga]

Hi, there, well I think this pool is open and mining bullmining!!!Is that Right?

[seeksilence1]

It is useless. A hard fork is coming and those coines mined in that pool will be orphaned.

[deztroyr1]

what exactly will be required from our side after the hard fork? will we have to update our wallets or will we have to resynch the blockchain from scratch?
or... nothing? 

[RoumenL]

I sent my XMG from suprnova to Cryptopia
before about 15 minutes
suprnova say OK
but Crypropia say 0.000000000 :-)
Do I hve to do something else?



aaaa sorry they just come , but are not confirmed ....

[111magic]

I sent my XMG from suprnova to Cryptopia
before about 15 minutes
suprnova say OK
but Crypropia say 0.000000000 :-)
Do I hve to do something else?

Checked incoming transactions on Cryptopia?

[111magic]

what exactly will be required from our side after the hard fork? will we have to update our wallets or will we have to resynch the blockchain from scratch?
or... nothing? 

Yes update wallets & other blockchain links will be available at that moment.

[joelao95]

To All,

We got an issue few days ago, and here I'd make quick overview:

1) I'm getting to a point for an internal test of the fix (tomorrow night); I appreciated those who have helped MAGI on this incident. In case one wish to test or review changes, you can come to Slack; find 111magic (coin_magi_xmg) / ex33s / me there.

This incident has been observed as being related to the Pow / PoS rule in combination with the fact that 2-hour future blocks allowed as in the original design. Addition to this, the new block rule disturbs the difficulty, and this feature of uncertainty seems yet to get around. In observation of the Pow / PoS rule actually not being a major factor fixing the prior chain forking issue, I'd go (temporarily to go permanent upon no upcoming concerns) disable it. In the meantime, we will do a reduction of time drift for the blocks.

2) We try to make a release of the fix within this week. My expectation is that the fix would be like changes implemented such a way that a hard fork is required. Chain downtime or rollback will be avoided as much as possible, and actually I don't see those are necessary. Except for a need of the hard fork to get mining back to normal, this incident seems no influence on things like sending / receiving. Let me know if I missed some thing.
 

[starmman]

To All,

We got an issue few days ago, and here I'd make quick overview:

1) I'm getting to a point for an internal test of the fix (tomorrow night); I appreciated those who have helped MAGI on this incident. In case one wish to test or review changes, you can come to Slack; find 111magic (coin_magi_xmg) / ex33s / me there.

This incident has been observed as being related to the Pow / PoS rule in combination with the fact that 2-hour future blocks allowed as in the original design. Addition to this, the new block rule disturbs the difficulty, and this feature of uncertainty seems yet to get around. In observation of the Pow / PoS rule actually not being a major factor fixing the prior chain forking issue, I'd go (temporarily to go permanent upon no upcoming concerns) disable it. In the meantime, we will do a reduction of time drift for the blocks.

2) We try to make a release of the fix within this week. My expectation is that the fix would be like changes implemented such a way that a hard fork is required. Chain downtime or rollback will be avoided as much as possible, and actually I don't see those are necessary. Except for a need of the hard fork to get mining back to normal, this incident seems no influence on things like sending / receiving. Let me know if I missed some thing.
 

Sounds fine to me Joe - thanks again for all your hard work

[dury10]

hello
2 days ago i had 0.7xx on suprnova and i send it to my wallet and it made the transfer super fast
and later on that day i decided to format my pc so i send all my xmg to my Bittrex wallet and the transfer went ok and i had @ 5min until i was able to use them


can someone tell me what can i make with my backup? because i made a backup to my wallet but i don't find any restore section

[qldbiz]

To All,

We got an issue few days ago, and here I'd make quick overview:

1) I'm getting to a point for an internal test of the fix (tomorrow night); I appreciated those who have helped MAGI on this incident. In case one wish to test or review changes, you can come to Slack; find 111magic (coin_magi_xmg) / ex33s / me there.

This incident has been observed as being related to the Pow / PoS rule in combination with the fact that 2-hour future blocks allowed as in the original design. Addition to this, the new block rule disturbs the difficulty, and this feature of uncertainty seems yet to get around. In observation of the Pow / PoS rule actually not being a major factor fixing the prior chain forking issue, I'd go (temporarily to go permanent upon no upcoming concerns) disable it. In the meantime, we will do a reduction of time drift for the blocks.

2) We try to make a release of the fix within this week. My expectation is that the fix would be like changes implemented such a way that a hard fork is required. Chain downtime or rollback will be avoided as much as possible, and actually I don't see those are necessary. Except for a need of the hard fork to get mining back to normal, this incident seems no influence on things like sending / receiving. Let me know if I missed some thing.
 

Thanks for your hard work as well as everybody else that have been involved !!

Cross fingers it all goes fine.

Q

[111magic]

To All,

We got an issue few days ago, and here I'd make quick overview:

1) I'm getting to a point for an internal test of the fix (tomorrow night); I appreciated those who have helped MAGI on this incident. In case one wish to test or review changes, you can come to Slack; find 111magic (coin_magi_xmg) / ex33s / me there.

This incident has been observed as being related to the Pow / PoS rule in combination with the fact that 2-hour future blocks allowed as in the original design. Addition to this, the new block rule disturbs the difficulty, and this feature of uncertainty seems yet to get around. In observation of the Pow / PoS rule actually not being a major factor fixing the prior chain forking issue, I'd go (temporarily to go permanent upon no upcoming concerns) disable it. In the meantime, we will do a reduction of time drift for the blocks.

2) We try to make a release of the fix within this week. My expectation is that the fix would be like changes implemented such a way that a hard fork is required. Chain downtime or rollback will be avoided as much as possible, and actually I don't see those are necessary. Except for a need of the hard fork to get mining back to normal, this incident seems no influence on things like sending / receiving. Let me know if I missed some thing.
 

Sounds fine to me Joe - thanks again for all your hard work

Awesome Joe thanks for the info!💪

[abraxsis]

hello
2 days ago i had 0.7xx on suprnova and i send it to my wallet and it made the transfer super fast
and later on that day i decided to format my pc so i send all my xmg to my Bittrex wallet and the transfer went ok and i had @ 5min until i was able to use them


can someone tell me what can i make with my backup? because i made a backup to my wallet but i don't find any restore section

Reinstall a fresh copy of the wallet, then shut it down. Find the location of wallet.dat for your system and simply replace the new "wallet.dat" with the backed up version. Then restart your wallet.

[AngryWhiteWolf]

Wallet is under automated maintenance on Bittrex. Was also yesterday if I remember correctly.
Shall I better wait for the new wallet release ?

[dury10]

hello
2 days ago i had 0.7xx on suprnova and i send it to my wallet and it made the transfer super fast
and later on that day i decided to format my pc so i send all my xmg to my Bittrex wallet and the transfer went ok and i had @ 5min until i was able to use them


can someone tell me what can i make with my backup? because i made a backup to my wallet but i don't find any restore section

Reinstall a fresh copy of the wallet, then shut it down. Find the location of wallet.dat for your system and simply replace the new "wallet.dat" with the backed up version. Then restart your wallet.

thanks.
waiting again for all the blocks to be downloaded

Wallet is under automated maintenance on Bittrex. Was also yesterday if I remember correctly.
Shall I better wait for the new wallet release ?

its like this from 16-dec
its working only some hours/day

i feel an explosion coming  soon on Magi (x3 or x5  )

[xpoolx]

Hi

On www.xpoolx.com/magindex.php this night we found a valid block and confirmed. Is it possible? or it's a forked block and wont be valid?

Thanks

[maxeprom]

Hi

On www.xpoolx.com/magindex.php this night we found a valid block and confirmed. Is it possible? or it's a forked block and wont be valid?

Thanks

The magi block explorer shows apparently normal PoW extraction. High reward due to low hashrate.
So, xpoolx's block seems to be valid.

[abraxsis]

hello
2 days ago i had 0.7xx on suprnova and i send it to my wallet and it made the transfer super fast
and later on that day i decided to format my pc so i send all my xmg to my Bittrex wallet and the transfer went ok and i had @ 5min until i was able to use them


can someone tell me what can i make with my backup? because i made a backup to my wallet but i don't find any restore section

Reinstall a fresh copy of the wallet, then shut it down. Find the location of wallet.dat for your system and simply replace the new "wallet.dat" with the backed up version. Then restart your wallet.

thanks.
waiting again for all the blocks to be downloaded

Wallet is under automated maintenance on Bittrex. Was also yesterday if I remember correctly.
Shall I better wait for the new wallet release ?

its like this from 16-dec
its working only some hours/day

i feel an explosion coming  soon on Magi (x3 or x5  )

I would wait till the new wallet is released after the hardfork to download the blockchain, otherwise you might just have to do it again.

[abraxsis]

Hi

On www.xpoolx.com/magindex.php this night we found a valid block and confirmed. Is it possible? or it's a forked block and wont be valid?

Thanks

The dev said that they will try to minimize any roll-back on the chain, but that isn't a guarantee it won't happen. So the block might be valid, it might not be valid, or it might be rolled back. personally, I wouldn't be wasting energy on mining right now since it is unknown what will happen exactly. Just be patient and wait for the hardfork.