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

[Zer0Sum]

x11 and other algos needed on kHashier.
I could help forge the clam shell much better if I were able to mine DRK or other x11 coins.

x11 and other algos needed on kHashier.
I could help forge the clam shell much better if I were able to mine DRK or other x11 coins.

Yup...

If you guys are serious about mining; I can bump it up on the list of TODO's.
Take a look at it tonight.

Been trying to delegate and divide up time as efficiently as possible... given the lack of interest in the Multi-Pool, adding an additional algorithm to dilute hash was not a priority (though still planned).

Speculative GPU miners I think are a lot more common then speculative scrypt miners. 
And nscrypt profitability has dropped a lot lately, it's just not worth mining compared to X11 or X13.

I mined for a bit with nscrypt when it was worthwhile, but am waiting to point my rigs at khashier until we have some new algos.  And I think you'll see there are others in the same boat as me.

Also, as someone else said, people really like stats.  More stats would probably help the multi-pool more then anything.

Yes, miners love stats more than anything except one thing.

You get an idea of general MultiPool demographics by checking the BlackCoin Pool:

Scrypt......818
X11..........542
SHA256.....157
Scrypt-N...12

http://blackcoinpool.com/dashboard

The world is awash in cheap Scrypt ASICs...
And the CLAM MultiPool will get more and more important as CLAM cap grows...
So there have to be promotions for new people to go on Clam Hunts.

As for the current Stake rate annualized.. here's my numbers for last 6.6 days:

320 CLAM in 3 wallets... 38 x 0.10 stakes = 1 + (3.80/320) ^ (365/6.6) = 91% annualized

[whatsabitworth]

Sorry it has taken me so long to respond; it has been a busy week!


It seems there are quite a few people having sync issues.

The following build is a test build. 
It appears to functioning extremely well (including a few new features), but you should be aware it is currently being tested and is likely to have some flaws. 
If a user is using Windows, I would expect that the vast majority of issues might be solved by using this build:

CLAMClient Windows Test Build 1.4.2d

This worked for me. wallet synced and I'm back in Clams
thank you.

[phzi]

As for the current Stake rate annualized.. here's my numbers for last 6.6 days:

320 CLAM in 3 wallets... 38 x 0.10 stakes = 1 + (3.80/320) ^ (365/6.6) = 91% annualized

Uh, (3.80/320) ^ (365/6.6) = 0.  Not so sure about your math there.

[dooglus]

As for the current Stake rate annualized.. here's my numbers for last 6.6 days:

320 CLAM in 3 wallets... 38 x 0.10 stakes = 1 + (3.80/320) ^ (365/6.6) = 91% annualized

Uh, (3.80/320) ^ (365/6.6) = 0.  Not so sure about your math there.

The 1+ is meant to be inside the parentheses:

>>> (1 + 3.80/320) ** (365/6.6)
1.921017101683441

92%

[SuperClam]

x11 and other algos needed on kHashier.
I could help forge the clam shell much better if I were able to mine DRK or other x11 coins.

x11 and other algos needed on kHashier.
I could help forge the clam shell much better if I were able to mine DRK or other x11 coins.

Yup...

If you guys are serious about mining; I can bump it up on the list of TODO's.
Take a look at it tonight.
Been trying to delegate and divide up time as efficiently as possible... given the lack of interest in the Multi-Pool, adding an additional algorithm to dilute hash was not a priority (though still planned).

Speculative GPU miners I think are a lot more common then speculative scrypt miners. 
And nscrypt profitability has dropped a lot lately, it's just not worth mining compared to X11 or X13.
I mined for a bit with nscrypt when it was worthwhile, but am waiting to point my rigs at khashier until we have some new algos.  And I think you'll see there are others in the same boat as me.
Also, as someone else said, people really like stats.  More stats would probably help the multi-pool more then anything.

Yes, miners love stats more than anything except one thing.
You get an idea of general MultiPool demographics by checking the BlackCoin Pool:
Scrypt......818
X11..........542
SHA256.....157
Scrypt-N...12
http://blackcoinpool.com/dashboard
The world is awash in cheap Scrypt ASICs...
And the CLAM MultiPool will get more and more important as CLAM cap grows...
So there have to be promotions for new people to go on Clam Hunts.
As for the current Stake rate annualized.. here's my numbers for last 6.6 days:
320 CLAM in 3 wallets... 38 x 0.10 stakes = 1 + (3.80/320) ^ (365/6.6) = 91% annualized

Work has already begun to add x11 to the CLAMS Multi-pool

[phzi]

Work has already begun to add x11 to the CLAMS Multi-pool

WIN!  I want to mine me some X11 CLAMs!

[kbroadfoot]

Just curious:

Is that 1.5 BTC buy support @ 0.0015 the 'Clam Shell'?

[dooglus]

Just curious:

Is that 1.5 BTC buy support @ 0.0015 the 'Clam Shell'?

No.

[romerun]

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

[dooglus]

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.

[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?

[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?