Re: [CGA] Cryptographic Anomaly - MANDATORY UPDATE ON FEB 6th @ 20:00 GMT!!!
I haven`t been getting any payments from p2pool for two hours, but cgminer seems to be working as usual, am I on the wrong chain or what?
Same from Anomalypool. Pool charts are down but haven't flatlined, so I should be getting something.
Sooo does this mean that the AnomalyPool has just decided to stop sending out coins as they're mined until the update? Not meaning to come off harsh, but how can you even think about releasing a mandatory update in a couple hours if you don't have a windows wallet compiled yet?
All three P2Pool nodes including anomalypool pay out per P2Pool protocol, which is that a block found = instant payout. If you're not receiving anything even though you had a share in the payout (see the Payout or Graphs tab on any node) and a block was found, then you're on a different chain.. In that case, try restarting your wallet as described earlier in the thread (make a backup of the data directory, move it out of the way, copy your cryptograhpicanomaly.conf and wallet.dat, make sure you add the nodes from https://bitcointalk.org/index.php?topic=437950.msg4961802#msg4961802).
This did work for me. Shoulda thought of it before.
Thanks.
Did it the third time and it worked, odd.
Just to be sure I did all of it before posting and it didn`t help, repeated all this actions again a moment ago, still got nothing.
Yesterday cryptochomper decieved me with my coins for almost half a day because of that stuck thing and now again. wtf
Yesterday cryptochomper decieved me with my coins for almost half a day because of that stuck thing and now again. wtf
I understand your worries, but we have no chance to make sure that cryptochomper is on the right chain. We already secured the chains around the p2pools, please use only the nodes you'll find in this thread. I'd also suggest to take the node of the p2pool you use as your first "addnode=..." line in your config. Unfortunately there is no way we can make sure that cryptochomper doesn't jump off the chain again.
I used the nodes from this thread and my p2pool node (148.251.15.235) was as the first one in the conf file. Only for the third time clearing the roaming data worked for me, so it`s ok now.