Thank you for the well written explanation......i didn't see anything about unstaked coins

Any pile of coin that's available as an input to a transaction is "unstaked" - it's either too young or it's currently "staking" (trying to solve a block). The chance of those piles "staking" is based on the number of coins and the "age" (i.e. time, number of confirms etc.) which combine to give the "weight". In that coin control screen you can see how the coins are split up (number of inputs per address) and the number of confirmations. This gives you an insight into their weight. Every pile of coins can potentially stake, although it has been pointed out that if less than (or equal to?) 0.1 coins it effectively has 0 chance.

As Superclam says, when you send coins you might "break up" a partially used input and the "age" for that input (chance it will earn a reward) resets. This is not good and should be avoided, as it will mean that these coins will take that much longer to stake.

What's unique about CLAMs over traditional POS is that while logic might suggest that you should have all your coins in one pile (number of coins adds weight) that doesn't work out so well in practice because the reward is fixed(*). While your larger pile of coins has a better chance of solving a block than a smaller one (at the same age), a set of smaller blocks will all eventually stake anyway, potentially giving you a higher return (multiple rewards rather than just one). How you split up your coins to maximise returns is up to you to decide.

"Staked" coins don't appear as available as inputs in the coin control window - their total is displayed on the main screen as "Stake" and are unavailable to spend for 510 confirms.

(*) Although the standard reward is fixed (0.1 CLAM) there is a chance of a (much) higher payout should you be lucky and hit a lotto block (up to 1,000 CLAM). Each time you solve a block there's the potential to "win" one of these, so it's another reason why multiple smaller piles of staking coins is much better than a single larger one.

Hope the above helps!

When they stake, yes the number of coins staking will move to there. You'll also see a transaction entry in the transaction list marked "Mined" (most likely with a value of 0.1 but you never know it could be more!). When that reaches 510 confirms the "Staked" coins will become available in your spend balance again and be ready to start staking all over again.

"...and should remain active until clams balance changes..."
Not quite.

The CLAMS used to stake are the CLAMS listed on the "Spendable" line.

The "Stake" line of your balance are the CLAMS which have RECENTLY staked.

Edit:
dooglus made a good point. (already:recently).

In fact, the "Stake" line is the total of all the CLAMs which have RECENTLY staked, and so are currently unavailable for spending until they mature (which takes 510 blocks, or about 9 hours).

I have a doubt.
"Coin Control" screen can be seen in tree mode or in list mode. When I see it in tree mode I notice that there are addresses with 1 node inside and addresses with more than 1 node inside. The question is: Which is called "pile" (or "output") ?  Is it each one of the nodes belonging to one address, or all the nodes of an address ?.  If I have the address A with 2 nodes, one with 5 CLAM and other with 3 CLAM; if I select the node of 3 CLAM and send it to another address, the age of node of 5 CLAM will be reseted ?

Thanks.

Addresses almost never matter. It's all about the individual outputs. Your 3 and your 5 are separate things with their own ages.

The client will probably merge them into a single output when either of them stakes, so you might want to keep them in different addresses. That will stop them being merged.

looks like the address x9S2gMQQ5iKrP9SwRJ6PF9Q3wqDxRegc2w has a ton of 2.6 clam piles

when i try to check http://khashier.com:2750/address/x9S2gMQQ5iKrP9SwRJ6PF9Q3wqDxRegc2w
it says "I'm sorry, this address has too many records to display."

this address has lots of POS blocks, i would have thought the client would combine the clams since they are staking in less than 24 hrs

Which is what I've done, although it begs the question - is there a limit to the number of addresses per wallet?

I don't think I ever posted this:

http://pastie.org/9456438

It's a small Python script that takes any number of BTC, LTC, DOGE, and CLAM addresses and gives links to the corresponding blockchain explorer pages for the equivalent BTC, LTC, DOGE, and CLAM addresses.

When there was a giant influx of newly dug CLAMs about a week ago, I ran this script on a bunch of the CLAM addresses that were staking, and discovered that the new CLAMs were being dug from DOGE addresses.

Here's an example of it in use:

$ ./clam.py 18KSgPcNRPi9K4bp91Vb3pVNygPon4y5Pw x9S2gMQQ5iKrP9SwRJ6PF9Q3wqDxRegc2w

   BTC: http://blockchain.info/address/18KSgPcNRPi9K4bp91Vb3pVNygPon4y5Pw
  DOGE: http://dogechain.info/address/DCTYDeZ1iocRr4nQsbV9baeyrp878jRzaG
   LTC: http://block-explorer.com/address/LSYPwbvCW3xCZsHyK9UtKqZ9Btm5wrJXxa
  CLAM: http://khashier.com:2750/address/xFd5aGSqh7CBMShgVV8FUznACnh3DALPss


   BTC: http://blockchain.info/address/128PnUZvozqpLmM54pTioy7Giivj44ketX
  DOGE: http://dogechain.info/address/D6GVKjWa7Qk6smXfoQTHMjGsbrf2Nvx5Po
   LTC: http://block-explorer.com/address/LLMM3gsktf5sba3EExT25zB2vwJ17S9JV2
  CLAM: http://khashier.com:2750/address/x9S2gMQQ5iKrP9SwRJ6PF9Q3wqDxRegc2w


It uses https://github.com/jgarzik/python-bitcoinlib.git to do the heavy lifting, so you'll need to fetch that using git, and update the path to it in the script itself.

Edit: I forgot to say why this is useful... If you only just heard about CLAMs, and are worried about sharing your Bitcoin wallet with the CLAM client, you can use this script to convert your BTC addresses to CLAM addresses and look up the balance on the CLAM address without needed to give anyone your private keys at all. Bear in mind that your wallet probably has a bunch of "change" addresses in it which it carefully hides from view, and those change addresses may have CLAMs on them too, so you probably have more CLAMs than you think...

Edit2: the two addresses I gave in the example aren't great. The first is a BTC address that wasn't funded for the initial CLAM distribution, and the second is a CLAM address that I created in the CLAM client. But you get the idea!