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

[Boocha466]

The last block update occurred 236 minutes ago. Bittrex is silent . Or they also have 520 waiting units.

Can we see what version they use.
I tested Bittrex today and it worked fine. Little slow but it was ok.
Noticed the delay yesterday evening also but this morning it was good again.

Yes, I also saw that it worked! And now it costs 200 minutes. I'll try to get into the sapport.

I try to contact them by twitter. They responded pretty quick and asked me to contact them on slack.
But waiting for invitation now.

I would really appreciate the answer

[Elar]

I understand this is frustrating while this is the situation we have at this moment, and becomes quite most recently. My looking back the chain turns out a lot of PoW blocks mined right after the fork point pointing to one /few miners own considerable hash to push the chain faster than the rest, and I go the direction that the big miners somehow reported by people might be the cause. I'd see this a dilemma we're facing when we try to maintain the whole network hash up to a limit but few parties can bring in huge hash from whichever channels they can acquire. This is the plan we are thinking of to take on at this moment:

1) Please connect to the chain that 104.128.225.215 and poolinfo.systms.org are on. Shortly, I'll get an updated block data / wallet for downloads.

Edit: You can use the block date from here to catch up http://coinmagi.org/bin/block-chain/

Place connect=104.128.225.215 in magi.conf, or

magid -connect=104.128.225.215

2) We will make changes to the PoW ASAP. I must admit and make such a note upfront here that there is no guarantee that we'll be 100% isolated from hard fork, and there is always a probability unless we grow up to a scale that no one can compete the rest in both PoS and PoW. I recognize a weak point that we keep the network hash to a lower limit to favor low-hash miner, and that is where we're suffering from, while I would remain to stay on this.

Please make suggestions.

For the security maybe you can look the komodo project (superNet), I didn't understand all the things they can do but what I've understood is you can build your own coin as a childchain on the komodo network who will be protected by the bitcoin hashrate. I don't really know if this can be compatible with magi and it's feature, it's too technical for me but it sounds great

[ulorentz]

Hi!
Does anyone know why suprnova is still down? Magi seems to work now, and other pools are up.
Thanks!

[what-is-in-it]

folks, just want to highlight the effort and support the Magi team / devs and pools have been providing this last day.
Had reached out to 111Magic for help regarding my claim and the response was quick and they have been kind to compensate from their funds.

Appreciate your support and help! Rare to see devs stand strong behind a coin - shows their commitment and thats where the strength of a coin lies!

Awesome job guys!

[111magic]

folks, just want to highlight the effort and support the Magi team / devs and pools have been providing this last day.
Had reached out to 111Magic for help regarding my claim and the response was quick and they have been kind to compensate from their funds.

Appreciate your support and help! Rare to see devs stand strong behind a coin - shows their commitment and thats where the strength of a coin lies!

Awesome job guys!

Thank you for the nice words.
All remember Magi is still in a recovery period.
Make sure you have made a wallet-backup.
Joe is working very hard to make Magi as strong as our community.

[malafaya]

There we go: network hash rate: 474 Mh/s.
Brace yourselves...

[Windozxpert]

I just got a reply from Minerclaim support. Despite the coins that i have mined previously have been confirmed which at least took 500 blocks to be confirmed and are unlikely from a wrong chain they have confiscated the coins. Please avoid using pools that are dishonest. There are a lot of pools of other pools out there.

To the guys from Minerclaim. Enjoy the coins.

It took a couple of hours, but I just received a manual payout from Minerclaim for just a day or so of work. They do a good job. It' just problematic right now..

[gunka]

I just got a reply from Minerclaim support. Despite the coins that i have mined previously have been confirmed which at least took 500 blocks to be confirmed and are unlikely from a wrong chain they have confiscated the coins. Please avoid using pools that are dishonest. There are a lot of pools of other pools out there.

To the guys from Minerclaim. Enjoy the coins.

It took a couple of hours, but I just received a manual payout from Minerclaim for just a day or so of work. They do a good job. It' just problematic right now..

I still have everything in Unconfirmed and the information about the open blocks has disappeared since the database was rolled back.

[Boocha466]

Bittrex! So he does not get up? I have coins. Who are waiting?

[Myth888]

I just got a reply from Minerclaim support. Despite the coins that i have mined previously have been confirmed which at least took 500 blocks to be confirmed and are unlikely from a wrong chain they have confiscated the coins. Please avoid using pools that are dishonest. There are a lot of pools of other pools out there.

To the guys from Minerclaim. Enjoy the coins.

It took a couple of hours, but I just received a manual payout from Minerclaim for just a day or so of work. They do a good job. It' just problematic right now..

When my confirmed coins was reset i wasnt upset. I simply sent them mail to inform them i lost coins since it is stated that our shares and hash are safe on their website. The response i got after was sorry for the inconvenience and no offer to return the lost coins or even we will try and see what we can do. It was after my 2nd email that they angrily asked me for details after i told them it wasnt acceptable and posted on this forum about it. Im glad you got your coins back though.

As for me i reached out calmly and informed them of my issue. So i shared my story hoping it would at least help others. If they return the coins to everyone including me then ill also share that they did. I already reached out so im not gonna ask them again for just a few coins. They can have it. If they intend to return it they will return it to everyone. Magi team offered to compensate for it but i wont ask Magi team to shoulder for a pool. If indeed the confirmed coins were part of a fork chain I will accept it if it was properly communicated and checked. Not just sorry for the inconvenience dont worry your share from now on will be fine.

[cryptosamuri]

I have been dabbling in crypto-mining over the last year, so imagine my my excitement when all of a sudden i start my miner up to solo mine, and  BAMM  I solve a block then another and befor I know it Im solving left and right. I was jumping out of my seat fricking excited is how excited I was. This slowly turned to puzzled  then curious, finally to worried. As i said ive been around for alittle bit so I knew that I wasnt that lucky and my hash rate isn't really anything to write home to momma about, so I figured I was on the wrong chain. At this point my worry became some thing else call it what you will, At this point my wallet said I had about 1200 dollars worth of xmg in it so I backing up and checking and guarding. Moree importantly i was wishing and praying that what i was afraid of wasnt going to happen.  And of course it did  because it anyone wants a sure bet they should bet on the fact that no matter what i try I will always join at the wrong time or pick the wrong horse to bet on. So as I updated my wallet and saw the enevitability that my 5000 xmg became .98 uncomfirmed , I was to say the least verbally upset enough to make the dogs hide under the table. I wanted peoples heads, I wanted a line to the president and I wanted most of all my funds back.  THen I get on bitcoin Talk and I see that the devs  from Magi coin had the nerve to post
 

  Magi community & friends,

For those who had lost in the past days because of forks on mining or balance, Magi will make out a compensationprogram.

The process will be:

1) Make own claims to Magi
(for example, by sending PM to us) and propose the amount of your loss, along with your main XMG & BTC addresses

2)Magi will collect all the information and come up with a total affordable number for compensation, each one will take a proportional portion. Does not mean 100% but Magi will do whatever they can.

3) This might not be a simple job and will not be finished soon. Magi will need to check the claims. Be smart and add as much info you have like screenshots or other info.

4) Because Magi will do this as goodwill to the awesome Magi community it will keep the right to reject claims if abuse like fake claims might be there. Be fair with this.

5) You can send your PM directly to Joelao95 or me.
Add Claim in the message subject.

6) The total fund for this will be supported by our Magi team. Personal i think its a very nice gesture!
Special thanks during this periode for Joe. Well done!

Last remark:
Send in your claim before 31 august 2017!

Good luck to all! 

This post can be adjust by Magi team if i forgot something. 

Smiley

Well all I can say to that is Awesome of you all to make  a commitment like that to your community, And though I am disheartened it is not by you or your team its just the way things roll. But I do want to thank you, because this gesture means a lot since it restores my faith in people to do what is right when it would be just as easy to do the opposite and be able to walk away with maybe a few dirty looks but not really be blamed. You have made the right choice and I will also Im not going to turn in a claim what happened happened it wasn't your fault. Thank you for giving me a coin I can stand with, well at least once i get some coins mined or saved up I will stand with you. But I think you all are going to be successful and be here awhile so i have time even if it takes me a year thanks again.

[Redrover]

Looks like each pool is on a different block and we are forked again.

[drgauravxmg]

Looks like each pool is on a different block and we are forked again.

Backing up the wallet and running 'repairwallet' on m-wallet console won't work?

[Redrover]

Looks like each pool is on a different block and we are forked again.

Backing up the wallet and running 'repairwallet' on m-wallet console won't work?

We don't know which chain is correct, if your wallet is on the wrong chain, then the backup and repair will be wrong.  Safe thing to do right now is keep it closed until it's resolved again.
I'm not an expert on this, just been my experiences so far.

3 pools are still on the same chain so that might be the correct one
https://poolinfo.systms.org/#pools

[frphm]

This is getting super ridiculous. The dev never posted what caused all this in the first place - I assume because they don't know?

[Redrover]

This is getting super ridiculous. The dev never posted what caused all this in the first place - I assume because they don't know?

I don't know but my guess is this won't be fixed until something is changed with the way PoW and PoS is calculated.  But this is just a guess on my part.

Right now, pom pool, minerclaim, and trashmamod are still sync'd with poolinfo.
Suprnova and xmg pool are on different chains according to poolinfo site.

[starmman]

This is getting super ridiculous. The dev never posted what caused all this in the first place - I assume because they don't know?

I don't know but my guess is this won't be fixed until something is changed with the way PoW and PoS is calculated.  But this is just a guess on my part.

Right now, pom pool, minerclaim, and trashmamod are still sync'd with poolinfo.
Suprnova and xmg pool are on different chains according to poolinfo site.

My guess is that the person with the massive hash rate has so much power that he/she is causing forks as they have too many nodes - the problems stared to happen at around the same time as the hash increase

[oxothuk]

This is getting super ridiculous. The dev never posted what caused all this in the first place - I assume because they don't know?

I don't know but my guess is this won't be fixed until something is changed with the way PoW and PoS is calculated.  But this is just a guess on my part.

Right now, pom pool, minerclaim, and trashmamod are still sync'd with poolinfo.
Suprnova and xmg pool are on different chains according to poolinfo site.

My guess is that the person with the massive hash rate has so much power that he/she is causing forks as they have too many nodes - the problems stared to happen at around the same time as the hash increase

I have hashrate floating value from 4-5 to 18mh/s  at night (europe time ) ,  and mining at zPool..  but don`t know how it can cause forks, because all data goes through the pool and not from separate wallets.



PS:  Zpool seems at wrong chain now

[111magic]

Looks like each pool is on a different block and we are forked again.

Backing up the wallet and running 'repairwallet' on m-wallet console won't work?

We don't know which chain is correct, if your wallet is on the wrong chain, then the backup and repair will be wrong.  Safe thing to do right now is keep it closed until it's resolved again.
I'm not an expert on this, just been my experiences so far.

3 pools are still on the same chain so that might be the correct one
https://poolinfo.systms.org/#pools

Look at this tool and check pools before start mining.
Indeed 3 pools have same chain. He already mentioned the right chain. Magi can not be responsible for mining in the wrong chain after Joe gave the info.

[111magic]

This is getting super ridiculous. The dev never posted what caused all this in the first place - I assume because they don't know?

I don't know but my guess is this won't be fixed until something is changed with the way PoW and PoS is calculated.  But this is just a guess on my part.

Right now, pom pool, minerclaim, and trashmamod are still sync'd with poolinfo.
Suprnova and xmg pool are on different chains according to poolinfo site.

My guess is that the person with the massive hash rate has so much power that he/she is causing forks as they have too many nodes - the problems stared to happen at around the same time as the hash increase

Use the code Joe gave to give power to the chain.
Don't use addnode but connect