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

[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.

[1715061377]

1715061377

[1715061377]

1715061377

[1715061377]

1715061377

[1715061377]

1715061377

[1715061377]

1715061377

[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? 

[zazarb]

"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.

recent 3 day I have a higher problems with my pc (hdd issue), so relaunch wallet just now
I look to log file and see that in case successful stake- "stake took 0s"
but further going that:
(I snipe tousands similar"ORPHAN BLOCK 751" line)

Code:

deae8c622be746328e71c5b3e
ERROR: ProcessBlock() : already have block (orphan) 22010a88394f699ac48dffd09eb3f33728e90a7264a784fb2c72a563694c2d73
ERROR: ProcessBlock() : already have block (orphan) 220f9aae758f3d32b84afaa6d46a03f96f571f22711bdf3a8e13644b5ca1b5a3
ERROR: ProcessBlock() : already have block (orphan) 220f9aae758f3d32b84afaa6d46a03f96f571f22711bdf3a8e13644b5ca1b5a3
ERROR: ProcessBlock() : already have block (orphan) 
-snip-


ProcessBlock: ORPHAN BLOCK 751, prev=8f6d7170f1bc8000addcdb348386d08d4534eb756b598efb2ca38e542eb27d6f
ProcessBlock: ORPHAN BLOCK 751, prev=4a6c09d5f9ea7269002379dfa002ace37c9798e85691325c29941f3cc3f345ed
ProcessBlock: ORPHAN BLOCK 751, prev=fd7257c1e685c890cf2b36777c032acc9a06b814a0ed2e198112dcd40cc4df99
ERROR: AcceptBlock() : incorrect proof-of-stake
ERROR: ProcessBlock() : AcceptBlock FAILED
Misbehaving: 74.118.192.18:31174 (0 -> 100) DISCONNECTING
socket recv error 10054
socket recv error 10054
socket recv error 10054
socket recv error 10054
Added time data, samples 11, offset +4 (+0 minutes)
nTimeOffset = +4  (+0 minutes)
receive version message: version 60014, blocks=1026015, us=*****, them=[2602:100:4b87:2f8f:2::]:31174, peer=75.135.47.143:31174
ERROR: AcceptBlock() : incorrect proof-of-stake
ERROR: ProcessBlock() : AcceptBlock FAILED
Misbehaving: 75.135.47.143:31174 (0 -> 100) DISCONNECTING
socket recv error 10054
addcon thread interrupt
dumpaddr thread stop
net thread interrupt
msghand thread interrupt
opencon thread interrupt
Shutdown : In progress...
StopNode()
Shutdown : done




















Clam version v1.4.17 (2015-09-23 21:07:15 -0300)
Using OpenSSL version OpenSSL 1.0.1j 15 Oct 2014
Startup time: 06/09/16 08:17:03
Default data directory C:\Users\*****\AppData\Roaming\Clam
Used data directory C:\Users\*****\AppData\Roaming\Clam
init message: Verifying database integrity...
dbenv.open LogDir=C:\Users\******\AppData\Roaming\Clam\database ErrorFile=C:\Users\*****\AppData\Roaming\Clam\db.log
Bound to [::]:31174
Bound to 0.0.0.0:31174
init message: Loading block index...
Opening LevelDB in C:\Users\*****\AppData\Roaming\Clam\txleveldb
Transaction index version is 70509
Opened LevelDB successfully
LoadBlockIndex(): hashBestChain=91dfdb0f7d573ba1636a05a8897f731fc505d816871d832e3eefaddf16da958d  height=1021312  trust=5365710003885107  date=06/05/16 21:36:00
LoadBlockIndex(): synchronized checkpoint b560c121438f630401c102767587b70cb0cc7d1e0c09114dd0b91455262aa64c
Verifying last 500 blocks at level 1
 block index           96784ms
init message: Loading wallet...
nFileVersion = 1041700
Keys: 237 plaintext, 0 encrypted, 237 w/ metadata, 237 total
 wallet                 1903ms
init message: Loading addresses...
Loaded 3527 addresses from peers.dat  85ms
mapBlockIndex.size() = 1023859
nBestHeight = 1021312
setKeyPool.size() = 101
mapWallet.size() = 478
mapAddressBook.size() = 137
dnsseed thread start
net thread start
opencon thread start
dumpaddr thread start
upnp thread start
addcon thread start
msghand thread start
init message: Done loading
Added time data, samples 2, offset +5 (+0 minutes)
No valid UPnP IGDs found
upnp thread exit
P2P peers available. Skipped DNS seeding.
dnsseed thread exit
receive version message: version 60014, blocks=1026243, us=*****, them=144.76.239.66:31174, peer=144.76.239.66:31174
Added time data, samples 3, offset -8 (+0 minutes)
receive version message: version 60014, blocks=1026243, us=*****, them=74.207.230.61:31174, peer=74.207.230.61:31174
Added time data, samples 4, offset -8 (+0 minutes)
receive version message: version 60014, blocks=1026243, us=*****, them=176.9.113.75:31174, peer=176.9.113.75:31174
Added time data, samples 5, offset -8 (+0 minutes)
nTimeOffset = -8  (+0 minutes)
receive version message: version 60014, blocks=899813, us=*****, them=188.93.93.9:31174, peer=188.93.93.9:31174
Added time data, samples 6, offset -1 (+0 minutes)
receive version message: version 60014, blocks=1026243, us=*****, them=95.176.184.9:31174, peer=89.142.77.12:31174
ERROR: AcceptBlock() : incorrect proof-of-stake
ERROR: ProcessBlock() : AcceptBlock FAILED
Misbehaving: 144.76.239.66:31174 (0 -> 100) DISCONNECTING
Added time data, samples 7, offset +7 (+0 minutes)
nTimeOffset = -1  (+0 minutes)
receive version message: version 60014, blocks=1026243, us=*****, them=84.25.187.9:31174, peer=84.25.192.90:31174
Added time data, samples 8, offset +5 (+0 minutes)
receive version message: version 60014, blocks=840488, us=*****, them=158.69.27.82:31174, peer=158.69.27.82:31174
Added time data, samples 9, offset +6 (+0 minutes)
nTimeOffset = +0  (+0 minutes)
receive version message: version 60014, blocks=1026243, us=*****, them=199.233.246.224:31174, peer=199.233.246.224:31174
Added time data, samples 10, offset +8 (+0 minutes)
receive version message: version 60014, blocks=1026243, us=*****, them=78.14.250.252:31174, peer=78.14.249.80:31174
Added time data, samples 11, offset +4 (+0 minutes)
nTimeOffset = +4  (+0 minutes)
receive version message: version 60014, blocks=963523, us=*****, them=73.40.156.2:31174, peer=73.40.156.2:31174
Added time data, samples 12, offset +7 (+0 minutes)
receive version message: version 60014, blocks=1026243, us=*****, them=0.0.0.0:31174, peer=87.3.201.29:31174
Added time data, samples 13, offset +8 (+0 minutes)
nTimeOffset = +5  (+0 minutes)
receive version message: version 60014, blocks=1026243, us=78.62.83.197:63425, them=174.117.39.176:31174, peer=174.117.39.176:31174
Added time data, samples 14, offset +4 (+0 minutes)
receive version message: version 60014, blocks=1026243, us=*****, them=67.84.56.61:31174, peer=67.84.56.61:31174
Added time data, samples 15, offset +21 (+0 minutes)
nTimeOffset = +5  (+0 minutes)
receive version message: version 60014, blocks=1026243, us=*****, them=188.152.77.192:31174, peer=188.152.77.192:31174
Added time data, samples 16, offset +7 (+0 minutes)
receive version message: version 60014, blocks=1026243, us=*****:63436, them=[2602:100:4b87:2f8f:2::]:31174, peer=75.135.47.143:31174
Added time data, samples 17, offset +7 (+0 minutes)
nTimeOffset = +5  (+0 minutes)
receive version message: version 60014, blocks=674183, us=*****, them=115.70.90.161:31174, peer=115.70.90.161:31174
ProcessBlock: ORPHAN BLOCK 0, prev=2cfa939011c0abc6c4abfad516d0f5f9eac981cda74133dff2330ab970f5da26
ProcessBlock: ORPHAN BLOCK 1, prev=39ba418ede7002a5acc87d3673f70ccaa31552a7d5a7f31e37b95981b26a76ea
ProcessBlock: ORPHAN BLOCK 2, prev=268e662550684931b81f293042a48d5858919b557ebcba6b9955a092a7b4d99e
ProcessBlock: ORPHAN BLOCK 3, prev=0b45242b4ed19395bda836b8512030680772b80924d196ad60798673b9621364
ProcessBlock: ORPHAN BLOCK 4, prev=bf42cc810e9203ea10119dd8f84e24702e2d4de48e07e3ad68bed2283e17f11b
ProcessBlock: ORPHAN BLOCK 5, prev=9bd40e3c4226917310fdaa9089f98e0a952301ba4d1db86b9755571b2a36deb5
ProcessBlock: ORPHAN BLOCK 6, prev=c5de6f2937dadda89d442a1eb45b00e6df50fa516dafe1962aaa6f883bd140a4
stake took 0s
ProcessBlock: ORPHAN BLOCK 7, prev=9119334e74cf40f28c90bf0fe04902d9697a339b23ded9f0cb7568cf0b3804dc
ProcessBlock: ORPHAN BLOCK 8, prev=6aa4a212463e45071e160b58add18a56898c0bbd04436da7ad1360e006789273
ProcessBlock: ORPHAN BLOCK 9, prev=39f4de732ad522e9e44b986b7aa147002fc8831e774233fd31692e3db1b82e35
ProcessBlock: ORPHAN BLOCK 10, prev=5e6ce1c92e7b6590bcdb4f6fb775aff27438854d0f06e17a1e07a45302fe444d
ProcessBlock: ORPHAN BLOCK 11, prev=bf11e6a6f7896581b34ec506e3fb4d0ebf7654f8d535322bde7495a05ad7284f
ProcessBlock: ORPHAN BLOCK 12, prev=a056180add77720f6101fbdda143677dd8c6a61c3d6221fbfb90b0f2d435560a
Added time data, samples 18, offset +6 (+0 minutes)
receive version message: version 60014, blocks=1026244, us=*****, them=104.236.149.112:31174, peer=104.236.149.112:31174
ProcessBlock: ORPHAN BLOCK 13, prev=dfdc7b527629ccd63b50bd186b81f0d932763d53eb0ceafc6bb1097605b2fd8e

ProcessBlock: ORPHAN BLOCK 751, prev=72d47acac3529906ba6c21ba60a8b57f8f44884df98097f2fac74aa746307d16
stake took 0s
stake took 0s
stake took 0s
peer 24.36.165.53:31174: leap backwards in height request, from max 826474 to current 277001. penalty=3/100
stake took 0s
stake took 0s
stake took 0s
disconnecting /Satoshi:1.4.4/
ProcessMessage(version, 100 bytes) FAILED
stake took 0s
stake took 0s
peer 73.40.156.2:31174: leap backwards in height request, from max 963567 to current 276001. penalty=5/100
stake took 0s
peer 188.93.93.9:31174: leap backwards in height request, from max 899831 to current 276001. penalty=2/100
stake took 0s
peer 73.40.156.2:31174: leap backwards in height request, from max 963568 to current 278001. penalty=6/100
stake took 0s
stake took 0s
stake took 0s
stake took 0s
stake took 0s
stake took 0s
stake took 0s
stake took 0s
stake took 0s
stake took 0s
stake took 0s
stake took 0s
stake took 0s
disconnecting /Satoshi:1.4.4/
ProcessMessage(version, 100 bytes) FAILED
stake took 0s
stake took 0s
stake took 0s
stake took 0s
stake took 0s
stake took 0s
stake took 0s
stake took 0s
stake took 0s
stake took 0s
stake took 0s

[Johnny00]

Clams keep dropping.

[Johnny00]

Dropped 20%. Keeps hitting new lows

[crazyivan]

It ll bounce back after halving, just watch. This is not natural drop, something s behind this and smart money will take advantage of this.