Topic: âš’[CGA] Cryptographic Anomaly - The Elusive Coinâš’ - page 115. (Read 226291 times)

some quick update: we think that 50.147.39.37 is on the right chain.

anomalypool's chain is the only one with hashpower, sawedoff's node didn't have any. And is down. So his chain is broken anyway.

We can't build a coin on a node which is down.

@awesomeperson451: We have a list of all "old" nodes, checking your finding against it now, thanks!

Guys, I just removed all the addnodes from my .conf file and started the v1.1.1.2 binary with just the hardcoded nodes to connect to. Then I let it connect and typed "getpeerinfo" into the debug console.

I think I found the culprit:




getpeerinfo


15:00:18


{
"addr" : "70.176.73.232:13931",
"services" : "00000003",
"lastsend" : 1391975633,
"lastrecv" : 1391975637,
"bytessent" : 1943,
"bytesrecv" : 14644,
"blocksrequested" : 0,
"conntime" : 1391975633,
"version" : 70002,
"subver" : "/Satoshi:1.1.1.2/",
"inbound" : false,
"startingheight" : 12660,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "64.188.167.211:13931",
"services" : "00000003",
"lastsend" : 1391975661,
"lastrecv" : 1391975663,
"bytessent" : 229,
"bytesrecv" : 8607,
"blocksrequested" : 0,
"conntime" : 1391975661,
"version" : 70002,
"subver" : "/Satoshi:1.1.1.2/",
"inbound" : false,
"startingheight" : 12384,
"banscore" : 0
},
{
"addr" : "162.243.225.132:13931",
"services" : "00000003",
"lastsend" : 1391975691,
"lastrecv" : 1391975869,
"bytessent" : 229,
"bytesrecv" : 7226,
"blocksrequested" : 0,
"conntime" : 1391975690,
"version" : 70002,
"subver" : "/Satoshi:1.1.1.2/",
"inbound" : false,
"startingheight" : 12384,
"banscore" : 0
},
{
"addr" : "50.147.39.37:13931",
"services" : "00000003",
"lastsend" : 1391975697,
"lastrecv" : 1391975704,
"bytessent" : 229,
"bytesrecv" : 8607,
"blocksrequested" : 0,
"conntime" : 1391975696,
"version" : 70002,
"subver" : "/Satoshi:1.0.0.1/",
"inbound" : false,
"startingheight" : 8211,
"banscore" : 0
},
{
"addr" : "68.43.46.243:13931",
"services" : "00000003",
"lastsend" : 1391975949,
"lastrecv" : 1391975974,
"bytessent" : 6515,
"bytesrecv" : 111250,
"blocksrequested" : 0,
"conntime" : 1391975702,
"version" : 70002,
"subver" : "/Satoshi:1.1.1.2/",
"inbound" : false,
"startingheight" : 12713,
"banscore" : 0
},
{
"addr" : "78.130.202.203:13931",
"services" : "00000003",
"lastsend" : 1391975975,
"lastrecv" : 1391975975,
"bytessent" : 5395,
"bytesrecv" : 7531,
"blocksrequested" : 0,
"conntime" : 1391975770,
"version" : 70002,
"subver" : "/Satoshi:1.1.1.2/",
"inbound" : false,
"startingheight" : 12714,
"banscore" : 0
},
{
"addr" : "71.105.130.10:13931",
"services" : "00000003",
"lastsend" : 1391975772,
"lastrecv" : 1391975773,
"bytessent" : 229,
"bytesrecv" : 6925,
"blocksrequested" : 0,
"conntime" : 1391975770,
"version" : 70002,
"subver" : "/Satoshi:1.1.1.2/",
"inbound" : false,
"startingheight" : 12660,
"banscore" : 0
},
{
"addr" : "149.210.168.71:13931",
"services" : "00000003",
"lastsend" : 1391975974,
"lastrecv" : 1391975974,
"bytessent" : 473,
"bytesrecv" : 11981,
"blocksrequested" : 0,
"conntime" : 1391975871,
"version" : 70002,
"subver" : "/Satoshi:1.1.1.2/",
"inbound" : false,
"startingheight" : 12716,
"banscore" : 0
}

problem is 'there aren't known good nodes'
anomalypools nodes chain is different than s4w3d0ff 's.
It's forking, your node is forking too.
My suggestion is getting s4w3d0ff 's node 'good', every other is bad atm.

EDIT : I know anomalypools chain is different because of my 2 coins..

Thanks, I see that now in the payouts...

sawedoff's node is down, we are taking node1.cga.anomalypool.com as main node now.

If you mine on anomalypool.com your mining will count and will be payed out, even if they don't show up in your (forked) wallet!

This is essentially what the new client will do. Everyone's local copy of the blockchain will be wiped, and the client will redownload from known good nodes. Additionally, the new client will reject any connection to the current or previous client to prevent the evil fork monster from spreading to the new client. This is an extreme measure, and it will require EVERYONE to update to continue using CGA.

This is normal p2pool behaviour, even if you don't mine you have "good shares" left you get payed for. So you'll probably get smaller and smaller payouts and in some time they will go to zero.

Would it be helpful if I uploaded the blockchain? (the zipped /roaming directory). I've been mining consistently in anomalypool since yesterday evening.

also i think right behaviour is deleting chain at all nodes only leave s4w3d0ff 's
nodes need to re download chain from s4w3d0ff.
or this broken chain issue will continue.
also wallet must contain only  s4w3d0ff 's node hardcoded.
so things will get fixed..

Ok thanks, BUT...I just reloaded the blockchain again in my Monitoring Wallet (not on the remote Miner) and a whole bunch of coin pieces showed up that were mined over the last Hour...Strange...Maybe it's still mining on a Fork...Unfortunately, I still can't log in to my Remote to see...As of 4 min. ago this Wallet is showing 12699.

i'm loosing my 2 coins mined today with anomalypools nodes..
pool takes coins to itself 

We're testing the new code now. The situation definitely is not 'normal', but we're working on it. s4w3d0ff was in our IRC, but his connection dropped a while ago and he hasn't come back, so his node is offline, but my node is up and on the right chain right now. We're going to be adding AnomalyPool's nodes to the code as seeds in this update, but for now, you can add this node to your client:
node1.cga.anomalypool.com
(node 2 is currently offline, will be back up soon).

Stay tuned....

No, your address shows no shares since 30 to 60 min.

this situation is not seem normal.
hardcoded nodes does not have same chain.
my suggestion is forking back to very first mandatory update.

EDIT: omg, i'll loose 8 coin :S

My second Wallet that I use for monitoring my remote Just forked again at block 12656. I just reloaded this Chain about 1 hour ago.

If it is helpful helpful I will update the little guide I wrote, as soon as I can after the new client is available.

May I suggest that the new client identifies itself (by version number) both in the help and in the download file itself?  That way it'll be easy for people to know what they are getting and whether to download it.

Then I can't advise. I've been getting returns from anomaly pool and I'm on block 12670.

Yes, mine just did.

yes hardcoded nodes forking each other.
i deleted chain an hour ago when wallet get forked..
re downloaded it..
and now..



{
"blocks" : 12652,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.15973277,
"errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.",
"generate" : true,
"genproclimit" : -1,
"hashespersec" : 562,
"networkhashps" : 21902299,
"pooledtx" : 0,
"testnet" : false
}

EDIT: can you please make 'setgenerate false' next update...