Joe probably not getting enough sleep this days... Im glad i opted to keep the connect argument on my config file. If the pool im on fall of the chain im gonna shift to solo mining again to support the coin
Yes very good. Indeed lots of work last days for our dev. No time for sleeping. |
|
|
|
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.
Blockchain data is here (block #1447972): http://coinmagi.org/bin/block-chain/Wallet version 1.4.1.1 is fine: http://coinmagi.org/bin/m-wallet-1.4.1.1/https://github.com/magi-project/magi/releasesI you like to search for the right posts fast use this https://bitcointalk.org/index.php?action=profile;u=182342;sa=showPostsThose are directly from the dev. |
|
|
|
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/#poolsLook 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. Use one of those 3 pools. Other pools still needs to adjust the blockchain. |
|
|
|
3 days ago was the last time when I sync the wallet, right now it says is 1800 blocks behind and it stays there, no progress at all with the same wallet which work 3 days ago. I tried also the 1.4.2 wallet and same thing. I see people here they sync the wallet but why is not working for me ? I tried everything what says here in the last 20-30 posts.
Did you adjust the magi.conf with connect=104.128.225.215? If not try that and restart wallet! |
|
|
|
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.
But 2 biggest pools have wrong chain.. it is strange Working very hard to reach everybody to adjust it. Any idea about bittrex? I sent them a message with all new links & info. Hope they will respond or adjust asap. |
|
|
|
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.
But 2 biggest pools have wrong chain.. it is strange Working very hard to reach everybody to adjust it. |
|
|
|
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.
Here on of Joe's posts again! |
|
|
|
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 |
|
|
|
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/#poolsLook 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. |
|
|
|
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. |
|
|
|
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. |
|
|
|
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. |
|
|
|
Hello, I deleted the whole blockchain folder and let the wallet sync with only "connect=104.128.225.215" in the magi.conf file and now it seems fine, the last block number is the same for my wallet, poolinfo.systms.org and the block explorer. The wallet didn't show my 100 xmg transaction, the very first transaction in this wallet, when I open it on my desktop. The wallet run on my server, and in the block explorer i can see he staked 2 times today but my desktop only show the last one. My xmg are still here, no loss for me, only a bug with my wallet file maybe, I restored the backup I made when I created this wallet and tried the repairwallet command but nothing. I hope all this things are over and Magi will continue to grow, thank you for all your works this last days and the coming days  You are welcome Elar. Reminder never stake during wallet sync! I also learned that today! |
|
|
|
...
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!
...
perfectly can anyone support you in this? Does this mean there won't be another fork soon? I do not know, no one knows I just wonted to donate some coins to support sorry for my English Thats very friendly. Because its not allowed to post addresses here in the posts on Bitcointalk i added a XMG & BTC address donation in my signature. |
|
|
|
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. Received already some claims. Best thing is send them directly to me. I will look into it. |
|
|
|
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.
as I written in my mail to you, please tell me the time you have mined this coins and which timezone you are. I will check our database against this. We are really not interested in taking user coins and stay in contact to the Coin Magi dev nearly nonstop to report and fix issues as soon as possible. In general for us it is not a worthwhile business running the pool. I think we have much more costs to our infrastructure which is not only one simple small server some people may think. We are just normal humans who works 40 hours per week and do this in our free time. In the last 19 hours we received 39 mails from users we all have answered. However, I can understand your current situation. We do not have to send you the time of mined coins, time zone, etc. just check your database since 08/11/2017 and paid the earnings the miners did (mi user is lhedwin, and mi email is lhedwin@outlook.com). The magi team do not have to pay for you. i send a email to youand your answer was "yes, we have a problem", but no solution. No need to talk about this. Magi team will work on the compensates. For the pools it was also a difficult period & Magi team is happy no pool said bye to Magi. We appriciate their work. Lets look at the future together. |
|
|
|
Give the team little time to adjust all websites, forums etc. And all remember only use links from official posts. Using other links will be at own risk!!! |
|
|
|
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. |
|
|
|
Here are some official posts! |
|
|
|
|
Show Posts
