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

Quote from: almightyruler on July 26, 2014, 08:18:40 AM

Quote from: dooglus on July 29, 2014, 11:31:09 AM

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

torrantz

sr. member

Activity: 1063

Merit: 253

Sovryn - Brings DeFi to Bitcoin

Quote from: almightyruler on July 26, 2014, 08:18:40 AM

Quote from: seedtrue on July 29, 2014, 02:05:31 PM

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

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: dooglus on July 29, 2014, 02:00:14 PM

Quote from: seedtrue on July 29, 2014, 01:58:48 PM

Quote from: undergroundgeek on July 29, 2014, 01:49:45 PM

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.

seedtrue

legendary

Activity: 963

Merit: 1002

Quote from: dooglus on July 29, 2014, 02:00:14 PM

Quote from: seedtrue on July 29, 2014, 01:58:48 PM

Quote from: undergroundgeek on July 29, 2014, 01:49:45 PM

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

legendary

Activity: 2940

Merit: 1333

Quote from: seedtrue on July 29, 2014, 01:58:48 PM

Quote from: undergroundgeek on July 29, 2014, 01:49:45 PM

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

legendary

Activity: 963

Merit: 1002

Quote from: undergroundgeek on July 29, 2014, 01:49:45 PM

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.

undergroundgeek

newbie

Activity: 21

Merit: 0

And now someone just sold 374.05139511 clams

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: Zer0Sum on July 29, 2014, 01:21:00 PM

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:

Quote

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

And now it reports:

Quote

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

Zer0Sum

legendary

Activity: 1588

Merit: 1000

Quote from: almightyruler on July 26, 2014, 08:18:40 AM

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

legendary

Activity: 2940

Merit: 1333

Quote from: almightyruler on July 26, 2014, 08:18:40 AM

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

torrantz

sr. member

Activity: 1063

Merit: 253

Sovryn - Brings DeFi to Bitcoin

Quote from: almightyruler on July 26, 2014, 08:18:40 AM