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

[fatbloke85]

what is a good size for an address, 50 clam, 100 clam or 500 clam?

15-30 seems to be the general recommendation.

It does not have to be different addresses, just different outputs. Every time you send coins you get a new output. You can send them all to the same address if you want, just break them up into multiple transactions. There is a command option for the in the CLI to do that for you, but I'm not sure about the GUI.

If you send coins from an address back to itself does that split your coins into multiple outputs? Can you do that or do you have to send coins from different addresses to a single address to get multiple outputs?

[smooth]

what is a good size for an address, 50 clam, 100 clam or 500 clam?

15-30 seems to be the general recommendation.

It does not have to be different addresses, just different outputs. Every time you send coins you get a new output. You can send them all to the same address if you want, just break them up into multiple transactions. There is a command option for the in the CLI to do that for you, but I'm not sure about the GUI.

If you send coins from an address back to itself does that split your coins into multiple outputs? Can you do that or do you have to send coins from different addresses to a single address to get multiple outputs?

The address doesn't matter. The only thing that matters is the amount paid from each transaction. If you use coin control you can see the individual outputs even if they have the same address.

Another thing you can do is set the this option in your clam.conf file:

splitsize=15

Then the wallet will automatically split your outputs down to 15 when it stakes. That's all you need to do.

[SuperClam]

what is a good size for an address, 50 clam, 100 clam or 500 clam?

15-30 seems to be the general recommendation.
It does not have to be different addresses, just different outputs. Every time you send coins you get a new output. You can send them all to the same address if you want, just break them up into multiple transactions. There is a command option for the in the CLI to do that for you, but I'm not sure about the GUI.

If you send coins from an address back to itself does that split your coins into multiple outputs? Can you do that or do you have to send coins from different addresses to a single address to get multiple outputs?

The address doesn't matter. The only thing that matters is the amount paid from each transaction. If you use coin control you can see the individual outputs even if they have the same address.
Another thing you can do is set the this option in your clam.conf file:
splitsize=15
Then the wallet will automatically split your outputs down to 15 when it stakes. That's all you need to do.

 
smooth,
you rock. 

[Johnny00]

Thanks. I've been staking for 24 hours and nothing. I thought it was every 8 hours

[tspacepilot]

Thanks. I've been staking for 24 hours and nothing. I thought it was every 8 hours

I think the stake rewards happen every minute (on the average).  I could be wrong.

[dooglus]

Thanks. I've been staking for 24 hours and nothing. I thought it was every 8 hours

I think the stake rewards happen every minute (on the average).  I could be wrong.

Yes, the network targets one block per minute. Though block timestamps are always multiples of 16 seconds (since some date in 1970 or something) and so cannot be exactly one minute apart from each other).

The only significance of 8 hours I can think of is that it's roughly the amount of time it takes for a block to mature after being staked. The staking output cannot be spent until it has 500 confirmations, and at 1 confirmation per minute that's a little over 8 hours.

Having said all that, staking is random. If you have 1000 CLAMs you can expect to stake about once per day on average at the moment. If you have more or less, change that estimate proportionally. The client uses the current network difficulty to estimate the expected time until staking. The network difficulty wanders up and down each day and so the estimate reported in the client wanders down and up as the difficulty adjusts. Like with Bitcoin mining, you never make "progress" towards staking a block. Every 16 seconds you either get to stake or you don't. Eventually you'll get to stake if you keep trying.

[zazarb]

Thanks. I've been staking for 24 hours and nothing. I thought it was every 8 hours

I think the stake rewards happen every minute (on the average).  I could be wrong.

Yes, the network targets one block per minute. Though block timestamps are always multiples of 16 seconds (since some date in 1970 or something) and so cannot be exactly one minute apart from each other).

The only significance of 8 hours I can think of is that it's roughly the amount of time it takes for a block to mature after being staked. The staking output cannot be spent until it has 500 confirmations, and at 1 confirmation per minute that's a little over 8 hours.

Having said all that, staking is random. If you have 1000 CLAMs you can expect to stake about once per day on average at the moment. If you have more or less, change that estimate proportionally. The client uses the current network difficulty to estimate the expected time until staking. The network difficulty wanders up and down each day and so the estimate reported in the client wanders down and up as the difficulty adjusts. Like with Bitcoin mining, you never make "progress" towards staking a block. Every 16 seconds you either get to stake or you don't. Eventually you'll get to stake if you keep trying.

damn.. whats wrong with my wallet ~140clam  already 23 day age
 and still not get reward..my patience is running out

[rocoro]

damn.. whats wrong with my wallet ~140clam  already 23 day age
 and still not get reward..my patience is running out

Again age doesn't matter,  you need more clams if you want to get a reward faster.

[andulolika]

Thanks. I've been staking for 24 hours and nothing. I thought it was every 8 hours

I think the stake rewards happen every minute (on the average).  I could be wrong.

Yes, the network targets one block per minute. Though block timestamps are always multiples of 16 seconds (since some date in 1970 or something) and so cannot be exactly one minute apart from each other).

The only significance of 8 hours I can think of is that it's roughly the amount of time it takes for a block to mature after being staked. The staking output cannot be spent until it has 500 confirmations, and at 1 confirmation per minute that's a little over 8 hours.

Having said all that, staking is random. If you have 1000 CLAMs you can expect to stake about once per day on average at the moment. If you have more or less, change that estimate proportionally. The client uses the current network difficulty to estimate the expected time until staking. The network difficulty wanders up and down each day and so the estimate reported in the client wanders down and up as the difficulty adjusts. Like with Bitcoin mining, you never make "progress" towards staking a block. Every 16 seconds you either get to stake or you don't. Eventually you'll get to stake if you keep trying.

damn.. whats wrong with my wallet ~140clam  already 23 day age
 and still not get reward..my patience is running out

Staking out of jd is a bit hard right now without a good amount of clams.

[dooglus]

damn.. whats wrong with my wallet ~140clam  already 23 day age
 and still not get reward..my patience is running out

You don't give me anywhere enough information to answer your question.

Can you tell me:

 * Are you keeping it online 24/7?

 * Is it up-to-date with the CLAM blockchain? ( run getblockcount in the debug console; compare output with the 3rd column at http://khashier.com/ )

 * Is it actually attempting to stake? (run getstakinginfo in the debug console; expect something like the following: )

{
  "enabled" : true,
  "staking" : true,
  "errors" : "",
  "currentblocksize" : 1000,
  "currentblocktx" : 0,
  "pooledtx" : 0,
  "difficulty" : 81531.22290140096,
  "search-interval" : 16,
  "weight" : 30404.01666316,
  "netstakeweight" : 1113517.408240138,
  "expectedtime" : 1852
}

[zazarb]

Are you keeping it online 24/7?

of course- non stop.

Is it up-to-date with the CLAM blockchain?

compared
22:44:58
1021207
vs
1021206   2016-06-05 19:44:00
the same time, but with different time zone

Is it actually attempting to stake?

{
"enabled" : true,
"staking" : true,
"errors" : "",
"currentblocksize" : 1000,
"currentblocktx" : 0,
"pooledtx" : 0,
"difficulty" : 120670.42481457,
"search-interval" : 16,
"weight" : 141.49010000,
"netstakeweight" : 1315856.37860787,
"expectedtime" : 586991
}

[dooglus]

"expectedtime" : 586991

That all looks right.

That expected time is in seconds, and 586991 / 3600.0 / 24 = 6.79 days

You should stake once every 7 days or so. You haven't staked at all in 23 days. That's unlucky.

Take a look at your debug.log file - it's in the same folder as your CLAM wallet.dat.

Do you see something like this?

starting stake
CWallet::CreateCoinStake() found no stake
stake took 3s
starting stake
CWallet::CreateCoinStake() found no stake
stake took 4s

If so, what do the "stake took ..." lines say? If it's more than 16 seconds that's a problem.

[SuperClam]

You should stake once every 7 days or so. You haven't staked at all in 23 days. That's unlucky.
Take a look at your debug.log file - it's in the same folder as your CLAM wallet.dat.
Do you see something like this?

starting stake
CWallet::CreateCoinStake() found no stake
stake took 3s
starting stake
CWallet::CreateCoinStake() found no stake
stake took 4s

If so, what do the "stake took ..." lines say? If it's more than 16 seconds that's a problem.

 
 
Might be worth your time to search your debug for orphans as well. 
It is possible that you found a block or two and they got orphaned.

[mraudio106]

hope i'm not repeating a prior post but cant figure out why my wallet wont go past March 18, or if it does it is very slow been trying for days and yes 24/7... loaded the latest bootstrap and no go... any suggestions???  Thanks

[jd1959]

Hi guys
I've read about Clam.conf file can somebody tell me what directory to put it in please? thanks in advance

Cheers Jon

[zazarb]

Hi guys
I've read about Clam.conf file can somebody tell me what directory to put it in please? thanks in advance

Cheers Jon

In Windows OS by default in this directory:
c:\Users\username\AppData\Roaming\Clam

regards
-zz

[SuperClam]

Hi guys
I've read about Clam.conf file can somebody tell me what directory to put it in please? thanks in advance
Cheers Jon

In Windows OS by default in this directory:
c:\Users\username\AppData\Roaming\Clam
regards
-zz

 
 
*nix it will be in ~/.clam

[SuperClam]

hope i'm not repeating a prior post but cant figure out why my wallet wont go past March 18, or if it does it is very slow been trying for days and yes 24/7... loaded the latest bootstrap and no go... any suggestions???  Thanks

 
 
Would need a debug log or additional information to identify a specific problem. 
If by 'past March 18' you mean it isn't sync'd, you can try the 'kick it' solution - restart the client. 
In the same vein, check your ./clamd getinfo and make sure you have peers. 
 
Just a couple thoughts.

[dooglus]

hope i'm not repeating a prior post but cant figure out why my wallet wont go past March 18, or if it does it is very slow been trying for days and yes 24/7... loaded the latest bootstrap and no go... any suggestions???  Thanks

 
 
Would need a debug log or additional information to identify a specific problem. 
If by 'past March 18' you mean it isn't sync'd, you can try the 'kick it' solution - restart the client. 
In the same vein, check your ./clamd getinfo and make sure you have peers. 
 
Just a couple thoughts.

The latest bootstrap shouldn't need "kicking". It goes to May 22nd.

[SuperClam]

hope i'm not repeating a prior post but cant figure out why my wallet wont go past March 18, or if it does it is very slow been trying for days and yes 24/7... loaded the latest bootstrap and no go... any suggestions???  Thanks

 
Would need a debug log or additional information to identify a specific problem. 
If by 'past March 18' you mean it isn't sync'd, you can try the 'kick it' solution - restart the client. 
In the same vein, check your ./clamd getinfo and make sure you have peers. 
Just a couple thoughts.

The latest bootstrap shouldn't need "kicking". It goes to May 22nd.

...bootstrap...

 
 
Good point. 
Are you certain the bootstrap 'loaded'..? 
It exists in the data directory renamed?