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

[almightyruler]

Damn it.  I just spent the last hour importing all my private keys from blockchain.info and moving all my BTC and any assets I hold tied to a BTC address (maidsafe, XCP, AGS) to new addresses cuz I'll be damned if the clams client is getting any private keys that are worth anything to me.  I'm all set to claim my clams and.......client won't sync.  0 nodes.  Yes, I am using the latest build.  Can someone gives me some nodes?

Try these:

Code:

# coin: clam
addnode=24.67.30.88
addnode=198.245.60.38
addnode=65.102.47.162
addnode=24.184.168.36
addnode=93.103.131.59
addnode=85.17.81.164
addnode=142.4.201.123
addnode=84.194.247.232
addnode=220.253.2.201
addnode=188.116.147.85
addnode=85.17.81.169
addnode=109.223.234.123
addnode=173.68.204.192
addnode=198.245.60.38
addnode=107.192.136.116
addnode=24.238.75.8
addnode=184.9.244.44
addnode=79.206.224.49
addnode=207.61.182.125
addnode=216.46.33.120
addnode=99.233.92.9
addnode=85.191.52.188
addnode=67.201.165.63
addnode=82.26.243.220

Superclam, I see the source code has 4 different seed nodes, are they down or just "full"?

connect to address 54.186.94.88: Operation timed out
connect to address 54.186.202.251: Operation timed out
connect to address 54.186.249.57: Operation timed out
connect to address 54.187.138.13: Operation timed out

[dooglus]

Can someone gives me some nodes?

Here:

24.238.75.8:31174
65.102.47.162:31174
75.131.208.152:31174
76.173.48.220:31174
84.194.247.232:31174
85.191.52.188:31174
93.103.131.59:31174
107.192.136.116:31174
142.4.201.123:31174
173.68.204.192:31174
184.9.244.44:31174
188.116.147.85:31174
203.20.114.252:31174
216.46.33.120:31174
220.253.2.201:31174

[sixteendigits]

Damn it.  I just spent the last hour importing all my private keys from blockchain.info and moving all my BTC and any assets I hold tied to a BTC address (maidsafe, XCP, AGS) to new addresses cuz I'll be damned if the clams client is getting any private keys that are worth anything to me.  I'm all set to claim my clams and.......client won't sync.  0 nodes.  Yes, I am using the latest build.  Can someone gives me some nodes?

Try these:

Code:

# coin: clam
addnode=24.67.30.88
addnode=198.245.60.38
addnode=65.102.47.162
addnode=24.184.168.36
addnode=93.103.131.59
addnode=85.17.81.164
addnode=142.4.201.123
addnode=84.194.247.232
addnode=220.253.2.201
addnode=188.116.147.85
addnode=85.17.81.169
addnode=109.223.234.123
addnode=173.68.204.192
addnode=198.245.60.38
addnode=107.192.136.116
addnode=24.238.75.8
addnode=184.9.244.44
addnode=79.206.224.49
addnode=207.61.182.125
addnode=216.46.33.120
addnode=99.233.92.9
addnode=85.191.52.188
addnode=67.201.165.63
addnode=82.26.243.220

Superclam, I see the source code has 4 different seed nodes, are they down or just "full"?

connect to address 54.186.94.88: Operation timed out
connect to address 54.186.202.251: Operation timed out
connect to address 54.186.249.57: Operation timed out
connect to address 54.187.138.13: Operation timed out

Thanks, that worked.  Kinda sucks after all that work I only ended up with 4.6 CLAM but oh well.  I guess there are far more BTC addresses than DOGE and LTC combined so odds any particular BTC address contains CLAM is probably much smaller than with DOGE or LTC.

[dooglus]

Kinda sucks after all that work I only ended up with 4.6 CLAM but oh well.  I guess there are far more BTC addresses than DOGE and LTC combined so odds any particular BTC address contains CLAM is probably much smaller than with DOGE or LTC.

That's not how it works.

*Every* BTC address that had a non-dust balance on the date in question got 4.6 CLAM awarded to it.

[sixteendigits]

Kinda sucks after all that work I only ended up with 4.6 CLAM but oh well.  I guess there are far more BTC addresses than DOGE and LTC combined so odds any particular BTC address contains CLAM is probably much smaller than with DOGE or LTC.

That's not how it works.

*Every* BTC address that had a non-dust balance on the date in question got 4.6 CLAM awarded to it.

Yeah, I just started seeing more CLAM pop up.  I guess I assumed I'd see them all at once.  I'm up to 27.6 CLAM right now.

[dooglus]

Kinda sucks after all that work I only ended up with 4.6 CLAM but oh well.  I guess there are far more BTC addresses than DOGE and LTC combined so odds any particular BTC address contains CLAM is probably much smaller than with DOGE or LTC.

That's not how it works.

*Every* BTC address that had a non-dust balance on the date in question got 4.6 CLAM awarded to it.

Yeah, I just started seeing more CLAM pop up.  I guess I assumed I'd see them all at once.  I'm up to 27.6 CLAM right now.

They should all be in your wallet as soon as it finishes rescanning the blockchain. That takes a few minutes typically.

Oh, but maybe you didn't download the blockchain yet - if you're downloading it, you'll see them appear as it downloads. It looks like the 4.6 CLAM awards happened from block 558 to block 9262.

[sixteendigits]

Kinda sucks after all that work I only ended up with 4.6 CLAM but oh well.  I guess there are far more BTC addresses than DOGE and LTC combined so odds any particular BTC address contains CLAM is probably much smaller than with DOGE or LTC.

That's not how it works.

*Every* BTC address that had a non-dust balance on the date in question got 4.6 CLAM awarded to it.

Yeah, I just started seeing more CLAM pop up.  I guess I assumed I'd see them all at once.  I'm up to 27.6 CLAM right now.

They should all be in your wallet as soon as it finishes rescanning the blockchain. That takes a few minutes typically.

Oh, but maybe you didn't download the blockchain yet - if you're downloading it, you'll see them appear as it downloads. It looks like the 4.6 CLAM awards happened from block 558 to block 9262.

Yeah, as soon as I saw the nodes worked, I closed the client and replaced the wallet.dat, they slowly started popping up as I downloaded the blockchain.  And already got 0.1 CLAM more for staking!

[dooglus]

Yeah, as soon as I saw the nodes worked, I closed the client and replaced the wallet.dat, they slowly started popping up as I downloaded the blockchain.  And already got 0.1 CLAM more for staking!

The network difficulty is generally at or around the minimum.

That means that each of your 4.6 CLAM outputs has a 2^20 / (4.6 * age_in_days) chance of staking each second.

The distribution was around 72 days ago, and so:

>>> 2**20 / (72 * 4.6)
3166

each 4.6 CLAM output will typically take about an hour on average to stake.

When it stakes, its age is destroyed, so you won't expect to see it stake again for a while.

And the 0.1 you saw is pseudo-random, and can be as much as 1000 CLAMs if you're really lucky.

99% of the time it's 0.1 though.

[dooglus]

I notice that some addresses received multiple 4.6 CLAM deposits in the initial distribution.

See http://khashier.com:2750/address/xV4sJ8TkjZbkfAP4knLfRVgGVeNQTQQxPJ for example.

Was that a mistake, or what's going on with that?

[romerun]

can I just claim my Clam, is it too late ? how to

Any BTC, LTC, or DOGE private key which had some non-dust amount of coin on it some time in early May this year will have 4.6 or so CLAM on it too.

Simply export the private key from your BTC (or LTC, or DOGE) client and import it into the CLAM client.

Alternately, you can just copy your wallet.dat from the BTC data folder into the CLAM data folder, then run "clam-qt -rescan" to have it check all the private keys in that wallet.

A natural concern is that the CLAM wallet software will steal the BTC from the private keys you give it. I have given it private keys with hundreds of BTC on, and it hasn't stolen any of them.

If you're concerned, you can make sure the private keys you give it have already been emptied out of BTC - then you don't have to trust the CLAM software.

Sweet ! So those centralized services generating numerous addresses can have boat load of clams.

[dooglus]

Sweet ! So those centralized services generating numerous addresses can have boat load of clams.

Only the lazy ones that don't sweep customer deposits into cold storage.

[paulc010]

Anyone else noticed a higher number of "Generated but not accepted" recently? Over the last 2 days I've had 20%.... 2 out of the last 10.

Maybe the number of coins I'm staking is too low (5-8 per "pile")?

Am using build v1.4.2.0-47-g7fecba1.

[phzi]

Anyone else noticed a higher number of "Generated but not accepted" recently? Over the last 2 days I've had 20%.... 2 out of the last 10.

Maybe the number of coins I'm staking is too low (5-8 per "pile")?

Am using build v1.4.2.0-47-g7fecba1.

Try to increase your peer count.  5 per pile seems to be a great amount per stack, and that shouldn't have any affect on orphans anyway.

I have never had an orphan block since I have been staking CLAMs.

[sixteendigits]

Yeah, as soon as I saw the nodes worked, I closed the client and replaced the wallet.dat, they slowly started popping up as I downloaded the blockchain.  And already got 0.1 CLAM more for staking!

The network difficulty is generally at or around the minimum.

That means that each of your 4.6 CLAM outputs has a 2^20 / (4.6 * age_in_days) chance of staking each second.

The distribution was around 72 days ago, and so:

>>> 2**20 / (72 * 4.6)
3166

each 4.6 CLAM output will typically take about an hour on average to stake.

When it stakes, its age is destroyed, so you won't expect to see it stake again for a while.

And the 0.1 you saw is pseudo-random, and can be as much as 1000 CLAMs if you're really lucky.

99% of the time it's 0.1 though.

Ok, so forgive me if this has been addressed already, but I'm just curious if I understand this correctly.  If I have 50 clams, odds are I am going to hit the same number of PoS blocks in a year no matter if those clams are in one pile or spread out in little piles over 100 different addresses.  EXCEPT for that long confirmation time of 510 blocks.  If we view PoS in clams as a lottery, the guy that has all his clams in one pile effectively doesn't have a ticket for 510 blocks.  So the guy with lots of little piles will end up hitting more blocks, as he is always going to have a ticket.  So it is advantageous to spread your clams out as much as possible.  Do I got this right?

[paulc010]

Wow my client is currently reporting the network weight as 178,365. Never seen it that high before....

Output from getstakinginfo:

{
"enabled" : true,
"staking" : true,
"errors" : "",
"currentblocksize" : 1000,
"currentblocktx" : 0,
"pooledtx" : 0,
"difficulty" : 0.00438567,
"search-interval" : 1,
"weight" : 28,
"netstakeweight" : 178365,
"expectedtime" : 31850
}


My tiny piles make take a while to stake now.....

[kbroadfoot]

Definitely looks like more and more people are discovering clams... network weight WAY up:



201700   ( wow )

[seedtrue]

Definitely looks like more and more people are discovering clams... network weight WAY up:



201700   ( wow )

I think someone dug up a WHOLE LOT of old clams. If you look at the block explorer, almost all of the new stakes are on stacks of 4.60545574.

[dooglus]

Anyone else noticed a higher number of "Generated but not accepted" recently? Over the last 2 days I've had 20%.... 2 out of the last 10.

Maybe the number of coins I'm staking is too low (5-8 per "pile")?

Am using build v1.4.2.0-47-g7fecba1.

No, I've noticed quite the opposite.

I used to get one or two per day, and recently I've seen none for 4 days.

I think it's just a question of luck. If you and I both try to stake a block at the same time, only one of us can succeed. Whichever of us has the better connection to the network "wins".

Note that it doesn't really matter - if an output stakes but that block isn't accepted, the output keeps its previous weight and so gets to stake again relatively quickly.

[dooglus]

That means that each of your 4.6 CLAM outputs has a 2^20 / (4.6 * age_in_days) chance of staking each second.

If I have 50 clams, odds are I am going to hit the same number of PoS blocks in a year no matter if those clams are in one pile or spread out in little piles over 100 different addresses.  EXCEPT for that long confirmation time of 510 blocks.

Do I got this right?

If what I said was true, your conclusion is also true.

However...

I missed out a small detail, and your real chance of staking (per second) is 1 in:

2^20 / int(value_in_CLAMs * age_in_days)

ie. the weight of your output is rounded down to an integer number of CLAM-days.

That means that if you split your outputs up into 0.01 CLAM units, they have (effectively) zero chance of staking until they are 100 days old.  (I say "effectively" because if your output rolls a zero in the sha256 hash, it stakes. But that (effectively) never happens).

Note also that the 2^20 is for minimum difficulty. At the moment we're at around 10 times minimum difficulty, so you need to decrease your chance by a factor of 10 until the recently dug CLAM mother lode finishes its initial round of staking.

I've not seen an analysis of the best stake size given these two constraints.

Oh, and there's a 3rd constraint: no output is allowed to stake within 4 hours of its previous movement (staking or transacting).

[dooglus]

I think someone dug up a WHOLE LOT of old clams. If you look at the block explorer, almost all of the new stakes are on stacks of 4.60545574.

216 of the most recent 232 blocks (all but 16) were freshly dug 4.60545574 CLAM outputs.

Only 1 of the 38 blocks before that were freshly dug.