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

Hey ya'll, I've added CGA to my new Multipool. Would love to have some miners stop by and mine! CGA is quite often the most profitable coin!


 

SWISSCEX and poloniex are on the same chain.

coinmine.pw is way flakey! they are up then down then up then down.....too unreliable for me to waste hashes on....

CoinMine.pw synced to chain with 182082 blocks. You can mine CGA here. http://www.coinmine.pw/poolinfo.php?coinid=39

Thank you, I do keep dated incremental backups.
I just added the addnode into the .conf file since it states on the main (first) post that the hard coded peers/nodes are down and to add those to configuration start syncing.

So I did.
I think there is a big split happening most the block explorers are frozen and the 3 exchanges are on different chains. Some peps can deposit to some of them but not the others and vice versa.
Thank you anyway.

iSpace, please update and re-sync your wallet asap!

Maybe some of the nodes are out of the proper chain.

You must normally have NO addnode's if everything goes right.

I am connected with these nodes (total of both of my wallets), and seems i am ok.

107.15.231.157
107.170.184.50
108.61.10.90
114.79.28.132
144.76.9.247
148.251.19.213
174.70.129.192
188.165.194.96
188.226.196.176
192.155.250.74
192.241.178.8
193.95.253.142
195.130.216.149
2.51.119.236
209.222.20.140
222.76.215.53
27.96.51.14
5.149.147.225
5.45.109.154
66.169.251.146
68.53.11.59
68.7.158.54
80.241.218.9
82.149.230.110
83.246.149.99
87.206.207.143
87.98.190.199
88.218.101.44
91.132.178.106
92.255.199.98
94.242.222.27


1- Start with a clean slate, including these nodes (erase other files and KEEP only your wallet).

2- When the synchronization is about to end (let's say 10 days ago), STOP the program, wait to for it to finish (debug.log should be the newest file in the directory), and then BACKUP the entire directory and (re)name it CGA-up-to-06-05 (example).

3- Re-open the program and continue to synchronize.

4- I suggest, after a proper synchronization, to remove the addnode's and restart.


This way, if you fail at some point (follow the wrong nodes), you stop, and restore from the last known right state (directory).

E.g. if you fail at -2 days, restore, and save again at -3 or -4 days.

This way you can have a windows like restore point.  CGA data are not so big to keep a duplicate, like doge for instance.

A good habit is also to backup the peers file when all are running ok.


Hope i helped.

How do I get on the right chain?

I am running version v1.3.4.1-unk-beta

I have the following node on the .conf file:

addnode=80.241.218.9
addnode=176.58.92.169
addnode=176.9.63.136
addnode=195.130.216.149
addnode=192.99.35.133
addnode=149.210.168.71
addnode=71.105.130.10
addnode=91.132.178.106
addnode=88.218.101.44
addnode=115.29.160.13
addnode=78.13.151.160
addnode=93.171.209.97
addnode=190.177.100.76
addnode=54.72.105.98
addnode=83.247.7.131

but now that I restarted the walled it says: "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."

and getpeerinfo gives me:

[
{
"addr" : "80.241.218.9:13931",
"services" : "00000003",
"lastsend" : 1402745253,
"lastrecv" : 1402744778,
"bytessent" : 339,
"bytesrecv" : 58164,
"blocksrequested" : 0,
"conntime" : 1402744775,
"version" : 70006,
"subver" : "/Satoshi:1.3.4.2/",
"inbound" : false,
"startingheight" : 174315,
"banscore" : 0
},
{
"addr" : "176.58.92.169:13931",
"services" : "00000003",
"lastsend" : 1402745253,
"lastrecv" : 1402745191,
"bytessent" : 1383,
"bytesrecv" : 63789,
"blocksrequested" : 0,
"conntime" : 1402744776,
"version" : 70006,
"subver" : "/Satoshi:1.3.4.2/",
"inbound" : false,
"startingheight" : 180368,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "176.9.63.136:13931",
"services" : "00000003",
"lastsend" : 1402745252,
"lastrecv" : 1402744961,
"bytessent" : 5514,
"bytesrecv" : 369814,
"blocksrequested" : 0,
"conntime" : 1402744776,
"version" : 70006,
"subver" : "/Satoshi:1.3.4.1/",
"inbound" : false,
"startingheight" : 180368,
"banscore" : 0
},
{
"addr" : "195.130.216.149:13931",
"services" : "00000003",
"lastsend" : 1402744962,
"lastrecv" : 1402745289,
"bytessent" : 339,
"bytesrecv" : 45289,
"blocksrequested" : 0,
"conntime" : 1402744777,
"version" : 70006,
"subver" : "/Satoshi:1.3.4.2/",
"inbound" : false,
"startingheight" : 174315,
"banscore" : 0
},
{
"addr" : "192.99.35.133:13931",
"services" : "00000003",
"lastsend" : 1402745348,
"lastrecv" : 1402745312,
"bytessent" : 73702,
"bytesrecv" : 1359054,
"blocksrequested" : 0,
"conntime" : 1402744778,
"version" : 70006,
"subver" : "/Satoshi:1.3.4.2/",
"inbound" : false,
"startingheight" : 181908,
"banscore" : 0
},
{
"addr" : "149.210.168.71:13931",
"services" : "00000003",
"lastsend" : 1402745348,
"lastrecv" : 1402745312,
"bytessent" : 37237,
"bytesrecv" : 710109,
"blocksrequested" : 0,
"conntime" : 1402744778,
"version" : 70006,
"subver" : "/Satoshi:1.3.4.2/",
"inbound" : false,
"startingheight" : 181908,
"banscore" : 0
},
{
"addr" : "91.132.178.106:13931",
"services" : "00000003",
"lastsend" : 1402745319,
"lastrecv" : 1402745347,
"bytessent" : 5229,
"bytesrecv" : 56840,
"blocksrequested" : 0,
"conntime" : 1402744786,
"version" : 70006,
"subver" : "/Satoshi:1.3.4.1/",
"inbound" : false,
"startingheight" : 181908,
"banscore" : 0
},
{
"addr" : "88.218.101.44:13931",
"services" : "00000003",
"lastsend" : 1402745317,
"lastrecv" : 1402745317,
"bytessent" : 40888,
"bytesrecv" : 703496,
"blocksrequested" : 0,
"conntime" : 1402744792,
"version" : 70006,
"subver" : "/Satoshi:1.3.4.1/",
"inbound" : false,
"startingheight" : 181908,
"banscore" : 0
}
]

Thanks.
If it's not on the right chain, then what do I do next?
Should I submit a ticket to iSpace support and tell them to get on the right chain? Or update their wallet?

ispace isn't on the right chain. We had the same problem with some deposit to our exchange.
You could test if you are on the right chain with following commands.

getblockhash 180837

hash must be 61f73141b678b12a19678965738e056e24ea26cee29c82e9d0c486897140af6c

Kind regards

Tobias

Just had the first payment of 100 cga sent out from ispace to my wallet..problem is it hasn't arrived...it's been over an hour, almost 2 hours now since..
wallet says "up to date" - "processed 181306 blocks of transaction history"
I see others still at 179xxx .... what's goin on here?

fee free to drop by www.hasher.ca , we're running ~18-20MH/s now.

On another note, I now have opened up a new multipool, paying out in BTC. Come check it out too! www.xpool.ca

Cheers!

Hey yall,
my cga wallet is screaming "fill me!" .... I have 31 coins from way back when cga was new....
I see it's at #1 a lot to top 10 on coinwarz... maybe it's time to try mining it again.
Wallet is up to date...
What is a good pool or pools to mine cga from these days?
The ones recommended by the main cga site are all mostly dead now...
Suggestions welcome!
Thanks
Wolfey2014

Apparently the majority of the other nodes that you were connected to agreed on the correct chain, so your wallet ignored the wrong entry of thedigitalmint. Remember - the de-centralized nature means that a lot of things are decided by majority vote - including which chain is the correct one and which is the orphaned one...

forked today for about an hour... good thing I caught it. polo still frozen... need to re-download bchain every other day... what's up with this coin? tfhoneybadger recommended mining this coin...

Could someone please explain why I can have the "cga.thedigitalmint.org" in my getpeerinfo list (along with 5  other peers) and digitalmint on the apparent wrong block chain (according to its explorer) and my wallet still be on the correct chain (not agreeing with digitalmint) 

Why does there still appear to be a fork but trading is taking place?

After re-downloading the chain block about 12 hours ago tf2honeybadger posted on poloniex the correct block height and mine agreed.

My current wallet block is 174853.

Digitalmint (then only explorer I know of) is at 173395 with 72 connections and a 124MH/s.   Correction: 1.24MH/s (missed the decimal)

Am I mining on the wrong chain?

WHICH one is correct?

coinmine.pw is at 173548 now, and http://cga.thedigitalmint.org/ is stuck at 172851.

Both my wallets agree with the first (CGAs are transferred ok).

I have same blockheight as p2p pool:

"blocks" : 173262,

block explorer (http://cga.thedigitalmint.org/) is at 172849 ?!

Please advise what is correct chain now, exchanges are offline so also not able to check there

    
devs, it is not funny, it's so hard to check 1 per day network?
will solve the problem with fork

cga.thedigitalmint.org  Block:172774

p2pool Block:172994