Topic: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] - page 433. (Read 2375995 times)

I stop mining after the early morning fork on m-hash.com. Yesterday my wallet went to a fork, over the night I did full blockchain download. I will just keep my wallet open to see if stays on the chain if I'm doing nothing (not mining, not staking) and I will let you know.

I stopped mining to the magi chain , The roll back if that what you think it needs who am i say,  I off course dont like the fact that yet again I lose all my coins yet again  but if the only way is for that to happen then i support it, I dont have a clue where it should be rolled back to Im  sure all mine will be gone so either way Hopefully it save everyone elses. Ill try again when the network is back up, i hope your able to save most peoples coins. I keep an eye out I hope it goes well for the community

I'm quite new to this project (actually I joined right after all the forking issues so I didn't understand why my miner wasn't connecting to any of the pools ..). But this project helped me to start  to explore the world of blockchain, mining, PoW, PoS and a lot of other things.

As I'm still a rookie, what would a rollback exactly mean? Would we lose all coins generated from when the forking issues started until now? Or there is only a change in code required to fix all upcoming (new) mining while previous progress is kept?

I honestly belief that whatever change is required to stabilise the coin, should be done. Even if that means we'd lose progress from the previous week. I really like the setup and idea behind this coin so I'd like to see it work properly again such that I can continue to learn .
Anyways, just my two cents

Final question: Is it safe to transfer coins which are 'Confirmed' in the different pools to our private wallets? Or they'll get lost due to the forking?

Good luck on solving this issue!

if there would be a roll over i suggest it would be from the this point on where you made an announcement otherwise plenty would be disappointed throwing their hash rates when we were not even sure if we would get rewarded.

i was just beginning to edit my conf file to accommodate all my devices but since its adviced to stop mining i will mine on another cpu coin im mining. ill monitor this thread and come back mining when adviced.

u can rollover back its ur coin... but...
what did cause this fork in the first place?
its will be fork again?
what will happend to our wallets balance?
and the mined stuck coins in pool´s wallet?



P.D. my wallet fully synchronized to 1450139 block at this moment

To ALL,

The fork takes place from one pool to another, and that I believe something fundamental needs a clarification as we haven't seen this before. This has messed around the mining. I suggest stop mining at this time until we firstly 1) get a keep-it-going solution, and 2) root cause finding and a solution to the fork. The mining just going on, unfortunately, doesn't make sense to me, and I would propose a rollover back to a fair point. Let me know if rollover sounds good to you, and where you want to startover.

down goes the chain again.  Bittrex hasn't confirmed any of my transactions in 2 days even with everything synced and recovery of lost coins from a prior blockchain now, I can't move funds around, and this ends up making it so I can't sell XMG.  This is not ok.


Warning: coin magi down again just now

I think ZPool is on fork too.

EDIT: Nope, just slow AF with syncing the network.

just to chime in again thanks for all the work the devs are doing  and the pools I appreciate all the work that you are putting in to get the chain stable I just wanted to ensurte that im not adding to the issue I have a 4 core cloud server running at the pool http://104.207.149.217, I have it configured to ruin with the bat file setup as ./m-minerd  -a m7mhash -o stratum+tcp://104.207.149.217:3333 -u username -p password -t 4
  
here is my hash
[2017-08-22 05:42:22] thread 4: 82472 hashes, 4.75 khash/s
[2017-08-22 05:42:22] accepted: 19/19 (100.00%), 35.40 khash/s (yay!!!)
[2017-08-22 05:42:35] thread 0: 141486 hashes, 4.79 khash/s
[2017-08-22 05:42:35] accepted: 20/20 (100.00%), 36.03 khash/s (yay!!!)
[2017-08-22 05:42:41] thread 7: 181460 hashes, 4.56 khash/s
[2017-08-22 05:42:41] accepted: 21/21 (100.00%), 35.98 khash/s (yay!!!)
[2017-08-22 05:42:42] thread 6: 244642 hashes, 4.48 khash/s
[2017-08-22 05:42:49] thread 0: 62817 hashes, 4.65 khash/s
[2017-08-22 05:42:49] accepted: 22/22 (100.00%), 36.24 khash/s (yay!!!)
[2017-08-22 05:42:51] thread 2: 258408 hashes, 4.70 khash/s
[2017-08-22 05:42:51] thread 4: 138293 hashes, 4.79 khash/s
[2017-08-22 05:42:51] accepted: 23/23 (100.00%), 36.67 khash/s (yay!!!)
[2017-08-22 05:42:53] thread 4: 11381 hashes, 5.09 khash/s
[2017-08-22 05:42:53] accepted: 24/24 (100.00%), 36.98 khash/s (yay!!!)
[2017-08-22 05:42:54] thread 2: 17316 hashes, 5.03 khash/s
[2017-08-22 05:42:54] accepted: 25/25 (100.00%), 37.32 khash/s (yay!!!)
[2017-08-22 05:42:55] thread 4: 7890 hashes, 5.17 khash/s
[2017-08-22 05:42:55] accepted: 26/26 (100.00%), 37.39 khash/s (yay!!!)

I'm still pretty new  but i do realize if I am adding to the issue i'm hurting my self as long with others so if you thing this is causing a problem let me know m,y computer is down right now so hence the cloud I'm only going to have it for a another couple days,  so if you  believe this has anything to do with the forking give me a holler  Thanks  all

Yes.
Forked again.

Can anyone please help me with ZPOOL? What should be the perfect code to run it?

-o stratum+tcp://.mine.zpool.ca: -u [-p c=,]

Is this how it should be filled up?
-o stratum+tcp://m7m.mine.zpool.ca:6033 -u [-p c=XMG,]

I insert my wallet address, but this is little confusing for me; those '[]'??!? I run it with the perfect details and I get an error.

We are just running through pools.

Thank You!

edit I: Bittrex says : Wallet Offline - Dev requested maintenance

edit II: Got it working. Thanks! The code, I am talking about. Not the wallet or anything else.

The code that I am using :
m-minerd.exe -o stratum+tcp://m7m.mine.zpool.ca:6033 -u 9EqEpwyBneF2qRw6pNQfuJXAvbvBAXtkgr -p c=XMG
Perfect? Or needs any thing to add to it?

On fork.

http://pom.m-hash.com/index.php

Thanks Myrth888 for your post.

Bittrex responded on our request.
Wallet in offline for maintenance!

I know some are getting frustrated mining when all this fork is happening but in my experience im actually getting more than a days worth of reward even from all this forking unless the pool itself decides to wipe all your hashes without letting them sort of if it was orphaned or not. I do wish it would be fixed soon, kinda getting tired wiping the blocks to resync and all but mining part is not a total loss and actually gaining.

I hope pools just try their best to reset and stay on the right chain so it will give their miners enough rewards even if they get some orphaned blocks. If your frustrated you saw a lot of coins orphaned because it was on the wrong block, normally you wont really be able to find that much coins so you didnt really loose that much coins. Because of all the forks happening botnets or big rentals are not really mining much at the moment and rewards are maxed or near max so if you can manage to stay on the right chain for even a few hours you would have gotten enough coins for a regular day of mining.

anything found before the fork will be ok. after the fork it will be orphaned

What about the block that found before ? It's gonna orphaned again ?

xmgpool is on another fork. You'd better use other pool right now.

I just restarted it. I do not know when it will have another fork.

XMGPool down again. 

i got the 2 core i7 model from 2011 somewhere. dno if its worth setting it up tho.

Yeah, 4 threads 100% load

not bad.. how much cpu load? 100%