[ANN][CLAM] CLAMs, Proof-Of-Chain, Proof-Of-Working-Stake, a.k.a. "Clamcoin"

[Bitcoiner2015]

I'm sure it's been mentioned before, but could the digger be Mt. Gox, or representatives of them involved in the liquidation settlements?
They must have a lot of addresses that weren't dust at the time of CLAMs creation.

Otherwise who has so many none dust accounts?  I am holding, there have been big diggers before, and it will happen again, but that is part of CLAMs.

Sites like walletexplorer.com and scorechain.com can 'cluster' addresses based on their blockchain history. Doing so suggests this digging isn't using Gox addresses.

Who does it suggest it may be? or is there no one specific that can be found?

[1714737495]

1714737495

[1714737495]

1714737495

[1714737495]

1714737495

[1714737495]

1714737495

[chilly2k]

   I thought we had the website set up as a WIKI, but I can't seem to find it. 

  I just got the wallet setup on a Raspberry Pi and got a stake on it.  I wanted to create an install guide to help anyone else trying to do this.  The daemon compile is pretty straight forward, but there are a few gotcha's that would be nice to see all in one place... 

[SuperClam]

   I thought we had the website set up as a WIKI, but I can't seem to find it. 

  I just got the wallet setup on a Raspberry Pi and got a stake on it.  I wanted to create an install guide to help anyone else trying to do this.  The daemon compile is pretty straight forward, but there are a few gotcha's that would be nice to see all in one place... 

The website is just markdown, live compiled from the github repository here:

Website Repository


Example page:

Code:

http://clamclient.com/start/

Raw https://github.com/nochowderforyou/nochowderforyou.github.io/start/index.md

[chilly2k]

Just noticed a weird problem...  running 1.4.17

I fired up my old client on a different box and it caught-up to the block chain and processed these fine.  I shut that down and started this guy back up and now it's running  fine.  Any clue what was happening there?  This is a new Raspberry Pi daemon, so I've been watching very closely.  This was running fine for around 18 hours. 

Code:

2015-10-30 18:54:35 SetBestChain: new best=3f5c063a6a5cae2d744656415f8bbf78d3ec0d93bdd90f02d56b08f66cb9438a  height=708540  trust=95795426480965258601  blocktrust=394397162270365  date=10/30/15 18:54:24
2015-10-30 18:54:35 ProcessBlock: ACCEPTED
2015-10-30 18:54:36 ERROR: FetchInputs() : 2735bdf592b697b34a4ce9533ff0af647342b660da6779dae75bd4d4c43dcb15 mempool Tx prev not found 467a9d7a17de112f1766d53b32ee57f3869c6c2d04d1468870d6f5a2b8345d1d
2015-10-30 18:54:41 stake took 0s
2015-10-30 18:54:44 ERROR: FetchInputs() : 2735bdf592b697b34a4ce9533ff0af647342b660da6779dae75bd4d4c43dcb15 mempool Tx prev not found 467a9d7a17de112f1766d53b32ee57f3869c6c2d04d1468870d6f5a2b8345d1d
2015-10-30 18:54:48 ERROR: FetchInputs() : 2735bdf592b697b34a4ce9533ff0af647342b660da6779dae75bd4d4c43dcb15 mempool Tx prev not found 467a9d7a17de112f1766d53b32ee57f3869c6c2d04d1468870d6f5a2b8345d1d
2015-10-30 18:54:53 ERROR: FetchInputs() : 2735bdf592b697b34a4ce9533ff0af647342b660da6779dae75bd4d4c43dcb15 mempool Tx prev not found 467a9d7a17de112f1766d53b32ee57f3869c6c2d04d1468870d6f5a2b8345d1d
2015-10-30 18:54:56 ERROR: FetchInputs() : 2735bdf592b697b34a4ce9533ff0af647342b660da6779dae75bd4d4c43dcb15 mempool Tx prev not found 467a9d7a17de112f1766d53b32ee57f3869c6c2d04d1468870d6f5a2b8345d1d
2015-10-30 18:54:57 stake took 0s
2015-10-30 18:55:01 ERROR: FetchInputs() : 2735bdf592b697b34a4ce9533ff0af647342b660da6779dae75bd4d4c43dcb15 prev tx 467a9d7a17de112f1766d53b32ee57f3869c6c2d04d1468870d6f5a2b8345d1d index entry not found
2015-10-30 18:55:01 InvalidChainFound: invalid block=a22b8c842f7e4855331f564e686db009fb3e464109bd789f8a8dd490d9fd9b8d  height=708541  trust=95795821283295403912  blocktrust=394802330145311  date=10/30/15 18:54:56
2015-10-30 18:55:01 InvalidChainFound:  current best=3f5c063a6a5cae2d744656415f8bbf78d3ec0d93bdd90f02d56b08f66cb9438a  height=708540  trust=95795426480965258601  blocktrust=394397162270365  date=10/30/15 18:54:24
2015-10-30 18:55:01 ERROR: SetBestChain() : SetBestChainInner failed
2015-10-30 18:55:01 ERROR: AcceptBlock() : AddToBlockIndex failed
2015-10-30 18:55:01 ERROR: ProcessBlock() : AcceptBlock FAILED
2015-10-30 18:55:05 ERROR: FetchInputs() : 2735bdf592b697b34a4ce9533ff0af647342b660da6779dae75bd4d4c43dcb15 mempool Tx prev not found 467a9d7a17de112f1766d53b32ee57f3869c6c2d04d1468870d6f5a2b8345d1d
2015-10-30 18:55:13 stake took 0s
2015-10-30 18:55:30 stake took 1s
2015-10-30 18:55:45 Postponing 1 reconnects
2015-10-30 18:55:45 REORGANIZE
2015-10-30 18:55:45 REORGANIZE: Disconnect 0 blocks; 3f5c063a6a5cae2d744656415f8bbf78d3ec0d93bdd90f02d56b08f66cb9438a..3f5c063a6a5cae2d744656415f8bbf78d3ec0d93bdd90f02d56b08f66cb9438a
2015-10-30 18:55:45 REORGANIZE: Connect 1 blocks; 3f5c063a6a5cae2d744656415f8bbf78d3ec0d93bdd90f02d56b08f66cb9438a..a22b8c842f7e4855331f564e686db009fb3e464109bd789f8a8dd490d9fd9b8d
2015-10-30 18:55:45 ERROR: FetchInputs() : 2735bdf592b697b34a4ce9533ff0af647342b660da6779dae75bd4d4c43dcb15 prev tx 467a9d7a17de112f1766d53b32ee57f3869c6c2d04d1468870d6f5a2b8345d1d index entry not found
2015-10-30 18:55:45 ERROR: Reorganize() : ConnectBlock a22b8c842f7e4855331f564e686db009fb3e464109bd789f8a8dd490d9fd9b8d failed
2015-10-30 18:55:45 InvalidChainFound: invalid block=401a920919215869d558be3528cc43ecc4fa6c614f5cbf75a0dac4a4860fff25  height=708542  trust=95796216491626745705  blocktrust=395208331341793  date=10/30/15 18:55:44
2015-10-30 18:55:45 InvalidChainFound:  current best=3f5c063a6a5cae2d744656415f8bbf78d3ec0d93bdd90f02d56b08f66cb9438a  height=708540  trust=95795426480965258601  blocktrust=394397162270365  date=10/30/15 18:54:24
2015-10-30 18:55:45 ERROR: SetBestChain() : Reorganize failed
2015-10-30 18:55:45 ERROR: AcceptBlock() : AddToBlockIndex failed
2015-10-30 18:55:45 ERROR: ProcessBlock() : AcceptBlock FAILED
2015-10-30 18:55:46 stake took 1s
2015-10-30 18:56:01 stake took 0s
2015-10-30 18:56:17 stake took 0s
2015-10-30 18:56:33 stake took 0s
2015-10-30 18:56:34 Postponing 2 reconnects
2015-10-30 18:56:34 REORGANIZE
2015-10-30 18:56:34 REORGANIZE: Disconnect 0 blocks; 3f5c063a6a5cae2d744656415f8bbf78d3ec0d93bdd90f02d56b08f66cb9438a..3f5c063a6a5cae2d744656415f8bbf78d3ec0d93bdd90f02d56b08f66cb9438a
2015-10-30 18:56:34 REORGANIZE: Connect 1 blocks; 3f5c063a6a5cae2d744656415f8bbf78d3ec0d93bdd90f02d56b08f66cb9438a..a22b8c842f7e4855331f564e686db009fb3e464109bd789f8a8dd490d9fd9b8d
2015-10-30 18:56:34 ERROR: FetchInputs() : 2735bdf592b697b34a4ce9533ff0af647342b660da6779dae75bd4d4c43dcb15 prev tx 467a9d7a17de112f1766d53b32ee57f3869c6c2d04d1468870d6f5a2b8345d1d index entry not found
2015-10-30 18:56:34 ERROR: Reorganize() : ConnectBlock a22b8c842f7e4855331f564e686db009fb3e464109bd789f8a8dd490d9fd9b8d failed
2015-10-30 18:56:34 InvalidChainFound: invalid block=5811802af96f11fd29e126e55e25682e7e73653d8575d2500e50dc1d55743019  height=708543  trust=95796612106795179040  blocktrust=395615168433335  date=10/30/15 18:56:32
2015-10-30 18:56:34 InvalidChainFound:  current best=3f5c063a6a5cae2d744656415f8bbf78d3ec0d93bdd90f02d56b08f66cb9438a  height=708540  trust=95795426480965258601  blocktrust=394397162270365  date=10/30/15 18:54:24
2015-10-30 18:56:34 ERROR: SetBestChain() : Reorganize failed
2015-10-30 18:56:34 ERROR: AcceptBlock() : AddToBlockIndex failed
2015-10-30 18:56:34 ERROR: ProcessBlock() : AcceptBlock FAILED
2015-10-30 18:56:35 ERROR: FetchInputs() : 2735bdf592b697b34a4ce9533ff0af647342b660da6779dae75bd4d4c43dcb15 mempool Tx prev not found 467a9d7a17de112f1766d53b32ee57f3869c6c2d04d1468870d6f5a2b8345d1d
2015-10-30 18:56:43 ERROR: FetchInputs() : 2735bdf592b697b34a4ce9533ff0af647342b660da6779dae75bd4d4c43dcb15 mempool Tx prev not found 467a9d7a17de112f1766d53b32ee57f3869c6c2d04d1468870d6f5a2b8345d1d
2015-10-30 18:56:49 stake took 0s
2015-10-30 18:57:06 stake took 1s
2015-10-30 18:57:14 ERROR: FetchInputs() : 2735bdf592b697b34a4ce9533ff0af647342b660da6779dae75bd4d4c43dcb15 mempool Tx prev not found 467a9d7a17de112f1766d53b32ee57f3869c6c2d04d1468870d6f5a2b8345d1d
2015-10-30 18:57:21 stake took 0s
2015-10-30 18:57:29 Postponing 3 reconnects
2015-10-30 18:57:29 REORGANIZE
2015-10-30 18:57:29 REORGANIZE: Disconnect 0 blocks; 3f5c063a6a5cae2d744656415f8bbf78d3ec0d93bdd90f02d56b08f66cb9438a..3f5c063a6a5cae2d744656415f8bbf78d3ec0d93bdd90f02d56b08f66cb9438a
2015-10-30 18:57:29 REORGANIZE: Connect 1 blocks; 3f5c063a6a5cae2d744656415f8bbf78d3ec0d93bdd90f02d56b08f66cb9438a..a22b8c842f7e4855331f564e686db009fb3e464109bd789f8a8dd490d9fd9b8d
2015-10-30 18:57:29 ERROR: FetchInputs() : 2735bdf592b697b34a4ce9533ff0af647342b660da6779dae75bd4d4c43dcb15 prev tx 467a9d7a17de112f1766d53b32ee57f3869c6c2d04d1468870d6f5a2b8345d1d index entry not found
2015-10-30 18:57:29 ERROR: Reorganize() : ConnectBlock a22b8c842f7e4855331f564e686db009fb3e464109bd789f8a8dd490d9fd9b8d failed
2015-10-30 18:57:29 InvalidChainFound: invalid block=45ea26b6c5e277023f30a7bec65eb5c12065d759bcd0d00d16895c64571cf04f  height=708544  trust=95797008129639183109  blocktrust=396022844004069  date=10/30/15 18:57:20
2015-10-30 18:57:29 InvalidChainFound:  current best=3f5c063a6a5cae2d744656415f8bbf78d3ec0d93bdd90f02d56b08f66cb9438a  height=708540  trust=95795426480965258601  blocktrust=394397162270365  date=10/30/15 18:54:24
2015-10-30 18:57:29 ERROR: SetBestChain() : Reorganize failed
2015-10-30 18:57:29 ERROR: AcceptBlock() : AddToBlockIndex failed
2015-10-30 18:57:29 ERROR: ProcessBlock() : AcceptBlock FAILED
2015-10-30 18:57:37 stake took 0s
2015-10-30 18:57:53 stake took 0s
2015-10-30 18:57:57 Postponing 4 reconnects
2015-10-30 18:57:57 REORGANIZE
2015-10-30 18:57:57 REORGANIZE: Disconnect 0 blocks; 3f5c063a6a5cae2d744656415f8bbf78d3ec0d93bdd90f02d56b08f66cb9438a..3f5c063a6a5cae2d744656415f8bbf78d3ec0d93bdd90f02d56b08f66cb9438a
2015-10-30 18:57:57 REORGANIZE: Connect 1 blocks; 3f5c063a6a5cae2d744656415f8bbf78d3ec0d93bdd90f02d56b08f66cb9438a..a22b8c842f7e4855331f564e686db009fb3e464109bd789f8a8dd490d9fd9b8d
2015-10-30 18:57:57 ERROR: FetchInputs() : 2735bdf592b697b34a4ce9533ff0af647342b660da6779dae75bd4d4c43dcb15 prev tx 467a9d7a17de112f1766d53b32ee57f3869c6c2d04d1468870d6f5a2b8345d1d index entry not found
2015-10-30 18:57:57 ERROR: Reorganize() : ConnectBlock a22b8c842f7e4855331f564e686db009fb3e464109bd789f8a8dd490d9fd9b8d failed
2015-10-30 18:57:57 InvalidChainFound: invalid block=be297a55e10d467734b2b1f238aa7c39d1a1e81ee0fb003bf3c558a8e3c9c2b8  height=708545  trust=95797404356636212698  blocktrust=396226997029589  date=10/30/15 18:57:52
2015-10-30 18:57:57 InvalidChainFound:  current best=3f5c063a6a5cae2d744656415f8bbf78d3ec0d93bdd90f02d56b08f66cb9438a  height=708540  trust=95795426480965258601  blocktrust=394397162270365  date=10/30/15 18:54:24
2015-10-30 18:57:57 ERROR: SetBestChain() : Reorganize failed
2015-10-30 18:57:57 ERROR: AcceptBlock() : AddToBlockIndex failed
2015-10-30 18:57:57 ERROR: ProcessBlock() : AcceptBlock FAILED
2015-10-30 18:58:10 stake took 1s
2015-10-30 18:58:26 stake took 1s

[dooglus]

I fired up my old client on a different box and it caught-up to the block chain and processed these fine.  I shut that down and started this guy back up and now it's running  fine.  Any clue what was happening there?

Code:

2015-10-30 18:54:44 ERROR: FetchInputs() : 2735bdf592b697b34a4ce9533ff0af647342b660da6779dae75bd4d4c43dcb15 mempool Tx prev not found 467a9d7a17de112f1766d53b32ee57f3869c6c2d04d1468870d6f5a2b8345d1d
2015-10-30 18:54:48 ERROR: FetchInputs() : 2735bdf592b697b34a4ce9533ff0af647342b660da6779dae75bd4d4c43dcb15 mempool Tx prev not found 467a9d7a17de112f1766d53b32ee57f3869c6c2d04d1468870d6f5a2b8345d1d
2015-10-30 18:54:53 ERROR: FetchInputs() : 2735bdf592b697b34a4ce9533ff0af647342b660da6779dae75bd4d4c43dcb15 mempool Tx prev not found 467a9d7a17de112f1766d53b32ee57f3869c6c2d04d1468870d6f5a2b8345d1d

No idea. It's saying that the new 2735... tx is invalid because it spends a coin from tx 467a which it doesn't know about, but that 467a transaction is in block 699197 (2015-10-24 05:55:12), so I've no idea why it couldn't find it, or why restarting would fix it.

[Wintermute420]

I downloaded the client earlier in the week and started syncing, but I am stuck at 21 weeks behind.  Can somebody provide me with a current list of nodes?  Thanks in advance.

[SuperClam]

I downloaded the client earlier in the week and started syncing, but I am stuck at 21 weeks behind.  Can somebody provide me with a current list of nodes?  Thanks in advance.

If you have the newest version of the client, from the repository - it should automatically get an up-to-date list of active nodes.

[Wintermute420]

I grabbed it from the link on the front of this thread.  It looks it is syncing after a restart and adding the nodes.  20 weeks behind now, I see higher network activity from clam-qt.  Thanks for your help.

[romjpn]

Aaand it's dropping again. 

[SuperClam]

Aaand it's dropping again. 

And yet, the asks spread thinner. 
Currently, 44 BTC in purchases to a price of 0.01 BTC.

At a certain point a large portion of the entire CLAM moneysupply is purchasable for a 'relatively' small amount of BTC.
Not attempting to make price predictions - simply pointing out the fact that the distribution is no less conservative.

Fundamentals haven't drastically changed with the exception of a large amount of CLAM, which already existed, coming into circulation via claims.

[BayAreaCoins]

Aaand it's dropping again.  

And yet, the asks spread thinner.  
Currently, 44 BTC in purchases to a price of 0.01 BTC.

At a certain point a large portion of the entire CLAM moneysupply is purchasable for a 'relatively' small amount of BTC.
Not attempting to make price predictions - simply pointing out the fact that the distribution is no less conservative.

Fundamentals haven't drastically changed with the exception of a large amount of CLAM, which already existed, coming into circulation via claims.

Need a 300 Bitcoin wall @ .001....

Someone needs to nut up and get this shit done.  (I got my bid in my service)

I'm standing tall on it and I expect other people around the project to hold firm or else all your digs are belong to Clamchecker!  

[SuperClam]

Aaand it's dropping again.  

And yet, the asks spread thinner.  
Currently, 44 BTC in purchases to a price of 0.01 BTC.
At a certain point a large portion of the entire CLAM moneysupply is purchasable for a 'relatively' small amount of BTC.
Not attempting to make price predictions - simply pointing out the fact that the distribution is no less conservative.
Fundamentals haven't drastically changed with the exception of a large amount of CLAM, which already existed, coming into circulation via claims.

Need a 300 Bitcoin wall @ .001....
Someone needs to nut up and get this shit done.  (I got my bid in my service)
I'm standing tall on it and I expect other people around the project to hold firm or else all your digs are belong to Clamchecker!  

No one is going anywhere - this is our network.

When this is all finished we can thank the digger for increasing the money supply and hence the coefficient for 'market cap'

EDIT:
My 142% biased prediction that no one should pay any attention to: 5 million market cap within two months of the digger finishing 

[crazyivan]

Aaand it's dropping again.  

And yet, the asks spread thinner.  
Currently, 44 BTC in purchases to a price of 0.01 BTC.
At a certain point a large portion of the entire CLAM moneysupply is purchasable for a 'relatively' small amount of BTC.
Not attempting to make price predictions - simply pointing out the fact that the distribution is no less conservative.
Fundamentals haven't drastically changed with the exception of a large amount of CLAM, which already existed, coming into circulation via claims.

Need a 300 Bitcoin wall @ .001....
Someone needs to nut up and get this shit done.  (I got my bid in my service)
I'm standing tall on it and I expect other people around the project to hold firm or else all your digs are belong to Clamchecker!  

No one is going anywhere - this is our network.

When this is all finished we can thank the digger for increasing the money supply and hence the coefficient for 'market cap'

EDIT:
My 142% biased prediction that no one should pay any attention to: 5 million market cap within two months of the digger finishing 

When do you expect him to finish? Also, how do you know his total supply?

[tspacepilot]

Aaand it's dropping again.  

And yet, the asks spread thinner.  
Currently, 44 BTC in purchases to a price of 0.01 BTC.
At a certain point a large portion of the entire CLAM moneysupply is purchasable for a 'relatively' small amount of BTC.
Not attempting to make price predictions - simply pointing out the fact that the distribution is no less conservative.
Fundamentals haven't drastically changed with the exception of a large amount of CLAM, which already existed, coming into circulation via claims.

Need a 300 Bitcoin wall @ .001....
Someone needs to nut up and get this shit done.  (I got my bid in my service)
I'm standing tall on it and I expect other people around the project to hold firm or else all your digs are belong to Clamchecker!  

No one is going anywhere - this is our network.

When this is all finished we can thank the digger for increasing the money supply and hence the coefficient for 'market cap'

EDIT:
My 142% biased prediction that no one should pay any attention to: 5 million market cap within two months of the digger finishing 

When do you expect him to finish? Also, how do you know his total supply?

We know an upper bound on it (the amount of clams deposited in the initial distribution).  That may be large, but it's finite and in theory, it was expected to be hit sooner or later.  Everyone is fretting about uncertainty and whatnot, if someone digs up all the CLAMS, that removes uncertainty about how many are left to be dug.

[dooglus]

I find it hard sometimes to understand what you're saying.

Need a 300 Bitcoin wall @ .001....

Who needs a 300 BTC wall, and why? It sounds like you're encouraging us to buy the digger's CLAMs for more than it will be necessary to spend. Who does that benefit?

Someone needs to nut up and get this shit done.  (I got my bid in my service)

"Nut up" as in "grow a pair"? It's not fear that's stopping me from paying 0.001 for all the digger's remaining CLAMs. I think he's going to end up selling them cheaper than that. I don't see any reason to pay more than is necessary for them.

Once the price falls below 0.001 per CLAM, your offer of 0.005 BTC per private key means that you will be losing money every time someone uses your service. How many digs are you prepared to handle if you're losing 0.002 BTC for each one? Let's say the digger has 50k private keys left. Would you buy them off him for 0.005 BTC each, losing 100 BTC in the process? I think that's what you have claimed in the past, that you will continue paying 0.005 BTC per private key even if it means taking a loss.

I'm standing tall on it and I expect other people around the project to hold firm or else all your digs are belong to Clamchecker!  

"Holding firm" doesn't really mean anything. There's no reason to try to keep the price artificially high in the face of constant sell pressure. It is best to allow the price to fall so as little value as possible leaves the community. Buying private keys for over 100% of their value is even more silly than offering to buy them for less than 20% of their value.

[Noolz39]

CLAMs prise go to 0.0009 or less
see it soon

[andulolika]

Aaand it's dropping again.  

And yet, the asks spread thinner.  
Currently, 44 BTC in purchases to a price of 0.01 BTC.
At a certain point a large portion of the entire CLAM moneysupply is purchasable for a 'relatively' small amount of BTC.
Not attempting to make price predictions - simply pointing out the fact that the distribution is no less conservative.
Fundamentals haven't drastically changed with the exception of a large amount of CLAM, which already existed, coming into circulation via claims.

Need a 300 Bitcoin wall @ .001....
Someone needs to nut up and get this shit done.  (I got my bid in my service)
I'm standing tall on it and I expect other people around the project to hold firm or else all your digs are belong to Clamchecker!  

No one is going anywhere - this is our network.

When this is all finished we can thank the digger for increasing the money supply and hence the coefficient for 'market cap'

EDIT:
My 142% biased prediction that no one should pay any attention to: 5 million market cap within two months of the digger finishing  

Finally someone that agrees that this is good for clam, and for all of us who want cheap clams, after the digger we will only need to worry bout bac.

Aaand it's dropping again. 

And yet, the asks spread thinner. 
Currently, 44 BTC in purchases to a price of 0.01 BTC.

At a certain point a large portion of the entire CLAM moneysupply is purchasable for a 'relatively' small amount of BTC.
Not attempting to make price predictions - simply pointing out the fact that the distribution is no less conservative.

Fundamentals haven't drastically changed with the exception of a large amount of CLAM, which already existed, coming into circulation via claims.

Need a 300 Bitcoin wall @ .001....

Someone needs to nut up and get this shit done.  (I got my bid in my service)

I'm standing tall on it and I expect other people around the project to hold firm or else all your digs are belong to Clamchecker!   

Yeah im pretty sure there will be some support there.

[BayAreaCoins]

Once the price falls below 0.001 per CLAM, your offer of 0.005 BTC per private key means that you will be losing money every time someone uses your service. How many digs are you prepared to handle if you're losing 0.002 BTC for each one? Let's say the digger has 50k private keys left. Would you buy them off him for 0.005 BTC each, losing 100 BTC in the process? I think that's what you have claimed in the past, that you will continue paying 0.005 BTC per private key even if it means taking a loss.

We will most likely be purchasing 30,000-100,000 fresh Clamcoins at a "loss" (this could change of course because of shit going on in life & other markets... but that is my goal.)

Here is our hot for purchasing fresh clammies & paying affiliates: https://blockchain.info/address/18U3uQqGviBHAfExC8iQQE9i6mcUtkc5q8

"Holding firm" doesn't really mean anything. There's no reason to try to keep the price artificially high in the face of constant sell pressure. It is best to allow the price to fall so as little value as possible leaves the community. Buying private keys for over 100% of their value is even more silly than offering to buy them for less than 20% of their value.

Sometimes you have to "lose" today to "win" tomorrow with trading.

It reminds me when I first bought into CLAM... I "lost" over 50% because I slapped the Ask, but if I would have only sat on the Bid then I wouldn't have acquired the number of Clamcoins that I did... Well looking back at that "50% loss" I must say I'm fairly pleased .

(My earlier post wasn't intended as being shitty or anything... this market just needs some confidence and I truly feel my # is fair and accurate... I've felt that way for a while now.  I totally could be wrong of course... I'm not a know it all and time will tell I suppose.)

[BayAreaCoins]

No one is going anywhere - this is our network.

In case you forgot

https://www.youtube.com/watch?v=h4TTedpirFs

(teasing)

When this is all finished we can thank the digger for increasing the money supply and hence the coefficient for 'market cap'

I'm so happy to see you say this.

I agree 1000%.

[jpcfan]

I can add 0.001btc to that 300btc buy wall if you need me