Topic: [ANN][CLAM] CLAMs, Proof-Of-Chain, Proof-Of-Working-Stake, a.k.a. "Clamcoin" - page 436. (Read 1151252 times)

Updated difficulty charts:

The numbers look shocking but it's working fine. New staking chance isn't factored into the network weight (which was only ever an indicator) or the expected time to stake calculation.

My wallet is staking just fine even though the client is telling me I need to wait a year

This sound about right

(getinfo)
"version" : "v1.4.2.1-355-gf36c215",
"protocolversion" : 60014,
"walletversion" : 60000,
"balance" : 94.20881502,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 204771,
"timeoffset" : 0,
"moneysupply" : 15054374.76984581,
"connections" : 20,
"proxy" : "",
"ip" : "",
"difficulty" : {
"proof-of-work" : 0.00024876,
"proof-of-stake" : 4613.98166182
},
"testnet" : false,
"keypoololdest" : 1404539916,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00000000,
"errors" : ""

(getstakinginfo)
enabled" : true,
"staking" : true,
"errors" : "",
"currentblocksize" : 1000,
"currentblocktx" : 0,
"pooledtx" : 0,
"difficulty" : 4587.99675682,
"search-interval" : 16,
"weight" : 9420881502,
"netstakeweight" : 6627397658617,
"expectedtime" : 268435456


your weight 94
network weight 6,600,000,000,000
expected time to earn reward 3106 days

Here's a chart showing the network difficulty per block from shortly before the fork until now:



The net client made it around 100 million times easier to stake, since the previous code would let you stake if your output's hash was less than:


and the new code lets you stake if your output's hash is less than:


Your output's age is no longer taken into account. It used to be that your chance of staking increased the longer it had been since you last staked, but that no longer happens. Note that the output's value in satoshis is now used rather than its value in clams - that's where the factor of 100 million comes in. Given constant "difficulty", it is now 100 million times easier for a 1-day-old output to stake than it was before. However, it's only 50 million times easier for a 2-day-old output to stake, and only 1 million times easier for a 100-day-old output to stake. Most outputs used to stake within 50 days or so. I would guess the average time to stake used to be around 10 days. So we might expect the network difficulty to adjust by a factor of 10 million to compensate.

The difficulty adjustment code smoothly ramped the difficulty up by a factor of around 1 million, but it overshot, and it's taking a while to reach a new equilibrium. Here's a close-up of the last few hundred block difficulties:



Why did the network difficulty "only" adjust by a factor of 1 million? Perhaps because a significant percentage of the network didn't switch to the net client yet. Or perhaps because my math is wrong.

Edit:

To get the data, I ran:


(where 'cc' is an alias for 'clamd') and to plot the charts:

downloading the new client right now...
my chain is "again" on the wrong fork up to 2039xx
hopefully I can manage to resynch better than last time

2 times stuck @99% and the third time it saves to my hd but I got this error on chrome

http://webchat.freenode.net/?channels=clams

I've also noticed I seem to be staking a lot. Is there a simple way to get onto your IRC channel via a web client? I haven't used IRC for 10 years.

Difficulty currently 5000?  

Bit of the old signed integer overflow here...

{
    "enabled" : true,
    "staking" : true,
    "errors" : "",
    "currentblocksize" : 1000,
    "currentblocktx" : 0,
    "pooledtx" : 0,
    "difficulty" : 4911.38914873,
    "search-interval" : 16,
    "weight" : 23285562167,
    "netstakeweight" : 5109529310971,
    "expectedtime" : -226293232
}

We went for a bit of a ride after the fork, all of the estimates are entirely off, though things are balancing out now.
If you want to check that you are on the right chain, or get things straightened out stop into IRC, friend.

The last two stakes orphaned and my client has lost all connections/ gone offline.

51'd ?

Indeed, difficulty is racing upwards to catch it - we are investigating.

Stop into #clams on freenode, we are exchanging blockhashes and monitoring the chain.

Well all I'm getting right now is a ton of "generated but not accepted" (for an hour and a half now). khashier seems to be on the old chain so no idea how to make sure mine is syncing to the correct one?

BTW the client says the network weight is over 93 million?

EDIT: Now 763 million...

Join the effort in CoinSwap's IRC room to vote CLAMs onto the exchange.

Go to http://webchat.freenode.net/?channels=coin-swap and enter "!vote CLAM" once per hour.

As of now CLAMs has over 200 votes and is near #3 on the list.

Thanks to user istvandv for pointing this out

Indeed.
The intent was to just include a very simple fix that will prevent people from having their manually split outputs re-combined on them.

Linux Binary:
CLAMclient 1.4.3.0 Linux

I don't think that's quite right.

It looks to me like the new code will combine outputs which are less than 1 CLAM into outputs of size 1 CLAM, but it will split anything that took less than 24 hours to stake (but only when it does eventually stake).

But maybe that's what you meant.

Awesome - bit rough around the edges, but it was a push to have it included in this update at all.
Those types of issues can easily be fixed without fork or hassle in the near future

Love the new look

Windows Client executable posted.
CLAMclient 1.4.3.0 Windows

I want to try and clarify this by saying the attacks after the fork at block ~170 000 benefitted the whole network rather than just a single entity. To put it simply, the network difficulty was being pushed down. So if you were staking, you did get an informal bonus.

This fork also puts a few new mechanisms into play that will allow some planned future updates to be soft-forked in and certainly be more seamless than things are now for the average user. As painful as two hard-forks this close together have been for all of us, it is my intention for users to not have to stare at this announcement forum all day long, or pay attention at all to anything but the client to be notified of an update. I only say this because there seems be clients still stuck on forks around block 165k-170k, and that concerns me. We want to include everyone here, even if someone can only devote a few minutes of focus on our coin. People are busy, after all. But we're here to stay and want to see our community flourish.

Cheers,
tryphe

Great catch, I will add it to the 'shortlist' above. 
Expect compiled binaries shortly.