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

Come mine with us!

New pool for CryptoGraphicAnomaly, spread the hash!
DDOS protection
Super fast stratum server based on node.js
Powerful dedicated server

http://nomp.thecryptopool.com

For now, until we can sort out just what the issue is with CGA and p2pool, I would suggest not mining CGA using a p2pool. Apparently the p2pools are submitting "bad blocks" and relaying them to wallets, causing the wallets to go out of sync. We have plenty of MPOS pools and a few NOMP pools to choose from, if you enjoy how p2pool works with payouts, try a NOMP pool. We are looking into the issue further so that we can bring p2pools back.

If your wallet stops syncing, please take note of the block that your wallet has stopped on, and PM me with the following info in order to help the investigation:

1.Block # wallet got stuck on
2.Machine specs (OS, 32 or 64 bit)
3.If you can save the debug log that would also help, I am just looking for the lines that say "InvalidChainFound: invalid block=" and "InvalidChainFound:  current best="

I'm shutting down anomalypool.com now, this makes no sense. Waiting for the devs to resolve the problem.

Something is really wrong with coin. Coin in forked again. P2pool at block 119824 my pool wallet again stuck with error "Displayed transactions..." with P2Pools at block 119824. My payout wallet have same chain with block explorer on block 119902

I'm resyncing the p2pool anomalypool.com due to:

I'm running into troubles every few days and I'm seriously thinking of turning off the p2pool. It seems like p2pool brings some instability to the CGA network.

7 active connections for 12 hours and wallet won't sync. Opened and closed with no luck. Any suggestions? Add nodes? if so which ones?

My wallet stuck again. Now on block 117620 with error "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
It happened already several times last weeks and CGA daemons need more and more attention... It's your unique anti-fork system? Needed redownload blockchain every week?

----------------[debug.log]-----------------------
2014-04-29 11:36:49 Cryptographicanomaly version v1.3.3.3-unk-beta (2014-04-08 16:05:25 -0700)
2014-04-29 11:36:49 Using OpenSSL version OpenSSL 1.0.1f 6 Jan 2014
2014-04-29 11:36:49 Default data directory /root/.cryptographicanomaly
2014-04-29 11:36:49 Using data directory /home/raid0/daemons/cryptogacoin
2014-04-29 11:36:49 Using at most 20 connections (100000 file descriptors available)
2014-04-29 11:36:49 Using 12 threads for script verification
2014-04-29 11:36:49 init message: Verifying wallet...
2014-04-29 11:36:49 dbenv.open LogDir=/home/raid0/daemons/cryptogacoin/database ErrorFile=/home/raid0/daemons/cryptogacoin/db.log
2014-04-29 11:36:49 Bound to [::]:13931
2014-04-29 11:36:49 Bound to 0.0.0.0:13931
2014-04-29 11:36:49 init message: Loading block index...
2014-04-29 11:36:49 Opening LevelDB in /home/raid0/daemons/cryptogacoin/blocks/index
2014-04-29 11:36:49 Opened LevelDB successfully
2014-04-29 11:36:49 Opening LevelDB in /home/raid0/daemons/cryptogacoin/chainstate
2014-04-29 11:36:49 Opened LevelDB successfully
2014-04-29 11:36:50 LoadBlockIndexDB(): last block file = 0
2014-04-29 11:36:50 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=119878, size=78569851, heights=0...119814, time=2014-02-01...2014-04-29)
2014-04-29 11:36:50 LoadBlockIndexDB(): transaction index disabled
2014-04-29 11:36:50 LoadBlockIndexDB(): hashBestChain=a8579f51c8158f5b4cd681458f42f83096135cc3cf1fb0c3e0cddefc6ce41e9e  height=117620 date=2014-04-28 10:34:00
2014-04-29 11:36:50 init message: Verifying blocks...
2014-04-29 11:36:50 Verifying last 288 blocks at level 3
2014-04-29 11:36:50 No coin database inconsistencies in last 289 blocks (381 transactions)
2014-04-29 11:36:50  block index            1119ms
2014-04-29 11:36:50 init message: Loading wallet...
2014-04-29 11:36:51 nFileVersion = 1030303
2014-04-29 11:36:51  wallet                  477ms
2014-04-29 11:36:51 init message: Loading addresses...
2014-04-29 11:36:51 Loaded 4751 addresses from peers.dat  9ms
2014-04-29 11:36:51 mapBlockIndex.size() = 119878
2014-04-29 11:36:51 nBestHeight = 117620
2014-04-29 11:36:51 setKeyPool.size() = 101
2014-04-29 11:36:51 mapWallet.size() = 1159
2014-04-29 11:36:51 mapAddressBook.size() = 3
2014-04-29 11:36:51 AddLocal(176.9.63.136:13931,1)
2014-04-29 11:36:51 IPv4 eth0: 176.9.63.136
2014-04-29 11:36:51 AddLocal([2a01:4f8:150:8185::2]:13931,1)
2014-04-29 11:36:51 IPv6 eth0: 2a01:4f8:150:8185::2
2014-04-29 11:36:51 addcon thread start
2014-04-29 11:36:51 dnsseed thread start
2014-04-29 11:36:51 Loading addresses from DNS seeds (could take a while)
2014-04-29 11:36:51 net thread start
2014-04-29 11:36:51 opencon thread start
2014-04-29 11:36:51 trying connection 184.154.116.146:13931 lastseen=360769.8hrs
2014-04-29 11:36:51 msghand thread start
2014-04-29 11:36:51 dumpaddr thread start
2014-04-29 11:36:51 init message: Done loading
2014-04-29 11:36:51 8 addresses found from DNS seeds
2014-04-29 11:36:51 dnsseed thread exit
2014-04-29 11:36:51 connected 184.154.116.146:13931
2014-04-29 11:36:51 send version message: version 70006, blocks=117620, us=176.9.63.136:13931, them=184.154.116.146:13931, peer=184.154.116.146:13931
2014-04-29 11:36:51 Added time data, samples 2, offset +0 (+0 minutes)
2014-04-29 11:36:51 receive version message: /Satoshi:1.3.3.3/: version 70006, blocks=119805, us=176.9.63.136:5686, them=184.154.116.147:13931, peer=184.154.116.146:13931

---
2014-04-29 11:37:08 received block ba75168fb87c66f93c4bba7e48b11051173e5367c19713dadbc73794dce2e9fa
2014-04-29 11:37:09   nActualTimespan = 71  before bounds
2014-04-29 11:37:09 GetNextWorkRequired RETARGET
2014-04-29 11:37:09 nTargetTimespan = 80    nActualTimespan = 71
2014-04-29 11:37:09 Before: 1c17d850  0000000017d85000000000000000000000000000000000000000000000000000
2014-04-29 11:37:09 After:  1c152993  00000000152993cccccccccccccccccccccccccccccccccccccccccccccccccc
2014-04-29 11:37:09 InvalidChainFound: invalid block=ba75168fb87c66f93c4bba7e48b11051173e5367c19713dadbc73794dce2e9fa  height=119806  log2_work=49.979477  date=2014-04-29 11:33:20
2014-04-29 11:37:09 InvalidChainFound:  current best=a8579f51c8158f5b4cd681458f42f83096135cc3cf1fb0c3e0cddefc6ce41e9e  height=117620  log2_work=49.918437  date=2014-04-28 10:34:00
2014-04-29 11:37:09 InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
2014-04-29 11:37:09 ProcessBlock: ACCEPTED
2014-04-29 11:37:09 connection timeout
2014-04-29 11:37:09 trying connection 176.58.88.153:13931 lastseen=2.5hrs
2014-04-29 11:37:09 connected 176.58.88.153:13931
2014-04-29 11:37:09 send version message: version 70006, blocks=117620, us=176.9.63.136:13931, them=176.58.88.153:13931, peer=176.58.88.153:13931
2014-04-29 11:37:09 Added time data, samples 6, offset -1 (+0 minutes)
---
2014-04-29 11:37:56 received block 9af97190ec39faff72a68535950f899119edec6333bb77b70f78fb977883f853
2014-04-29 11:37:56 InvalidChainFound: invalid block=9af97190ec39faff72a68535950f899119edec6333bb77b70f78fb977883f853  height=119815  log2_work=49.979684  date=2014-04-29 11:37:49
2014-04-29 11:37:56 InvalidChainFound:  current best=a8579f51c8158f5b4cd681458f42f83096135cc3cf1fb0c3e0cddefc6ce41e9e  height=117620  log2_work=49.918437  date=2014-04-28 10:34:00
2014-04-29 11:37:56 InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
2014-04-29 11:37:56 ProcessBlock: ACCEPTED
2014-04-29 11:38:00 Added 59 addresses from 66.128.118.35: 16 tried, 4988 new
2014-04-29 11:38:00 connection timeout
2014-04-29 11:38:01 trying connection 108.172.177.216:13931 lastseen=10.2hrs
2014-04-29 11:38:02 ThreadRPCServer method=listsinceblock
2014-04-29 11:38:06 connection timeout
2014-04-29 11:38:06 trying connection 213.21.33.12:13931 lastseen=13.2hrs
2014-04-29 11:38:11 connection timeout
2014-04-29 11:38:12 trying connection 88.198.198.94:13931 lastseen=87.2hrs
2014-04-29 11:38:17 connection timeout
2014-04-29 11:38:17 trying connection 212.107.142.229:13931 lastseen=30.6hrs
2014-04-29 11:38:22 connection timeout
2014-04-29 11:38:23 trying connection 94.158.147.116:13931 lastseen=6.3hrs
2014-04-29 11:38:23 connect() failed after select(): Connection refused
2014-04-29 11:38:23 trying connection 31.23.71.174:13931 lastseen=122.7hrs
2014-04-29 11:38:25 stored orphan tx 219a8cefcddc37e027c1420a553539ad9d8a9f5ba0cf080cb5909ea075783ac7 (mapsz 1)
2014-04-29 11:38:25 stored orphan tx 26c9dcb22504216761a3b4765a8943f108d4f17a677033f328e616308be08e43 (mapsz 2)

There is also a spike on http://anomalypool.com/static/

I think ASICs are joining the game.

Inceptioncraft has a problem - the security certificate of the site is revoked - possibly to fix the Heartbleed problem?
And I looked at the Miningpools stats to see why the net hashrate suddenly more than doubled (250 => 550 Mh/s).
There are 4 miners on CGA at TheMiningpools and the pool hashrate is 380 Mh/s !!!!
Looks like someone added a farm or a bunch of ASIC miners.
Now it is no fun to mine CGA any longer with a GPU - I already got less than $1 per day before.
I estimate that it will be half that now...
Incidentally I switched my mining to another coin that added some interesting features last weekend,
including a very stable diff estimation, so the diff hardly changes from block to block, unlike CGA.
That coin had been all but dead for a while, but some dev took an interest and has introduced interesting improvements.
Sources can be found here: https://github.com/ghostlander/Orbitcoin

Anyone with wallet issues, it would be much appreciated if the debug log info is posted for the block in question. It will help identify the problem so it can be fixed.

Please post the following if such an issue occurs:

1.Block # that the wallet is hung up on
2.Error that shows in the debug log
3.System specs that the issue has taken place on

I have not had such issues running the wallet on OSX 10.7 but I need more info on the matter so that the issue can be identified and fixed, thank you.

I'm on 70006. Thanks for the quick reply though.

There has been issues with the P2pools, check the settings for the protocol version, we have changed it a few times to fix forking issues, your protocol version should be "70006", of coarse I don't really know the specifics of p2pool but it may be the problem.

I've had to stop my cga p2pool server twice to re-download the blockchain. It keeps getting hosed. Something is wrong with the daemon or network. I'm going to keep it down until there's a fix.

Close the wallet and restart? If that doesn't work you may have to delete some bad chain data and redownload the entire chain. Steps to take are buried somewhere in this thread if you need I can find them.

My CGA Wallet will not sync. It was fine a few days ago but now it's been stuck for hours "synchronizing with network". Last received block was generated 41 hours ago.

Any ideas?

Thanks!

Ya WC has nothing to do with YIN/YANG, just a coincidence that the OP names are similar. Not sure what is going on over there.

Hey Sawedoff,
do you know who is YinYangTeam?
Apparently he is dev of WC (which has a vulnerability right now):
https://bitcointalk.org/index.php?topic=568517.5760
I expect that he has nothing to do with Yin and Yang coins
but there have been rumors for some time.

Just a heads up. I've added a zero fee CGA p2pool.

http://p2pool.sawilson.org:23932

Enjoy

I'm dedicating 0.1 BTC, and someone else 0.05 BTC, to voting for SwissCex. I'll be extremely surprised if we don't make it.

EDIT: 1000 votes later, and we're a solid #1 again. 0.1 BTC on standby if a coin jumps ahead.

We are *one* vote behind the nr 1 after someone dropped another 0.1 BTC into their pot to buy 2000 more votes.
I have never heard of ARK, but we should be able to beat them! Keep voting!