⚒[CGA] Cryptographic Anomaly - The Elusive Coin⚒

[brokedummy]

Looks like I chose the wrong time to mine this, probably have nothing to show for it. But anyway...

I compiled the new wallet and started a fresh sync but it won't got past block 8737.

Any hints?

try to clear out any old peers.dat files

I started with a clean slate, not even a wallet.dat. But I tried this anyway and same issue, gets to block 8737 and stops

What version number?

[1713949532]

1713949532

[1713949532]

1713949532

[1713949532]

1713949532

[1713949532]

1713949532

[s4w3d0ff]

Looks like I chose the wrong time to mine this, probably have nothing to show for it. But anyway...

I compiled the new wallet and started a fresh sync but it won't got past block 8737.

Any hints?

try to clear out any old peers.dat files

I started with a clean slate, not even a wallet.dat. But I tried this anyway and same issue, gets to block 8737 and stops

If it helps,

Code:

2014-03-23 22:28:49 SetBestChain: new best=73f3147fadd913980617b8a5bdea301e0c0a5ef3434eec693ecaca0bb62b4604  height=8737  log2_work=44.743169  tx=9353  date=2014-02-07 11:22:25 progress=0.058806
2014-03-23 22:28:49  nActualTimespan = 639 before bounds
2014-03-23 22:28:49 GetNextWorkRequired RETARGET
2014-03-23 22:28:49 nTargetTimespan = 80 nActualTimespan = 320
2014-03-23 22:28:49 Before: 1d02826c 00000002826c0000000000000000000000000000000000000000000000000000
2014-03-23 22:28:49 After: 1d0a09b0 0000000a09b00000000000000000000000000000000000000000000000000000
2014-03-23 22:28:49 ERROR: ConnectBlock() : coinbase pays too much (actual=100000000 vs limit=0)

What are your machines specs? We had this problem before but don't have enough data to come to a conclusion. We think it maybe a "rounding" issue due to differences in processors. If you could let us know what OS (32 or 64bit) and  possessor you are using that would help. It think that  older (low powered) processors are not doing the math with enough accuracy as the others. This problem has been fixed in the latest update but trying to sync new wallets may be an issue on older machines.

[s4w3d0ff]

I have this payout of  0.53220505 from the digital mint pool http://cga.thedigitalmint.org/index.php?transaction=c6ef09821c88e7a0f82e9d186dd8b7cf2a24f77dc7dda8aa8b1dafc722b01fea that I never received at my deposit address at poloniex. (I'm only depositing directly to poloniex directly because of the forking and the fact that I'm unable to keep my wallet on the correct chain).

Was/is the digital mint on the wrong chain?

The digitalmint is on the right chain. Poloniex may be updating (or not on the right chain) I have emailed them, give them some time, If you were on the correct chain and poloniex gets on the right chain you will get your coins.

[tseug]

What version number?

v1.3.2.1-unk-beta but looks like s4w3d0ff has the answer

Looks like I chose the wrong time to mine this, probably have nothing to show for it. But anyway...

I compiled the new wallet and started a fresh sync but it won't got past block 8737.

Any hints?

try to clear out any old peers.dat files

I started with a clean slate, not even a wallet.dat. But I tried this anyway and same issue, gets to block 8737 and stops

If it helps,

Code:

2014-03-23 22:28:49 SetBestChain: new best=73f3147fadd913980617b8a5bdea301e0c0a5ef3434eec693ecaca0bb62b4604  height=8737  log2_work=44.743169  tx=9353  date=2014-02-07 11:22:25 progress=0.058806
2014-03-23 22:28:49  nActualTimespan = 639 before bounds
2014-03-23 22:28:49 GetNextWorkRequired RETARGET
2014-03-23 22:28:49 nTargetTimespan = 80 nActualTimespan = 320
2014-03-23 22:28:49 Before: 1d02826c 00000002826c0000000000000000000000000000000000000000000000000000
2014-03-23 22:28:49 After: 1d0a09b0 0000000a09b00000000000000000000000000000000000000000000000000000
2014-03-23 22:28:49 ERROR: ConnectBlock() : coinbase pays too much (actual=100000000 vs limit=0)

What are your machines specs? We had this problem before but don't have enough data to come to a conclusion. We think it maybe a "rounding" issue due to differences in processors. If you could let us know what OS (32 or 64bit) and  possessor you are using that would help. It think that  older (low powered) processors are not doing the math with enough accuracy as the others. This problem has been fixed in the latest update but trying to sync new wallets may be an issue on older machines.

Well you'd be right about old/slow processors, this is on an Intel Atom N280 (slow when new, nevermind now).
And it's a 32 bit linux mint 16 system. I've had 32 bit specific problems before (like with DGW now) so that could be an issue.

Any chance there's a recent-ish blockchain download link somwhere in this thread?

Thanks for the support

[s4w3d0ff]

What version number?

v1.3.2.1-unk-beta but looks like s4w3d0ff has the answer

Looks like I chose the wrong time to mine this, probably have nothing to show for it. But anyway...

I compiled the new wallet and started a fresh sync but it won't got past block 8737.

Any hints?

try to clear out any old peers.dat files

I started with a clean slate, not even a wallet.dat. But I tried this anyway and same issue, gets to block 8737 and stops

If it helps,

Code:

2014-03-23 22:28:49 SetBestChain: new best=73f3147fadd913980617b8a5bdea301e0c0a5ef3434eec693ecaca0bb62b4604  height=8737  log2_work=44.743169  tx=9353  date=2014-02-07 11:22:25 progress=0.058806
2014-03-23 22:28:49  nActualTimespan = 639 before bounds
2014-03-23 22:28:49 GetNextWorkRequired RETARGET
2014-03-23 22:28:49 nTargetTimespan = 80 nActualTimespan = 320
2014-03-23 22:28:49 Before: 1d02826c 00000002826c0000000000000000000000000000000000000000000000000000
2014-03-23 22:28:49 After: 1d0a09b0 0000000a09b00000000000000000000000000000000000000000000000000000
2014-03-23 22:28:49 ERROR: ConnectBlock() : coinbase pays too much (actual=100000000 vs limit=0)

What are your machines specs? We had this problem before but don't have enough data to come to a conclusion. We think it maybe a "rounding" issue due to differences in processors. If you could let us know what OS (32 or 64bit) and  possessor you are using that would help. It think that  older (low powered) processors are not doing the math with enough accuracy as the others. This problem has been fixed in the latest update but trying to sync new wallets may be an issue on older machines.

Well you'd be right about old/slow processors, this is on an Intel Atom N280 (slow when new, nevermind now).
And it's a 32 bit linux mint 16 system. I've had 32 bit specific problems before (like with DGW now) so that could be an issue.

Any chance there's a recent-ish blockchain download link somwhere in this thread?

Thanks for the support

Thanks for the info, I believe this may be the issue. We do not have a download link for the blockchain yet (need to look into getting one soon if this problem keeps coming up) in the meantime if that is the only machine you can put the wallet on then I would suggest getting MuCoWa it is based off of Multibit so the blockchain is on a server. Only thing is that the wallet charges a small fee for transactions.

This is by all means not a "fix" for the problem, but if you need local storage of CGA on an older machine then this should work.

[Cor2]

So MPOS.CGA.anaomolypool finally paid out to my MuCoWa address, but now MuCoWa will not sync when I add my backed up wallet with that address back to it after reinstalling.  I know the address the cga was sent too, but I don't know of any way to put that address into a working wallet.  Anyone know how to do this, or did I lose my cga?  BTW, these cga were mined in the last few weeks and should not have been affected by the fork.  I am also using the latest cga wallet which is working fine.

I presume that something happened in MuCoWa that is not compatible with your old wallet, so here is what I would do:
- backup existing (new) wallet so it is secure (not overwrite old backup wallet!)
- re-install (or switch to directory with old MuCoWa, run it
- open the old backup wallet, don't care if it syncs, because you immediately do only the following:
- find out how to export the *private key(s)* for your CGA and store those securely
- close old MuCoWa
- run new MuCoWa again and import the stored private keys from the old wallet
- MuCoWa should now find the balance from the old wallet in the block chain. (because coins are stored in the block chain, not in a wallet)
NOTE: never publish your private key(s), those give full access to your coins in the block chain, including transfer elsewhere...
Success!

[Cor2]

Why is TheDigitalMint showing 0 pool hash and has Poloniex frozen the CGA market?
Are we still recovering from a fork and is TheDigitalMint redownloading?

[s4w3d0ff]

Why is TheDigitalMint showing 0 pool hash and has Poloniex frozen the CGA market?
Are we still recovering from a fork and is TheDigitalMint redownloading?

I can confirm that thedigitalmint seems to be down. Not sure why. Poloniex should be unfrozen as far as I know. I got an email from them saying they are on the latest version (1.3.2.1) about 2 hours ago.

Edit: Inceptioncraft block explorer seems to be forked or the front end frozen. http://node1.cga.anomalypool.com:2760/chain/CryptographicAnomaly is still good.

[Cor2]

Why is TheDigitalMint showing 0 pool hash and has Poloniex frozen the CGA market?
Are we still recovering from a fork and is TheDigitalMint redownloading?

I can confirm that thedigitalmint seems to be down. Not sure why. Poloniex should be unfrozen as far as I know. I got an email from them saying they are on the latest version (1.3.2.1) about 2 hours ago.

I tried again to submit an order a second ago and it says "This market is frozen"

[s4w3d0ff]

Why is TheDigitalMint showing 0 pool hash and has Poloniex frozen the CGA market?
Are we still recovering from a fork and is TheDigitalMint redownloading?

I can confirm that thedigitalmint seems to be down. Not sure why. Poloniex should be unfrozen as far as I know. I got an email from them saying they are on the latest version (1.3.2.1) about 2 hours ago.

I tried again to submit an order a second ago and it says "This market is frozen"

I will send him another email.

[romang]

The market is to flooded with these alt coins. i PASS

[s4w3d0ff]

Another junk coin.

Haters will be haters... you probably think that Tittiecoin is the greatest thing ever and will take over the world 

[MiningViking]

Ugh, was solo mining, hope the coins I did get arent on the wrong fork 

I hope you have been keeping up to date in the thread and irc, the older your client the more coin you will probably end up losing.  One of the causes of forks they think was a solominer on an out of date client.

Wow.. I lost everything 

They did choose the fork for their own pool that no one else was mining at...

[MiningViking]

Anybody want to send me some sympathy CGA? I wasted 36 hours on the wrong fork 

ARSDWmtinB2anBAQLhHS9UvesFN7yUpzWW

I lost almost 30 CGA, 3 kilowatt.

[wzttide]

So MPOS.CGA.anaomolypool finally paid out to my MuCoWa address, but now MuCoWa will not sync when I add my backed up wallet with that address back to it after reinstalling.  I know the address the cga was sent too, but I don't know of any way to put that address into a working wallet.  Anyone know how to do this, or did I lose my cga?  BTW, these cga were mined in the last few weeks and should not have been affected by the fork.  I am also using the latest cga wallet which is working fine.

I presume that something happened in MuCoWa that is not compatible with your old wallet, so here is what I would do:
- backup existing (new) wallet so it is secure (not overwrite old backup wallet!)
- re-install (or switch to directory with old MuCoWa, run it
- open the old backup wallet, don't care if it syncs, because you immediately do only the following:
- find out how to export the *private key(s)* for your CGA and store those securely
- close old MuCoWa
- run new MuCoWa again and import the stored private keys from the old wallet
- MuCoWa should now find the balance from the old wallet in the block chain. (because coins are stored in the block chain, not in a wallet)
NOTE: never publish your private key(s), those give full access to your coins in the block chain, including transfer elsewhere...
Success!

MuCoWa runs with an old protocol version, this prevents MuCoWa from syncing with the correct block chain. As soon as the devs report a stable version there will also be an update for MuCoWa.

Sawedoff/tf2, please send me a message asap with the correct protocol version which also will work for at least a few weeks, thanks!

[MiningViking]

So MPOS.CGA.anaomolypool finally paid out to my MuCoWa address, but now MuCoWa will not sync when I add my backed up wallet with that address back to it after reinstalling.  I know the address the cga was sent too, but I don't know of any way to put that address into a working wallet.  Anyone know how to do this, or did I lose my cga?  BTW, these cga were mined in the last few weeks and should not have been affected by the fork.  I am also using the latest cga wallet which is working fine.

I presume that something happened in MuCoWa that is not compatible with your old wallet, so here is what I would do:
- backup existing (new) wallet so it is secure (not overwrite old backup wallet!)
- re-install (or switch to directory with old MuCoWa, run it
- open the old backup wallet, don't care if it syncs, because you immediately do only the following:
- find out how to export the *private key(s)* for your CGA and store those securely
- close old MuCoWa
- run new MuCoWa again and import the stored private keys from the old wallet
- MuCoWa should now find the balance from the old wallet in the block chain. (because coins are stored in the block chain, not in a wallet)
NOTE: never publish your private key(s), those give full access to your coins in the block chain, including transfer elsewhere...
Success!

MuCoWa runs with an old protocol version, this prevents MuCoWa from syncing with the correct block chain. As soon as the devs report a stable version there will also be an update for MuCoWa.

Sawedoff/tf2, please send me a message asap with the correct protocol version which also will work for at least a few weeks, thanks!

Considering there been 2 fork in 1 weeks time i do think you should wait until a version worked for 2-3 weeks before re-adding it..

[s4w3d0ff]

Ugh, was solo mining, hope the coins I did get arent on the wrong fork 

I hope you have been keeping up to date in the thread and irc, the older your client the more coin you will probably end up losing.  One of the causes of forks they think was a solominer on an out of date client.

Wow.. I lost everything 

They did choose the fork for their own pool that no one else was mining at...

Not sure what you are getting at... it did not matter what chain we picked, people were going to have coins lost. I wasn't mining (nor do I really ever mine, because "mommy and daddy doesn't pay my bills or buy me what ever I want") so you can't accuse me of having some sort of personal vendetta. I picked the chain with the most valid data. I do not "own a pool" and at the time of the fork tf2honeybadger didn't either... So you are just blowing smoke up your ass. Shit happens, get over it and move on.

[s4w3d0ff]

Considering there been 2 fork in 1 weeks time i do think you should wait until a version worked for 2-3 weeks before re-adding it..

Your such a big help! Thank you for your input. If you ever make your own coin let me know. I would gladly repay 10x the amount of generous feed back that you have so graciously brought to this coin.

[MiningViking]

Ugh, was solo mining, hope the coins I did get arent on the wrong fork  

I hope you have been keeping up to date in the thread and irc, the older your client the more coin you will probably end up losing.   One of the causes of forks they think was a solominer on an out of date client.

Wow.. I lost everything  

They did choose the fork for their own pool that no one else was mining at...

Not sure what you are getting at... it did not matter what chain we picked, people were going to have coins lost. I wasn't mining (nor do I really ever mine, because "mommy and daddy doesn't pay my bills or buy me what ever I want") so you can't accuse me of having some sort of personal vendetta. I picked the chain with the most valid data. I do not "own a pool" and at the time of the fork tf2honeybadger didn't either... So you are just blowing smoke up your ass. Shit happens, get over it and move on.

You blabla still dont change the fact that you did choose the fork for a pool that no one was mining at expect you and your "team dev`s", and that people that where mining at the pool you recommended us to mine at lost it all..
Your choise was to minimize your own loss and let everyone else take the hit, its obvious so just be honest about it instead.
I pay for my own equipment and my own electricity bills because unlike you i live in my own house and unlike you my mother dont buy my underwear.

[MiningViking]

Considering there been 2 fork in 1 weeks time i do think you should wait until a version worked for 2-3 weeks before re-adding it..

Your such a big help! Thank you for your input. If you ever make your own coin let me know. I would gladly repay 10x the amount of generous feed back that you have so graciously brought to this coin.

Well i guess you get what you deserve, basic karma.