Nice find! Unfortunately the proposed fix can still be exploited to a "time traveling attack". They seem to be working it out in that thread so I will keep my eyes on it.

Brother3, LOL - thanks for the find!I made a suggestion to that thread for a new and simple algorithm that should remove the complexity and time travel issues of KGW and if we use it for CGA, it will quieten the jumps in the diff by averaging the block find time so that luck and sudden increases do not make it jump around.

shit.... Tried to make some extra money selling cross market at a profit.... bought 10 CGA for .0031 BTC each, then tried to sell them on allcrypt at .0041 each, or so I thought.... ended up selling 10 cga at .00041 BTC each... I was wondering why no one tried that yet...

shit.... Tried to make some extra money selling cross market at a profit.... bought 10 CGA for .0031 BTC each, then tried to sell them on allcoin at .0041 each, or so I thought.... ended up selling 10 cga at .00041 BTC each... I was wondering why no one tried that yet...

shit.... Tried to make some extra money selling cross market at a profit.... bought 10 CGA for .0031 BTC each, then tried to sell them on allcoin at .0041 each, or so I thought.... ended up selling 10 cga at .00041 BTC each... I was wondering why no one tried that yet...

shit.... Tried to make some extra money selling cross market at a profit.... bought 10 CGA for .0031 BTC each, then tried to sell them on allcoin at .0041 each, or so I thought.... ended up selling 10 cga at .00041 BTC each... I was wondering why no one tried that yet...

I guess it's about time I get new contacts.

got to count those zeros! I almost sold 8 CGA at 0.0006 on Allcrypt!

After Block 64k, becomes very difficult mining

You should be seeing rewards faster. You no longer have to worry about solving blocks that are worth 0. All the blocks are worth something.

shit.... Tried to make some extra money selling cross market at a profit.... bought 10 CGA for .0031 BTC each, then tried to sell them on allcoin at .0041 each, or so I thought.... ended up selling 10 cga at .00041 BTC each... I was wondering why no one tried that yet...

I guess it's about time I get new contacts.

got to count those zeros! I almost sold 8 CGA at 0.0006 on Allcrypt!

After Block 64k, becomes very difficult mining

You should be seeing rewards faster. You no longer have to worry about solving blocks that are worth 0. All the blocks are worth something.

Actually, I prefer the before Block 64K award rules. Hey, try to get on the cryptsy, this will cause the attention of bter.com

The http://cga.inceptioncraft.net/mpos pool is now processing payouts. The MPOS pool will not reopen, but the features I created for it (CGA/day estimate, anomaly generation probability) will be set up on BobNoble's pool at http://cga.thedigitalmint.net. I will be opening a P2Pool in the future, but I just cannot keep up with maintaining a MPOS pool due to the time requirement. If you mined on http://cga.inceptioncraft.net/mpos, please submit a manual withdrawal for your coins before April 19. After April 19, any coins left in the wallet will go into a community bounty pot that I will be posting more details about later. This information will also be posted on the pool's home page.

TL;DR: IF YOU MINED ON INCEPTIONCRAFT's MPOS POOL, GET YOUR COINS OUT BEFORE APRIL 19.

shit.... Tried to make some extra money selling cross market at a profit.... bought 10 CGA for .0031 BTC each, then tried to sell them on allcrypt at .0041 each, or so I thought.... ended up selling 10 cga at .00041 BTC each... I was wondering why no one tried that yet...

I'm trying to install the linux wallet. I have the latest sources from github.

Both cryptographicanomalyd and cryptographicanomaly-qt get stuck at block 8737, giving an error message suggesting that I'm on a forked block chain. I have tried deleting the blocks/ and chainstate/ directories, and still it only syncs upto 8737.

I'm trying to install the linux wallet. I have the latest sources from github.

Both cryptographicanomalyd and cryptographicanomaly-qt get stuck at block 8737, giving an error message suggesting that I'm on a forked block chain. I have tried deleting the blocks/ and chainstate/ directories, and still it only syncs upto 8737.

Hi!I'm trying to install the linux wallet. I have the latest sources from github.Both cryptographicanomalyd and cryptographicanomaly-qt get stuck at block 8737, giving an error message suggesting that I'm on a forked block chain. I have tried deleting the blocks/ and chainstate/ directories, and still it only syncs upto 8737.

In cases like this, if you want to see what is going on, the Debug log is the best place to look: Help -> Debug Window, then select Information tab and click on the "Open" button under the Debug Log file. It probably is also stored as a file in the CGA directory.The end of that file will show you the most recent transactions and why your wallet is rejecting what it is receiving.I have found in this case it very helpful to synchronise fast with a single known-good node. The suggestion has been made here beforeto put only the following two lines in your CryptoGraphicAnomaly.conf file, let the wallet sync completely and then put your normal config file back:

Code:

listen=0connect=cga.inceptioncraft.net

The first line disables the process to try and discover other nodes (so, you do not hear the forked node any longer) and the second line you should use a node that you know is good. My wallet sync'ed in record time with this setting.Success,

Perhaps this is related to the 1.3.0.1 update a few days ago? Has anyone actually tried to sync to block chain from the beginning with that version?

Yes it was properly tested. Issue is that the hardcoded nodes seem to still have peers that are on the old versions so you end up connecting to those peers and get stuck where they are. Do the following to get past the fork:

Shutdown wallet. Delete blockchain and peers.dat (don't touch the wallet.dat!), in your config file set listen=0 and add connect = cga.inceptioncraft.net, then start the wallet. This will cause you to connect to just cga.inceptioncraft.net and download the correct blockchain. Once you are fully synced, shutdown your wallet, change listen=1 and delete connect = cga.inceptioncraft.net. Start the wallet again... and BAM you should be cooking.

Perhaps this is related to the 1.3.0.1 update a few days ago? Has anyone actually tried to sync to block chain from the beginning with that version?

Yes it was properly tested. Issue is that the hardcoded nodes seem to still have peers that are on the old versions so you end up connecting to those peers and get stuck where they are. Do the following to get past the fork:

Shutdown wallet. Delete blockchain and peers.dat (don't touch the wallet.dat!), in your config file set listen=0 and add connect = cga.inceptioncraft.net, then start the wallet. This will cause you to connect to just cga.inceptioncraft.net and download the correct blockchain. Once you are fully synced, shutdown your wallet, change listen=1 and delete connect = cga.inceptioncraft.net. Start the wallet again... and BAM you should be cooking.