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

[dooglus]

And now someone just sold 374.05139511 clams

The sell side has reduced by about that much, I'm thinking someone got tired of waiting.

I've been thinking for a while how much of a waste it is to have all those clams just sitting there when someone could have been staking them.

I expect the exchange is staking them.

In fact it wouldn't be hard to find out if you bought CLAMs from an exchange by tracing them back on the blockchain and see if they were staking before you withdrew them.

Edit: Well, OK, it looks to me very much like the exchange *isn't* staking them:



A 138 CLAM output with 22 days of age should stake very easily:

>>> 2**20 / (138.16 * 22)
345

ie. after about 345 seconds. It's inconceivable that it has been trying to stake for 22 days and not managed it.

On the one hand that does seem like a waste, but on the other hand that's better for the rest of us. Less competition, lower difficulty, more chance of winning lottery payouts.

[seedtrue]

And now someone just sold 374.05139511 clams

The sell side has reduced by about that much, I'm thinking someone got tired of waiting.

I've been thinking for a while how much of a waste it is to have all those clams just sitting there when someone could have been staking them.

I expect the exchange is staking them.

In fact it wouldn't be hard to find out if you bought CLAMs from an exchange by tracing them back on the blockchain and see if they were staking before you withdrew them.

Yeah, you are probably right. This could possibly cause an issue though if too many coins were frozen in stake and someone wanted to make a large withdraw...They may have to wait a while.

[dooglus]

And now someone just sold 374.05139511 clams

The sell side has reduced by about that much, I'm thinking someone got tired of waiting.

I've been thinking for a while how much of a waste it is to have all those clams just sitting there when someone could have been staking them.

I expect the exchange is staking them.

In fact it wouldn't be hard to find out if you bought CLAMs from an exchange by tracing them back on the blockchain and see if they were staking before you withdrew them.

Yeah, you are probably right. This could possibly cause an issue though if too many coins were frozen in stake and someone wanted to make a large withdraw...They may have to wait a while.

Yes, that could be an issue. But I find that for the most part no more than 50% of my CLAM outputs are immature at any point in time, and usually it's much less, and also the exchange could make it clear that in extreme circumstances coins won't be immediately available for withdrawal. It's comparable to trying to withdraw coins from cold storage - you expect to have to wait while cold stored coins are moved back online.

I guess security could be an issue. In order to stake, you need to have your coins online and effectively not protected by encryption. I know there's an "unlock for staking only" option, but that's not really any protection at all against a determined hacker.

[torrantz]

it seems my wallet refuses to sync after block 34001

Hard fork. Install the newer client.

i'm using the 1.4.2b client but it will not go further then 34001



edit: fixed by reloading the chain

Same issue again, wallet will not sync :s

It staked for a few day's and then it did'nt sync anymore

is it only me that's having this problem?

Is it stuck at block 34001 again?

If so, that's a hard-fork problem.

If not, try adding these lines to your clam.conf file and restarting:

addnode=24.20.184.148
addnode=65.102.47.162
addnode=66.169.88.135
addnode=75.131.208.152
addnode=78.0.29.137
addnode=81.190.41.203
addnode=85.17.81.169
addnode=142.4.201.123
addnode=207.61.182.125
addnode=216.46.33.120
addnode=220.253.2.201

Hi,thx or help

 its stuck @ 43848 now

i added the nodes but still no luck

tried clam.conf and Clam.conf.

i'm going to try reloading the blockchain all over again :s

[torrantz]

it seems my wallet refuses to sync after block 34001

Hard fork. Install the newer client.

i'm using the 1.4.2b client but it will not go further then 34001



edit: fixed by reloading the chain

Same issue again, wallet will not sync :s

It staked for a few day's and then it did'nt sync anymore

is it only me that's having this problem?

Is it stuck at block 34001 again?

If so, that's a hard-fork problem.

If not, try adding these lines to your clam.conf file and restarting:

addnode=24.20.184.148
addnode=65.102.47.162
addnode=66.169.88.135
addnode=75.131.208.152
addnode=78.0.29.137
addnode=81.190.41.203
addnode=85.17.81.169
addnode=142.4.201.123
addnode=207.61.182.125
addnode=216.46.33.120
addnode=220.253.2.201

Hi,thx or help

 its stuck @ 43848 now

i added the nodes but still no luck

tried clam.conf and Clam.conf.

i'm going to try reloading the blockchain all over again :s

and that fixed it again hmm

[seedtrue]

@superclam was there not a clampool payout yesterday? I did not receive one. Also, is the pool at least getting profits comparable to litecoin mining? It does not seem so. 3 days of 20-25 mh/s +- and I have recieved less than 3 clams. I could have mined litecoin --> sold the litecoin and bought 25-30 clams. This will definitely deter new users.

[undergroundgeek]

A bit of a unnerving sell off going on..

[paulc010]

Looks like someone dug up a bunch, staked them then sold them. Up to them I guess but someone got a nice bunch of CLAMS cheap!

[seedtrue]

Looks like someone dug up a bunch, staked them then sold them. Up to them I guess but someone got a nice bunch of CLAMS cheap!

Maybe they sold some, but a lot of those freshly dug clams are still sitting in their wallets.


About 500 of them got sent to this address  http://khashier.com:2750/address/xAdUhg71Jn82s48VaRjWpQ7yBhwugd2Ejw

[SuperClam]

Well, it still could use some testing; but appears to be in working order

Introducing, CLAMClient 1.4.2.1

Download Windows
Download Linux


So far, we have had it up and running on a variety of VM's.
Any additional testing, on various machines/configurations is greatly appreciated.

This build should fix the sync, and also the freeze/crash issues some users have been experiencing recently.

The links in the OP Post have been updated accordingly.

Cheers

[SuperClam]

@superclam was there not a clampool payout yesterday? I did not receive one. Also, is the pool at least getting profits comparable to litecoin mining? It does not seem so. 3 days of 20-25 mh/s +- and I have recieved less than 3 clams. I could have mined litecoin --> sold the litecoin and bought 25-30 clams. This will definitely deter new users.

Payouts at the CLAM multi-pool at made at intervals when there are enough funds to be withdraw from exchanges without incurring a withdrawal fee that is massive in proportion to the withdrawn funds.  Unfortunately, this means that are sometimes sporadic.

I get the need for instant gratification; it is hard to stick with something that doesn't seem to net you instant results.

That said, I urge you to come back to the thread here in a couple weeks.
This will give your 'contribution' to the pool time to be part of a set of payouts.

Figure your ROI then, as Pearl Payouts were intended, and I would bet that your numbers look a bit different

[maccd123]

I moved my LTC wallet to the Clam wallet and thhe wallet synced to 0.00 Clams. I have 4 Backups that for some reason are coming up wjth the same result. Help please! I had quite a few more in there in the beginning.

[paulc010]

I moved my LTC wallet to the Clam wallet and thhe wallet synced to 0.00 Clams. I have 4 Backups that for some reason are coming up wjth the same result. Help please! I had quite a few more in there in the beginning.

Did you backup the original wallet.dat in the CLAM data directory? If so then just put that back....

[sixteendigits]

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

God damn it.  I spent all that time splitting up my CLAMs for nothing.  I thought I was being clever but the CLAM devs were one step ahead of me.  Guess I'll go combine all my 0.1 CLAM piles together.

[Trololoh]

I moved my LTC wallet to the Clam wallet and thhe wallet synced to 0.00 Clams. I have 4 Backups that for some reason are coming up wjth the same result. Help please! I had quite a few more in there in the beginning.

-You can try to export your keys from LTC and import them into Clams, no need for switching wallets like that.
This is what I did to get my Clams from Electrum and Doge, worked like a charm.
-Alternative, when you have many accounts/keys export LTC wallet and import into Clam.

When done use rescan option to catch any missing transaction, but should not make a difference since importing keys or wallet do also rescan the chain.

[seedtrue]

Someone just dug up a ton of fresh clams

[SuperClam]

Someone just dug up a ton of fresh clams

Something to remember, when looking at network 'weight' as a measure: at this point, freshly dug CLAMS have a great deal of 'age' and thus weight.

[kbroadfoot]

Yeah, got sent to the 'back of the line' again  

[kbroadfoot]

Only 877 CLAM on Poloniex's sell side now... EVERYONE must be staking now....
I can only assume that is good? -ish?

Price seems rather stable... volume is down a bit...

[dooglus]

Yeah, got sent to the 'back of the line' again  

There's no "line", just a "difficulty".

Most of the time the difficulty is at its minimum, meaning that every 1 CLAM-day output has a 1-in-a-million chance of staking each second.

Currently the difficulty is 20 times higher than the minimum, meaning that each output is 20 times less likely to stake in any given time period.

So if you're used to staking 20 times per day, now you'll be getting about 1 block per day instead, and it will feel as if you are at the "back of the line".

I usually get 5 or 6 blocks per hour, but overnight I went 5 hours without staking a single block!