Quote from: gamblingbad on December 05, 2015, 12:17:29 PM

people can vote sending clam? but can someone send many times the same coins?

No, only by staking. The screenshot showed a negative fee, so you can tell it's a stake. It's merging two smaller outputs into a larger one, but the output is 1 CLAM bigger than the sum of the inputs.

Quote from: gamblingbad on December 05, 2015, 01:20:21 PM

But need 50% of votes for change? So if jd have 750k clam votes change will happend?

Yesterday I implemented a system for Just-Dice investors to tell the site which petitions they want to support. Each time the site's wallets stake a block, they set the CLAMspeech according to user wishes. This page shows how the JD wallets are voting at any particular point in time. Currently Just-Dice is abstaining in 84% of the blocks it stakes, since the owners of 84% of the bankroll have not yet specified any petitions that they support.

Quote from: clf99 on December 05, 2015, 02:03:35 PM

Change the behavior of the opcode CHECKLOCKTIMEVERIFY so that it behaves identically to Bitcoin's implementation.

the above is one of the petitions.
wtf does it mean?

Peter Todd made a proposal for Bitcoin a long time ago, that if implemented would allow users to send coins to others in a way such that they couldn't be spent until a fixed date, or a fixed block number. That wasn't possible to do in any other way at the time.

Shortly after the initial proposal was made, the feature was implemented in CLAM.

After that, Peter Todd's proposal was improved, and finally implemented in Bitcoin. CLAM is still running with the initial, inferior proposal.

Kef's petition is saying we should switch CLAM to the way Bitcoin ended up implementing it.

Quote from: o_dima on December 05, 2015, 06:05:45 PM

Let suppose I have enough clamcoins to catch stacking block. If I vote for petition with my staking amount then send all my clams to poloniex or JD then remove client, intstall it again, change IP (another proxy) send my clammies back to new wallet and try to vote same petition again? Will it be counted?

Yes, you could do that, but it wouldn't help you at all.

Your plan:

1. vote
2. move to polo
3. move back
4. vote again

Note that after staking, your coins cannot be moved for 500 blocks, so you have an 8 hour gap between steps 1 and 2. Moving to polo and back only takes ~10 minutes each way, but coins can't vote again until they have sat for 4 hours without being involved in a transaction. So there's at least a 4 hour gap between steps 3 and 4. Adding all the gaps together I make that about 12.5 hours between steps 1 and 4.

A better plan would be:

1. vote
2. vote again

You still have the 500 block (8 hour) gap between the two steps, but that's all.

And even better plan would be:

1. split your coins into lots of small outputs
2. vote
3. vote again

There's a 4 hour gap between 1 and 2, but then there's very little gap between step 2 and 3, or between all your future votes, since when you stake only one of your small outputs is locked up for 500 blocks and the rest keep on trying to stake.