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

[seedtrue]

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.

Maybe an exchange, or gambling site? It is still mostly fresh clams staking. They must have a very substantial amount(assuming it is one person, but my bet is it is).

[paulc010]

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.

That explains it then. The weight seems to be dropping again now, so I guess this batch is nearing its end (maybe 2/3rds don looking at the numbers).

I hope it's lots of new CLAM diggers and not just 1 but who knows...

[kbroadfoot]

Yeah, the network weight has dropped to 60052..

Look like your analysis is correct...

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

[dooglus]

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

[Zer0Sum]

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?

I'm also having problems for the first time (all installations 1.4.2b for last 2 weeks).

2 clients working normally on 2 machines...
A 3rd client on a 3rd machine pops up then "not responding" so just freezes...
(Nothing helps this one even total reinstallation).

And clients installed on 2 fresh PCs not connecting at all for many hours...
Even with those nodes (though you should post a full config file)...
Why would "debug" have "addnode" removed?

So netstakeweight spiked... and then drop from > 200,000 to 8,833?
If that is in fact what happened?


I'm also having issues for the f

[dooglus]

So netstakeweight spiked... and then drop from > 200,000 to 8,833?
If that is in fact what happened?

It looks like someone dug up a whole bunch of old clams from the initial distribution, and let them all stake.

Old clams stake relatively easily, because chance of staking is proportional to age times value.

One they all staked once, their age will have been reset to zero, and so the rush of staking abated (until the next person digs up a bunch).

Weight is just the sum of (age-in-days times value-in-clams) of all outputs currently trying to stake.

Each old distribution output is 4.6 CLAMs, and about 74 days old. That gives each one a weight of 340 CLAM-days until it successfully stakes.

If the network weight went up by 200k, that suggests that around 600 (200k / 340) old 4.6 CLAM outputs were found in a single dig!

Edit:

That matches pretty closely with the number of addresses that have been claimed. A couple of days ago the IRC bot reported:

05:08 < SuperClam>  Amount Claimed:  9151.04055538 Clams, 1987 Addresses

And now it reports:

19:39 < SuperClam>  Amount Claimed: 12103.13768472 Clams, 2628 Addresses

[undergroundgeek]

And now someone just sold 374.05139511 clams

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

[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