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

[rocoro]

They will stake separately, but may be recombined when you stake, depending on your config.

So, how do you set the config so they won't recombine?

Thanks.

[doothewop]

What do you mean dumped? He has not dumped 1/3 of his stash and CLAM price is already almost 10% of what it was 2 months ago. Ok, since all of you think my suggestions are inadequate and this digging and dumping is actually a good thing for CLAM, fine, so be it. Let us see how low it can go. I will not mention this issue anymore cause the community obviously thinks differently. Happy dumping to the digger.

You're obviously very passionate about this.  Are you passionate enough about it to use the new voting system, or you'd rather just complain on forums?

[crazyivan]

What do you mean dumped? He has not dumped 1/3 of his stash and CLAM price is already almost 10% of what it was 2 months ago. Ok, since all of you think my suggestions are inadequate and this digging and dumping is actually a good thing for CLAM, fine, so be it. Let us see how low it can go. I will not mention this issue anymore cause the community obviously thinks differently. Happy dumping to the digger.

You're obviously very passionate about this.  Are you passionate enough about it to use the new voting system, or you'd rather just complain on forums?

Why would I start a voting campaign over something only I think should be done? Besides one or two guys here, most of the community thinks digging and dumping is the best way to move forward. Ok, I respect this, majority rules.

[Trent Russell]

curious, has anyone approached you about negotiating a lump buyout of your remaining Clams? I'd guess you have about 200,000 based on that sell order that was at .0045 on Poloniex. Perhaps a coalition of JD investors/gamblers would be interested in getting a lot at a fixed price.

curious did post this earlier, so he does seem interested in selling privately:

By the way, if anyone wants to buy clams OTC, let me know.

[Trent Russell]

The CLAMour voting system looks interesting. Good work!

About the current/future whale diggers, one possibility I haven't heard mentioned would be very simple and would dilute the initial distribution: increase the reward. There's at least a precedent for changing the reward system in Clams.

Maybe I'll make a CLAMour petition to increase the reward from 1 clam per block to, oh, say, 100 clams per block. This would increase the supply by about a million clams a week. Before long the initial distribution would be a relatively small percent of the total supply.

This would likely be terrible for the price. It might push us below 0.001. (<- That's intended as dark humour. I have looked at the price today.)

[djhomeschool]

btw i bought coffee from this guy http://cryptomercado.com/collections/all w/ clams (via email ultimately) and he claims it is in the mail

so, it's not just 'jd' anymore

You should have gotten an email with the USPS tracking number.

[rocoro]

They will stake separately, but may be recombined when you stake, depending on your config.

So, how do you set the config so they won't recombine?

Thanks.

^bump  ..  does anyone else happen to know?

[SuperClam]

They will stake separately, but may be recombined when you stake, depending on your config.

So, how do you set the config so they won't recombine?
Thanks.

^bump  ..  does anyone else happen to know?

Don't have a client available at the moment, but it should be listed with the other execution flags.

-nostakesplit, possibly?

EDIT:
Can set -combinelimit, re: https://github.com/nochowderforyou/clams/commit/92b99052b055802ae80dcc996155f85f417d5618
Can set -splitsize, re: https://github.com/nochowderforyou/clams/commit/3f15194aa8ca2ad22e538554813a3967ca8596fe

[rocoro]

They will stake separately, but may be recombined when you stake, depending on your config.

So, how do you set the config so they won't recombine?
Thanks.

^bump  ..  does anyone else happen to know?

Don't have a client available at the moment, but it should be listed with the other execution flags.

-nostakesplit, possibly?

EDIT:
Can set -combinelimit, re: https://github.com/nochowderforyou/clams/commit/92b99052b055802ae80dcc996155f85f417d5618
Can set -splitsize, re: https://github.com/nochowderforyou/clams/commit/3f15194aa8ca2ad22e538554813a3967ca8596fe

Thanks!
so for example..  
If I have output amounts as piles of 5..  and I set ./clamd -combinelimit=5    (set to 5 or less?)
Then it won't combine into larger piles right?

 

[Kefkius]

Our CLAM - The CLAMour Specification

Looking great. Thanks for all the work put into this. Not sure about the 10,000 block time frame though, it doesn't seem like enough time for a real vote to occur. Is the Clamour name a take on the word clamor?

Yeah, "clamour" is the British English equivalent of "clamor." For the sake of brevity, it started as "clamor," but "clamour" has the words "our" and "clam" in it.

About the 10,000 block frame: That's a moving frame. There is no deadline for votes; instead, whenever >50% of blocks staked in any 10,000 block window express support of a petition, that's considered a majority. So in effect, the vote can occur any time.

[gamblingbad]

So when will there be a vote on stop digging?

[gaba]

So when will there be a vote on stop digging?

It's too late now.

[DrkLvr_]

Our CLAM - The CLAMour Specification

Looking great. Thanks for all the work put into this. Not sure about the 10,000 block time frame though, it doesn't seem like enough time for a real vote to occur. Is the Clamour name a take on the word clamor?

Yeah, "clamour" is the British English equivalent of "clamor." For the sake of brevity, it started as "clamor," but "clamour" has the words "our" and "clam" in it.

About the 10,000 block frame: That's a moving frame. There is no deadline for votes; instead, whenever >50% of blocks staked in any 10,000 block window express support of a petition, that's considered a majority. So in effect, the vote can occur any time.

I still don't really understand what's supposed to happen in the event of a successful vote. Can you expand on that? So far I gather that nothing really happens, it's just a metric you can use to assess whether x% of people are likely to run a new fork with your proposed changes. It'd be up to the petition-maker to implement any changes they'd like to see, and convince people to run the new version.

Is that about the gist of it?

[gamblingbad]

So when will there be a vote on stop digging?

It's too late now.

Its not, is for the future whale diggers. And holders dont need fear huge diggers anymore.

[gamblingbad]

curious, has anyone approached you about negotiating a lump buyout of your remaining Clams? I'd guess you have about 200,000 based on that sell order that was at .0045 on Poloniex. Perhaps a coalition of JD investors/gamblers would be interested in getting a lot at a fixed price.

Yes, I'm open to it. So far only 2 people have PMd me with OTC offers and I have made deals with both of them.

can u tell around how much u got left so can see how much btc need to buy all?

[Kefkius]

Our CLAM - The CLAMour Specification

Looking great. Thanks for all the work put into this. Not sure about the 10,000 block time frame though, it doesn't seem like enough time for a real vote to occur. Is the Clamour name a take on the word clamor?

Yeah, "clamour" is the British English equivalent of "clamor." For the sake of brevity, it started as "clamor," but "clamour" has the words "our" and "clam" in it.

About the 10,000 block frame: That's a moving frame. There is no deadline for votes; instead, whenever >50% of blocks staked in any 10,000 block window express support of a petition, that's considered a majority. So in effect, the vote can occur any time.

I still don't really understand what's supposed to happen in the event of a successful vote. Can you expand on that? So far I gather that nothing really happens, it's just a metric you can use to assess whether x% of people are likely to run a new fork with your proposed changes. It'd be up to the petition-maker to implement any changes they'd like to see, and convince people to run the new version.

Is that about the gist of it?

Yes, that's about the gist of it. It provides evidence that the network is willing to accept a change to the CLAM protocol. The changes have to manually be made, but it is no longer up to the developers to prove that CLAM users want a change. In short, it protects users from tyranny and developers from blame.

[TooDumbForBitcoin]

Our CLAM - The CLAMour Specification

This looks like a lot of work in a short time by the CLAM devs.

I suggest a proposal created by CLAMour be called .... a CLAMidea

That way a person can say, "I have a CLAMidea".

WARNING:  Don't say, "I have CLAMidea".

[xploited]

Yeah, "clamour" is the British English equivalent of "clamor." For the sake of brevity, it started as "clamor," but "clamour" has the words "our" and "clam" in it.

About the 10,000 block frame: That's a moving frame. There is no deadline for votes; instead, whenever >50% of blocks staked in any 10,000 block window express support of a petition, that's considered a majority. So in effect, the vote can occur any time.

I'd just like to take a moment and thank Kefkius who's development with CLAM has been invaluable. We haven't said so yet officially, but we consider him part of the team

I still don't really understand what's supposed to happen in the event of a successful vote. Can you expand on that? So far I gather that nothing really happens, it's just a metric you can use to assess whether x% of people are likely to run a new fork with your proposed changes. It'd be up to the petition-maker to implement any changes they'd like to see, and convince people to run the new version.

Is that about the gist of it?

Your first part is correct,  it is a metric that can be used to assess the current "will" of the network. Its up to the petition-maker to gain support for their idea.. but not necessarily required for them to have code. By having the vote you will already know if people are willing to run the new version or not..  no convincing should really be required assuming the vote reaches majority.

I personally suggest a formal place to create a detailed plan of implementation once a vote has been won,  think CIP's (clam improvement protocol) which could be hosted on the nochowerderforyou git repo.
 

[TooDumbForBitcoin]

Yeah, "clamour" is the British English equivalent of "clamor." For the sake of brevity, it started as "clamor," but "clamour" has the words "our" and "clam" in it.

About the 10,000 block frame: That's a moving frame. There is no deadline for votes; instead, whenever >50% of blocks staked in any 10,000 block window express support of a petition, that's considered a majority. So in effect, the vote can occur any time.

I'd just like to take a moment and thank Kefkius who's development with CLAM has been invaluable. We haven't said so yet officially, but we consider him part of the team

I still don't really understand what's supposed to happen in the event of a successful vote. Can you expand on that? So far I gather that nothing really happens, it's just a metric you can use to assess whether x% of people are likely to run a new fork with your proposed changes. It'd be up to the petition-maker to implement any changes they'd like to see, and convince people to run the new version.

Is that about the gist of it?

Your first part is correct,  it is a metric that can be used to assess the current "will" of the network. Its up to the petition-maker to gain support for their idea.. but not necessarily required for them to have code. By having the vote you will already know if people are willing to run the new version or not..  no convincing should really be required assuming the vote reaches majority.

I personally suggest a formal place to create a detailed plan of implementation once a vote has been won,  think CIP's (clam improvement protocol) which could be hosted on the nochowerderforyou git repo.
 

or CLAP (CLAm Proposal) for short.

Dev1:  Did you get the CLAP?
Dev2:  Whattt?

[rocoro]

They will stake separately, but may be recombined when you stake, depending on your config.

So, how do you set the config so they won't recombine?
Thanks.

^bump  ..  does anyone else happen to know?

Don't have a client available at the moment, but it should be listed with the other execution flags.

-nostakesplit, possibly?

EDIT:
Can set -combinelimit, re: https://github.com/nochowderforyou/clams/commit/92b99052b055802ae80dcc996155f85f417d5618
Can set -splitsize, re: https://github.com/nochowderforyou/clams/commit/3f15194aa8ca2ad22e538554813a3967ca8596fe

Thanks!
so for example..  
If I have output amounts as piles of 5..  and I set ./clamd -combinelimit=5    (set to 5 or less?)
Then it won't combine into larger piles right?

^bump...     plus how do I use -staketo

just this?:
./clamd -staketo=<addresshere>