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

[istvandv]

One more question, how long does it take coins to mature?

staked clams mature after 510 confirmations

[dooglus]

One more question, how long does it take coins to mature?

staked clams mature after 510 confirmations

It's weird. Your client accepts spends after 500 confirmations from everyone except yourself, but won't let you spend until 510 confirmations.

If you use 'sendrawtransaction' you can spend after 500 too.

Here's me 'spending' my recent lottery win just 503 blocks after winning it:



(click to enlarge)

[melds39]

Looks like such a fun coin... too bad the way it got distributed kind of suck for us poor 

[madmartyk]

My 27 Clams are now staking!!  But it tells me my network weight is 1 and I can expect reward in 143 days!  :O  Is that right?

[dooglus]

Looks like such a fun coin... too bad the way it got distributed kind of suck for us poor 

It was given out for free equally to everyone who held any non-dust amount of BTC, LTC, or DOGE. How could it possibly have been more fair?

My 27 Clams are now staking!!  But it tells me my network weight is 1 and I can expect reward in 143 days!  :O  Is that right?

The weight is the sum of (age_in_days times value_in_clams) of all your outputs.

After 24 hours your weight should be 27 (1 day times 27 CLAMs), and the estimate of staking time should be 27 times smaller. After 2 days it will halve again as your weight will have doubled, etc.

At least I think that's how it works.

[SuperClam]

Looks like such a fun coin... too bad the way it got distributed kind of suck for us poor  

The actual situation is EXACTLY the opposite.

When CLAMS were distributed, the size of a user's balance was not taken into account.
(Only requirement being the balance was above dust.)


So, the Shibe with a pile of tips in an address, and the Bitcoin old timer with hundreds of BTC in an address:

Were given exactly the same amount of CLAMS for that address.

[istvandv]

One more question, how long does it take coins to mature?

staked clams mature after 510 confirmations

It's weird. Your client accepts spends after 500 confirmations from everyone except yourself, but won't let you spend until 510 confirmations.

If you use 'sendrawtransaction' you can spend after 500 too.

Here's me 'spending' my recent lottery win just 503 blocks after winning it:
*snip*

interesting, never really tried to spend clams before the 510 confirmations, i just went by what was displayed in QT after a successful stake

oh, just got a clampool payout  

[istvandv]

Looks like such a fun coin... too bad the way it got distributed kind of suck for us poor 

just curious, why do you think the distribution was bad? what gave you this impression?

[SuperClam]

Looks like such a fun coin... too bad the way it got distributed kind of suck for us poor 

just curious, why do you think the distribution was bad? what gave you this impression?

Indeed: understanding where this impression came from could help us to improve our message.
It is our fair and wide distribution that sets us apart from the rest of the crypto-world.

[FanEagle]

I tried to import my wallet vut it gives me an error! Code 2 i guess

[Thirdspace]

imported 4 address earlier... in about 2 hours, 2 of them got staked
going to import a few more later, but I have a few questions before that:
 ? how do I delete used address from my qt-client (at least how to hide them)?
both of my staked clams have 1 output, I've seen on the explorer that some addresses staked to 2 outputs
also about auto-joining staked into 1 single pile of 1000,
 ? so under what circumstances do the staked divided into 2 outputs? or joined into 1 output of 1000 CLAMs
I know there was a discussion about this, I don't quite understand it last time and I couldn't seem to find that post again

[dooglus]

how do I delete used address from my qt-client (at least how to hide them)?

I don't think you can, very easily. You can label them "do not use" or something, so you won't accidentally give them out to anyone.

Alternatively, you might find a tool called 'pywallet' can do it. Make a backup of your wallet.dat first, in case you mess it up.

both of my staked clams have 1 output, I've seen on the explorer that some addresses staked to 2 outputs
also about auto-joining staked into 1 single pile of 1000,

If an output stakes twice within 28 hours, it will be split into two roughly equal sized pieces of roughly half the size each.

When an output stakes, other outputs at the same address are combined with it to produce a single larger output (up to the value of 1000 CLAMs).

Each time an output stakes it gains between 0.1 and 1000 CLAMs in value. It's almost always 0.1, but if you're lucky it can be much more.

[SuperClam]

how do I delete used address from my qt-client (at least how to hide them)?

I don't think you can, very easily. You can label them "do not use" or something, so you won't accidentally give them out to anyone.
Alternatively, you might find a tool called 'pywallet' can do it. Make a backup of your wallet.dat first, in case you mess it up.

both of my staked clams have 1 output, I've seen on the explorer that some addresses staked to 2 outputs
also about auto-joining staked into 1 single pile of 1000,

If an output stakes twice within 28 hours, it will be split into two roughly equal sized pieces of roughly half the size each.
When an output stakes, other outputs at the same address are combined with it to produce a single larger output (up to the value of 1000 CLAMs).
Each time an output stakes it gains between 0.1 and 1000 CLAMs in value. It's almost always 0.1, but if you're lucky it can be much more.

I will put fixing the split/combine mechanism into the list of prioritized issues.
It is a client-side non-forking patch; and as such, there is no reason not to just get it done and release a hotfix compile.

It is something that has needed some work for some time; some of which dooglus and others have already completed (thank you).


We have been putting much of our effort into larger features and applications and I think it is time to just hammer this one out.

[madmartyk]

Got some spare CLAMS sitting around doing nothing?  Since I'm an active CLAMS holder (and supporter), please check out www.cryptoforkids.com

For the past decade WLRA Radio/Lewis University (Romeoville, IL) holds a bi-annual fundraiser to benefit Advocate Hope Children's Charities. So far Lewis U has raised over $100,000 for the charity. Twice a year WLRA has a "To kill a DJ" week where students raise money for the charity.
We are Big Burrito Radio (heard on WLRA Saturday mornings at 10AM CST), wanted to come up with different ways of raising money for the charity. We started out doing collections at music events. Then 4 years ago we came up with Island Dreams (www.islanddreamscards.com). Island Dreams is a charity art card set that itself has raised over $10,000 in the past 3 years.
Last year I caught the crypto-currency bug. I thought what a great idea to take crypto and exchange it for BTC for the Children's Hospital! So here we have Crypto for kids!

[almightyruler]

Bit of a strange one here. I downloaded the win client from mega, and to speed up things forced it to connect to my fully synced local node with listen=0 connect=x.x.x.x

Note the block estimate versus (single) peer height. Not sure why the estimate is about half what it should be. Once it got to 0 the progress bar disappeared, but the "(out of sync)" message was still there (presumably because the last block was far too old)

I had to allow it to connect to other peers in order to continue past block 48000.

[dooglus]

Bit of a strange one here. I downloaded the win client from mega, and to speed up things forced it to connect to my fully synced local node with listen=0 connect=x.x.x.x

Note the block estimate versus (single) peer height. Not sure why the estimate is about half what it should be. Once it got to 0 the progress bar disappeared, but the "(out of sync)" message was still there (presumably because the last block was far too old)

I had to allow it to connect to other peers in order to continue past block 48000.

I don't know why that happened, but I would suggest shutting down your local instance and just copying the whole folder that contains your wallet (except for the wallet.dat itself) onto the remote machine. Then it won't need to sync at all.

[almightyruler]

Another odd thing.

*nix v1.4.2.0-g32a928e:

   "difficulty" : 0.00458931,
    "weight" : 6842,
    "netstakeweight" : 256807,
    "expectedtime" : 187


Windows 1.4.2.1, same wallet, started a few mins later:

   "difficulty" : 0.00486416,
    "weight" : 6846,
    "netstakeweight" : 267481,
    "expectedtime" : 3195


Has the estimate code been changed, or is there some other issue?

edit: just saw on github,

dooglus on Jul 26
Fix "expectedtime" estimate returned by RPC call "getstakinginfo".

[dooglus]

Has the estimate code been changed [...]?

Yes, it was quite wrong and so I fixed it:

https://github.com/nochowderforyou/clams/issues/42

I don't know what version my change went into, but I'm guessing it was between the two version you're using.

[SuperClam]

Bit of a strange one here. I downloaded the win client from mega, and to speed up things forced it to connect to my fully synced local node with listen=0 connect=x.x.x.x
Note the block estimate versus (single) peer height. Not sure why the estimate is about half what it should be. Once it got to 0 the progress bar disappeared, but the "(out of sync)" message was still there (presumably because the last block was far too old)
I had to allow it to connect to other peers in order to continue past block 48000.

48k is an odd block to get stuck on.... if it was 34k the reason would of coarse be obvious...

[almightyruler]

Has the estimate code been changed [...]?

Yes, it was quite wrong and so I fixed it:

I'll say. In the above case it was about 17 times more optimistic! I'm not even close to minting.