âš’[CGA] Cryptographic Anomaly - The Elusive Coinâš’ - page 49.

tf2honeybadger

full member

Activity: 189

Merit: 100

Quote from: Zuikkis on March 20, 2014, 01:12:55 PM

Quote from: s4w3d0ff on March 20, 2014, 01:05:20 PM

Quote from: Zuikkis on March 20, 2014, 12:54:02 PM

Still stuck at 8737.. Sad

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.

That's exactly what I did. Here is the problem part from the log:

Code:

2014-03-20 17:46:51 received block 361031959e1085697e2e46417d26bcad3d9e9a7b7fc63ec2ac53aa386c494763
2014-03-20 17:46:51 nActualTimespan = 639 before bounds
2014-03-20 17:46:51 GetNextWorkRequired RETARGET
2014-03-20 17:46:51 nTargetTimespan = 80 nActualTimespan = 320
2014-03-20 17:46:51 Before: 1d02826c 00000002826c0000000000000000000000000000000000000000000000000000
2014-03-20 17:46:51 After: 1d0a09b0 0000000a09b00000000000000000000000000000000000000000000000000000
2014-03-20 17:46:51 ERROR: ConnectBlock() : coinbase pays too much (actual=100000000 vs limit=0)
2014-03-20 17:46:51 InvalidChainFound: invalid block=361031959e1085697e2e46417d26bcad3d9e9a7b7fc63ec2ac53aa386c494763 height=8738 log2_work=44.74319 date=2014-02-07 11:12:39
2014-03-20 17:46:51 InvalidChainFound: current best=73f3147fadd913980617b8a5bdea301e0c0a5ef3434eec693ecaca0bb62b4604 height=8737 log2_work=44.743169 date=2014-02-07 11:22:25
2014-03-20 17:46:51 InvalidChainFound: invalid block=361031959e1085697e2e46417d26bcad3d9e9a7b7fc63ec2ac53aa386c494763 height=8738 log2_work=44.74319 date=2014-02-07 11:12:39
2014-03-20 17:46:51 InvalidChainFound: current best=73f3147fadd913980617b8a5bdea301e0c0a5ef3434eec693ecaca0bb62b4604 height=8737 log2_work=44.743169 date=2014-02-07 11:22:25
2014-03-20 17:46:51 ERROR: SetBestBlock() : ConnectBlock 361031959e1085697e2e46417d26bcad3d9e9a7b7fc63ec2ac53aa386c494763 failed
2014-03-20 17:46:51 ERROR: AcceptBlock() : AddToBlockIndex failed
2014-03-20 17:46:51 ERROR: ProcessBlock() : AcceptBlock FAILED
2014-03-20 17:46:51 Misbehaving: 184.154.116.146:13931 (0 -> 100) DISCONNECTING
2014-03-20 17:46:51 disconnecting node cga.inceptioncraft.net
2014-03-20 17:46:54 trying connection cga.inceptioncraft.net lastseen=0.0hrs
2014-03-20 17:46:54 connected cga.inceptioncraft.net
2014-03-20 17:46:54 send version message: version 70003, blocks=8737, us=0.0.0.0:0, them=184.154.116.146:13931, peer=184.154.116.146:13931
2014-03-20 17:46:55 receive version message: /Satoshi:1.3.0.2/: version 70003, blocks=66493, us=62.44.208.15:53068, them=184.154.116.146:13931, peer=184.154.116.146:13931
2014-03-20 17:46:59 received block 4f28348ee7816ee9ffd5d9702383b5a8b7bd5d336f90fcea1ca36c6f9bfd5e4e
2014-03-20 17:46:59 ProcessBlock: ORPHAN BLOCK, prev=7b5c65bba4c23236b26225c20644b38bd1f6f93e5333b30c0e33e352d3c83ae6
2014-03-20 17:46:59 received block 47aca5654f4115862ed20fe6c69f585b736eb09dff74eee30202af39a3f01583

I watched the debug log on the cga.inceptioncraft.net node to see what was happening with our connection. Here's the relevant part:
2014-03-20 18:22:06 getblocks 8501 to daf25d32e91b5316bc7e3cf9ed1f444a7142e52e6401dd8a3f89aabf2257dd30 limit 500
2014-03-20 18:22:06 getblocks stopping at limit 9000 7b5c65bba4c23236b26225c20644b38bd1f6f93e5333b30c0e33e352d3c83ae6
2014-03-20 18:22:07 received getdata (500 invsz)
2014-03-20 18:22:09 socket closed
2014-03-20 18:22:09 disconnecting node 62.44.208.15:53107

Please try renaming your ~/.cryptographicanomaly/ directory to something else. Make sure you back up your wallet first. If your wallet is still unable to sync, please try recloning the source from our github repo and doing a fresh compile. If you are STILL unable to get past this point, please join #cganomaly on Freenode IRC so we can troubleshoot more in depth. Here's a link: https://kiwiirc.com/client/irc.freenode.net/#cganomaly

s4w3d0ff

sr. member

Activity: 322

Merit: 250

Spray and Pray

Quote from: Zuikkis on March 20, 2014, 01:12:55 PM

Quote from: s4w3d0ff on March 20, 2014, 01:05:20 PM

Quote from: Zuikkis on March 20, 2014, 12:54:02 PM

Still stuck at 8737.. Sad

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.

That's exactly what I did. Here is the problem part from the log:

Code:

2014-03-20 17:46:51 received block 361031959e1085697e2e46417d26bcad3d9e9a7b7fc63ec2ac53aa386c494763
2014-03-20 17:46:51 nActualTimespan = 639 before bounds
2014-03-20 17:46:51 GetNextWorkRequired RETARGET
2014-03-20 17:46:51 nTargetTimespan = 80 nActualTimespan = 320
2014-03-20 17:46:51 Before: 1d02826c 00000002826c0000000000000000000000000000000000000000000000000000
2014-03-20 17:46:51 After: 1d0a09b0 0000000a09b00000000000000000000000000000000000000000000000000000
2014-03-20 17:46:51 ERROR: ConnectBlock() : coinbase pays too much (actual=100000000 vs limit=0)
2014-03-20 17:46:51 InvalidChainFound: invalid block=361031959e1085697e2e46417d26bcad3d9e9a7b7fc63ec2ac53aa386c494763 height=8738 log2_work=44.74319 date=2014-02-07 11:12:39
2014-03-20 17:46:51 InvalidChainFound: current best=73f3147fadd913980617b8a5bdea301e0c0a5ef3434eec693ecaca0bb62b4604 height=8737 log2_work=44.743169 date=2014-02-07 11:22:25
2014-03-20 17:46:51 InvalidChainFound: invalid block=361031959e1085697e2e46417d26bcad3d9e9a7b7fc63ec2ac53aa386c494763 height=8738 log2_work=44.74319 date=2014-02-07 11:12:39
2014-03-20 17:46:51 InvalidChainFound: current best=73f3147fadd913980617b8a5bdea301e0c0a5ef3434eec693ecaca0bb62b4604 height=8737 log2_work=44.743169 date=2014-02-07 11:22:25
2014-03-20 17:46:51 ERROR: SetBestBlock() : ConnectBlock 361031959e1085697e2e46417d26bcad3d9e9a7b7fc63ec2ac53aa386c494763 failed
2014-03-20 17:46:51 ERROR: AcceptBlock() : AddToBlockIndex failed
2014-03-20 17:46:51 ERROR: ProcessBlock() : AcceptBlock FAILED
2014-03-20 17:46:51 Misbehaving: 184.154.116.146:13931 (0 -> 100) DISCONNECTING
2014-03-20 17:46:51 disconnecting node cga.inceptioncraft.net
2014-03-20 17:46:54 trying connection cga.inceptioncraft.net lastseen=0.0hrs
2014-03-20 17:46:54 connected cga.inceptioncraft.net
2014-03-20 17:46:54 send version message: version 70003, blocks=8737, us=0.0.0.0:0, them=184.154.116.146:13931, peer=184.154.116.146:13931
2014-03-20 17:46:55 receive version message: /Satoshi:1.3.0.2/: version 70003, blocks=66493, us=62.44.208.15:53068, them=184.154.116.146:13931, peer=184.154.116.146:13931
2014-03-20 17:46:59 received block 4f28348ee7816ee9ffd5d9702383b5a8b7bd5d336f90fcea1ca36c6f9bfd5e4e
2014-03-20 17:46:59 ProcessBlock: ORPHAN BLOCK, prev=7b5c65bba4c23236b26225c20644b38bd1f6f93e5333b30c0e33e352d3c83ae6
2014-03-20 17:46:59 received block 47aca5654f4115862ed20fe6c69f585b736eb09dff74eee30202af39a3f01583

Sorry should of added that you need to delete the chainstate folder as well. Try it one more time.

Zuikkis

newbie

Activity: 57

Merit: 0

Quote from: s4w3d0ff on March 20, 2014, 01:05:20 PM

Quote from: Zuikkis on March 20, 2014, 12:54:02 PM

Still stuck at 8737.. Sad

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.

That's exactly what I did. Here is the problem part from the log:

Code:

2014-03-20 17:46:51 received block 361031959e1085697e2e46417d26bcad3d9e9a7b7fc63ec2ac53aa386c494763
2014-03-20 17:46:51 nActualTimespan = 639 before bounds
2014-03-20 17:46:51 GetNextWorkRequired RETARGET
2014-03-20 17:46:51 nTargetTimespan = 80 nActualTimespan = 320
2014-03-20 17:46:51 Before: 1d02826c 00000002826c0000000000000000000000000000000000000000000000000000
2014-03-20 17:46:51 After: 1d0a09b0 0000000a09b00000000000000000000000000000000000000000000000000000
2014-03-20 17:46:51 ERROR: ConnectBlock() : coinbase pays too much (actual=100000000 vs limit=0)
2014-03-20 17:46:51 InvalidChainFound: invalid block=361031959e1085697e2e46417d26bcad3d9e9a7b7fc63ec2ac53aa386c494763 height=8738 log2_work=44.74319 date=2014-02-07 11:12:39
2014-03-20 17:46:51 InvalidChainFound: current best=73f3147fadd913980617b8a5bdea301e0c0a5ef3434eec693ecaca0bb62b4604 height=8737 log2_work=44.743169 date=2014-02-07 11:22:25
2014-03-20 17:46:51 InvalidChainFound: invalid block=361031959e1085697e2e46417d26bcad3d9e9a7b7fc63ec2ac53aa386c494763 height=8738 log2_work=44.74319 date=2014-02-07 11:12:39
2014-03-20 17:46:51 InvalidChainFound: current best=73f3147fadd913980617b8a5bdea301e0c0a5ef3434eec693ecaca0bb62b4604 height=8737 log2_work=44.743169 date=2014-02-07 11:22:25
2014-03-20 17:46:51 ERROR: SetBestBlock() : ConnectBlock 361031959e1085697e2e46417d26bcad3d9e9a7b7fc63ec2ac53aa386c494763 failed
2014-03-20 17:46:51 ERROR: AcceptBlock() : AddToBlockIndex failed
2014-03-20 17:46:51 ERROR: ProcessBlock() : AcceptBlock FAILED
2014-03-20 17:46:51 Misbehaving: 184.154.116.146:13931 (0 -> 100) DISCONNECTING
2014-03-20 17:46:51 disconnecting node cga.inceptioncraft.net
2014-03-20 17:46:54 trying connection cga.inceptioncraft.net lastseen=0.0hrs
2014-03-20 17:46:54 connected cga.inceptioncraft.net
2014-03-20 17:46:54 send version message: version 70003, blocks=8737, us=0.0.0.0:0, them=184.154.116.146:13931, peer=184.154.116.146:13931
2014-03-20 17:46:55 receive version message: /Satoshi:1.3.0.2/: version 70003, blocks=66493, us=62.44.208.15:53068, them=184.154.116.146:13931, peer=184.154.116.146:13931
2014-03-20 17:46:59 received block 4f28348ee7816ee9ffd5d9702383b5a8b7bd5d336f90fcea1ca36c6f9bfd5e4e
2014-03-20 17:46:59 ProcessBlock: ORPHAN BLOCK, prev=7b5c65bba4c23236b26225c20644b38bd1f6f93e5333b30c0e33e352d3c83ae6
2014-03-20 17:46:59 received block 47aca5654f4115862ed20fe6c69f585b736eb09dff74eee30202af39a3f01583

s4w3d0ff

sr. member

Activity: 322

Merit: 250

Spray and Pray

Quote from: Zuikkis on March 20, 2014, 12:54:02 PM

Still stuck at 8737.. Sad

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.

tertius993

hero member

Activity: 1029

Merit: 712

Quote from: Zuikkis on March 20, 2014, 12:54:02 PM

Still stuck at 8737.. Sad

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?

Latest is 1.3.0.2, and yes I fully synch'd my wallet with that version.

Zuikkis

newbie

Activity: 57

Merit: 0

Still stuck at 8737.. Sad

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?

Cor2

hero member

Activity: 595

Merit: 500

Quote from: Zuikkis on March 20, 2014, 06:42:13 AM

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 before
to 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=0
connect=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,

s4w3d0ff

sr. member

Activity: 322

Merit: 250

Spray and Pray

Quote from: cdboot on March 20, 2014, 07:09:07 AM

Quote from: polmax on March 20, 2014, 06:24:26 AM

I think it would be worthwhile to create posts on other forums to get more followers CGA

and who have the ability to create posts in other languages

Chinese,
German,
Russian,
Spanish,
French,
Hebrew ++...

Yes

This should be done this project before March

I agree, So if anyone is proficient in writing another language and English, please help us out and write up a post in your language and lets get CGA rolling!

tf2honeybadger

full member

Activity: 189

Merit: 100

Quote from: Zuikkis on March 20, 2014, 06:42:13 AM

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.

This is the output from "cryptographicanomalyd getinfo":

Code:

{
"version" : 1030002,
"protocolversion" : 70003,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 8737,
"timeoffset" : 0,
"connections" : 4,
"proxy" : "",
"difficulty" : 0.39848595,
"testnet" : false,
"keypoololdest" : 1395311078,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
}

And this is my config:

Code:

server=1
listen=1
rpcuser=xxxx
rpcpassword=yyyy
rpcport=13932
rpcallowip=192.168.0.*

Please delete your blocks/, chainstate/, and peers.dat file and then try resyncing with the network. Otherwise, you may just keep connecting to the same forked node.

cdboot

full member

Activity: 182

Merit: 100

Quote from: polmax on March 20, 2014, 06:24:26 AM

I think it would be worthwhile to create posts on other forums to get more followers CGA

and who have the ability to create posts in other languages

Chinese,
German,
Russian,
Spanish,
French,
Hebrew ++...

Yes

This should be done this project before March

Zuikkis

newbie

Activity: 57

Merit: 0

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.

This is the output from "cryptographicanomalyd getinfo":

Code:

{
"version" : 1030002,
"protocolversion" : 70003,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 8737,
"timeoffset" : 0,
"connections" : 4,
"proxy" : "",
"difficulty" : 0.39848595,
"testnet" : false,
"keypoololdest" : 1395311078,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
}

And this is my config:

Code:

server=1
listen=1
rpcuser=xxxx
rpcpassword=yyyy
rpcport=13932
rpcallowip=192.168.0.*

polmax

member

Activity: 66

Merit: 10

I think it would be worthwhile to create posts on other forums to get more followers CGA

and who have the ability to create posts in other languages

Chinese,
German,
Russian,
Spanish,
French,
Hebrew ++...

brother3

hero member

Activity: 980

Merit: 500

Quote from: awesomeperson451 on March 19, 2014, 10:11:23 PM

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 guess it's about time I get new contacts.

Oh no!!!! You did not!!!! Undecided

tf2honeybadger

full member

Activity: 189

Merit: 100

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.

cdboot

full member

Activity: 182

Merit: 100

Quote from: s4w3d0ff on March 19, 2014, 10:42:27 PM

Quote from: cdboot on March 19, 2014, 10:36:05 PM

Quote from: s4w3d0ff on March 19, 2014, 10:18:56 PM

Quote from: awesomeperson451 on March 19, 2014, 10:11:23 PM

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. Grin

Hey, try to get on the cryptsy, this will cause the attention of bter.com Cheesy

s4w3d0ff

sr. member

Activity: 322

Merit: 250

Spray and Pray

Quote from: cdboot on March 19, 2014, 10:36:05 PM

Quote from: s4w3d0ff on March 19, 2014, 10:18:56 PM

Quote from: awesomeperson451 on March 19, 2014, 10:11:23 PM

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.

cdboot

full member

Activity: 182

Merit: 100

Quote from: s4w3d0ff on March 19, 2014, 10:18:56 PM

Quote from: awesomeperson451 on March 19, 2014, 10:11:23 PM

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

s4w3d0ff

sr. member

Activity: 322

Merit: 250

Spray and Pray

Quote from: awesomeperson451 on March 19, 2014, 10:11:23 PM

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!

awesomeperson451

newbie

Activity: 28

Merit: 0

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 guess it's about time I get new contacts.

forzendiablo

legendary

Activity: 1526

Merit: 1000

the grandpa of cryptos

luving this coin!

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