Topic: [ANN][CLAM] CLAMs, Proof-Of-Chain, Proof-Of-Working-Stake, a.k.a. "Clamcoin" - page 40. (Read 1151252 times)

Looking to buy 10,000 Clams & perhaps more, at 0.00058 (slightly negotiable)
If any big holders interested,do PM.

Sounds great. I like your statement that small purchases don’t require you risking your personal information.

Where does the liquidity come from? Is it connected to other exchanges so that its price is matching with the market price?

I tried your site it works very well, and not expensive. Nice site! Get a 10 of 10 from me=)

My new CLAM trading tool Swap is starting to get a decent bankroll.

This allows users to buy and sell CLAMS for Bitcoin and other altcoins.

We've completed over 420 trades today!  

I think our "checkout" process is the best in the game... it's even better than Dominos Pizza's checkout.  (here is a 1.5 minute video if you want to watch before trying: https://www.youtube.com/watch?v=5AJ2wNgfkR0)

My new CLAM trading tool Swap is starting to get a decent bankroll.

This allows users to buy and sell CLAMS for Bitcoin and other altcoins.

We've completed over 420 trades today!  

I think our "checkout" process is the best in the game... it's even better than Dominos Pizza's checkout.  (here is a 1.5 minute video if you want to watch before trying: https://www.youtube.com/watch?v=5AJ2wNgfkR0)

Any update on the new client, specifically the syncing issue?

Mine was 18 days behind and after 8 hours it's still struggling to sync: ORPHAN BLOCK 751

For those who run the client 24/7 this is never a problem, but for everyone else.....

That seems possible. RPi is 32 bit right? My clam client (linux command line) after it has been running a while is using about 3.4 GB of address space though not quite that much actual memory. Seems close to a 32 bit limit. I'm on 64 bit system with plenty of RAM so it doesn't matter at all in my case but it may in yours.

2019-01-14 17:13:28 SetBestChain: new best=888094194c94f66b793783d1b13e11268b86a2a94f3d2c69246ea649a6130d7b  height=2381492  trust=888852073952277551647  blocktrust=841655184282631  date=01/14/19 17:13:20
2019-01-14 17:13:28 ProcessBlock: ACCEPTED

when will the new wallet come out?

Also I am considering, that the size of the clam overgrew what RPi can handle - are there other RPi stakers here?

NTP can be inaccurate if you get the wrong mix of peers. My main router has 5 external peers, and all are at least 500ms off (both +ve and -ve) my computed time. One is at +2.3 seconds offset. These are all supposedly stratum 2 servers, learned from pool.ntp.org.

2019-01-12 10:21:21 ERROR: CheckBlock() : block timestamp too far in the future
2019-01-12 10:21:21 ERROR: ProcessBlock() : CheckBlock FAILED
2019-01-12 10:21:47 CheckStakeKernelHash() : using modifier 0x5519ccb791de9d5c at height=2378211 timestamp=2019-01-12 10:17:20 UTC for block from timestamp=2018-12-26 15:50:24 UTC
2019-01-12 10:21:47 CheckStakeKernelHash() : check modifier=0x5519ccb791de9d5c nTimeBlockFrom=1545839424 nTimeTxPrev=1545839395 nPrevout=108 nTimeTx=1547288272 hashProof=0000e6800376214e9c9a5a94d73c2c8680523dd565a4b06b98433386c43d95ae
2019-01-12 10:21:47 CheckStakeKernelHash() : using modifier 0x5519ccb791de9d5c at height=2378211 timestamp=2019-01-12 10:17:20 UTC for block from timestamp=2018-12-26 15:50:24 UTC
2019-01-12 10:21:47 CheckStakeKernelHash() : check modifier=0x5519ccb791de9d5c nTimeBlockFrom=1545839424 nTimeTxPrev=1545839395 nPrevout=108 nTimeTx=1547288272 hashProof=0000e6800376214e9c9a5a94d73c2c8680523dd565a4b06b98433386c43d95ae
2019-01-12 10:21:48 SetBestChain: new best=40e955aeab8f05a5dba5d6f569f99a236d1318d74a63fa0063f5f6282755703f  height=2378212  trust=886542851187320957639  blocktrust=664485070067994  date=01/12/19 10:17:52
2019-01-12 10:21:48 ProcessBlock: ACCEPTED
2019-01-12 10:21:48 ERROR: ProcessBlock() : already have block 2378212 40e955aeab8f05a5dba5d6f569f99a236d1318d74a63fa0063f5f6282755703f
2019-01-12 10:21:59 peer 188.40.206.114:31174: leap backwards in height request, from max 2311199 to current 275001. penalty=1/100
2019-01-12 10:22:11 force request: block 258ce97be5f2dabfa7e12d5bc41377f7f183f76874de6a770d6e80ef62bcb2d7
2019-01-12 10:22:14 ERROR: CheckBlock() : block timestamp too far in the future
2019-01-12 10:22:14 ERROR: ProcessBlock() : CheckBlock FAILED
2019-01-12 10:22:23 CheckStakeKernelHash() : using modifier 0x5519ccb791de9d5c at height=2378212 timestamp=2019-01-12 10:17:52 UTC for block from timestamp=2018-10-13 10:28:16 UTC
2019-01-12 10:22:23 CheckStakeKernelHash() : check modifier=0x5519ccb791de9d5c nTimeBlockFrom=1539426496 nTimeTxPrev=1539426496 nPrevout=1 nTimeTx=1547288304 hashProof=0000145d97e32a4144ef8f773b2f4fcfd5eb45a5bd863d95d0135fef207b095f
2019-01-12 10:22:23 CheckStakeKernelHash() : using modifier 0x5519ccb791de9d5c at height=2378212 timestamp=2019-01-12 10:17:52 UTC for block from timestamp=2018-10-13 10:28:16 UTC
2019-01-12 10:22:23 CheckStakeKernelHash() : check modifier=0x5519ccb791de9d5c nTimeBlockFrom=1539426496 nTimeTxPrev=1539426496 nPrevout=1 nTimeTx=1547288304 hashProof=0000145d97e32a4144ef8f773b2f4fcfd5eb45a5bd863d95d0135fef207b095f
2019-01-12 10:22:23 SetBestChain: new best=4a0bec133723366a1e5989948094f0f938b1049d88a833c759a84416f147aadf  height=2378213  trust=886543514991569125486  blocktrust=663804248167847  date=01/12/19 10:18:24
2019-01-12 10:22:23 ProcessBlock: ACCEPTED
2019-01-12 10:22:23 ERROR: ProcessBlock() : already have block 2378213 4a0bec133723366a1e5989948094f0f938b1049d88a833c759a84416f147aadf
2019-01-12 10:22:39 ERROR: CheckBlock() : block timestamp too far in the future
2019-01-12 10:22:39 ERROR: ProcessBlock() : CheckBlock FAILED
2019-01-12 10:23:11 CheckStakeKernelHash() : using modifier 0x5519ccb791de9d5c at height=2378213 timestamp=2019-01-12 10:18:24 UTC for block from timestamp=2018-12-19 14:34:08 UTC
2019-01-12 10:23:11 CheckStakeKernelHash() : check modifier=0x5519ccb791de9d5c nTimeBlockFrom=1545230048 nTimeTxPrev=1545230048 nPrevout=1 nTimeTx=1547288352 hashProof=00003186d2858ece5df2cfaafe08616b305556a5bedafe0e18f301b12d9bbeb6
2019-01-12 10:23:11 CheckStakeKernelHash() : using modifier 0x5519ccb791de9d5c at height=2378213 timestamp=2019-01-12 10:18:24 UTC for block from timestamp=2018-12-19 14:34:08 UTC
2019-01-12 10:23:11 CheckStakeKernelHash() : check modifier=0x5519ccb791de9d5c nTimeBlockFrom=1545230048 nTimeTxPrev=1545230048 nPrevout=1 nTimeTx=1547288352 hashProof=00003186d2858ece5df2cfaafe08616b305556a5bedafe0e18f301b12d9bbeb6
2019-01-12 10:23:11 SetBestChain: new best=c60d28f4ccdf3fee4634c78ce48ffe27b4c543bd41cd02e70eea994e9da2978d  height=2378214  trust=886544178455603001062  blocktrust=663464033875576  date=01/12/19 10:19:12
2019-01-12 10:23:11 ProcessBlock: ACCEPTED
2019-01-12 10:23:11 ERROR: ProcessBlock() : already have block 2378214 c60d28f4ccdf3fee4634c78ce48ffe27b4c543bd41cd02e70eea994e9da2978d
2019-01-12 10:23:20 ERROR: CheckBlock() : block timestamp too far in the future
2019-01-12 10:23:20 ERROR: ProcessBlock() : CheckBlock FAILED
2019-01-12 10:23:43 ERROR: CheckBlock() : block timestamp too far in the future
2019-01-12 10:23:43 ERROR: ProcessBlock() : CheckBlock FAILED
2019-01-12 10:24:14 CheckStakeKernelHash() : using modifier 0x5519ccb791de9d5c at height=2378214 timestamp=2019-01-12 10:19:12 UTC for block from timestamp=2018-11-07 03:15:28 UTC
2019-01-12 10:24:14 CheckStakeKernelHash() : check modifier=0x5519ccb791de9d5c nTimeBlockFrom=1541560528 nTimeTxPrev=1541560528 nPrevout=2 nTimeTx=1547288416 hashProof=0000262bef905f7f0317001f41c80c6a8d3a939a969be45f1e4a774a988799a5
2019-01-12 10:24:14 CheckStakeKernelHash() : using modifier 0x5519ccb791de9d5c at height=2378214 timestamp=2019-01-12 10:19:12 UTC for block from timestamp=2018-11-07 03:15:28 UTC
2019-01-12 10:24:14 CheckStakeKernelHash() : check modifier=0x5519ccb791de9d5c nTimeBlockFrom=1541560528 nTimeTxPrev=1541560528 nPrevout=2 nTimeTx=1547288416 hashProof=0000262bef905f7f0317001f41c80c6a8d3a939a969be45f1e4a774a988799a5
2019-01-12 10:24:15 SetBestChain: new best=11f8931146069a41be5be689d453702e6654a1efb322dcdba878bdd9c81a3f8f  height=2378215  trust=886544841579584905956  blocktrust=663123981904894  date=01/12/19 10:20:16
2019-01-12 10:24:15 ProcessBlock: ACCEPTED
2019-01-12 10:24:15 ERROR: ProcessBlock() : already have block 2378215 11f8931146069a41be5be689d453702e6654a1efb322dcdba878bdd9c81a3f8f
2019-01-12 10:24:31 ERROR: CheckBlock() : block timestamp too far in the future
2019-01-12 10:24:31 ERROR: ProcessBlock() : CheckBlock FAILED
2019-01-12 10:24:39 ERROR: CheckBlock() : block timestamp too far in the future
2019-01-12 10:24:39 ERROR: ProcessBlock() : CheckBlock FAILED
2019-01-12 10:25:05 ping timeout: 1200.010178s
2019-01-12 10:25:20 CheckStakeKernelHash() : using modifier 0x5519ccb791de9d5c at height=2378215 timestamp=2019-01-12 10:20:16 UTC for block from timestamp=2019-01-07 19:29:36 UTC
2019-01-12 10:25:20 CheckStakeKernelHash() : check modifier=0x5519ccb791de9d5c nTimeBlockFrom=1546889376 nTimeTxPrev=1546889376 nPrevout=2 nTimeTx=1547288480 hashProof=00000712539b11721c548a48f699512ed023ce4ddfbbd9b10611124ebcaee86b
2019-01-12 10:25:20 CheckStakeKernelHash() : using modifier 0x5519ccb791de9d5c at height=2378215 timestamp=2019-01-12 10:20:16 UTC for block from timestamp=2019-01-07 19:29:36 UTC
2019-01-12 10:25:20 CheckStakeKernelHash() : check modifier=0x5519ccb791de9d5c nTimeBlockFrom=1546889376 nTimeTxPrev=1546889376 nPrevout=2 nTimeTx=1547288480 hashProof=00000712539b11721c548a48f699512ed023ce4ddfbbd9b10611124ebcaee86b
2019-01-12 10:25:20 SetBestChain: new best=702f7d9d7bb53884f53e0f7f07000d3cdab9cd55d08fa3b2f35d340a2e5c682f  height=2378216  trust=886545504363770220410  blocktrust=662784185314454  date=01/12/19 10:21:20
2019-01-12 10:25:20 ProcessBlock: ACCEPTED
2019-01-12 10:25:20 ERROR: ProcessBlock() : already have block 2378216 702f7d9d7bb53884f53e0f7f07000d3cdab9cd55d08fa3b2f35d340a2e5c682f

This does not seem to be a bug in CLAM client, but a misconfiguration on your raspberry pi. Here is a link to get you started, but that's the best i can offer you as i don't have one to debug by myself:

https://stackoverflow.com/questions/41848227/debian-linux-raspbian-raspberry-pi-time-offset-is-65s-ahead-of-utc

Looks like you got forked from the network. To be sure, please verify the output of the command
and take a look at https://csexplorer.criptocambio.com.br/ or http://khashier.com/ to see if the number of the last block indexed is similar. A difference of 1 is acceptable, as the network can take a time to propagate blocks. But if the difference is bigger, then you got forked and need to resync

The Raspberry has the time correctly synchronized. I started the clam node on my work PC (also synced)
Both nodes are connected to the same peer 69.121.201.75:31174, but Raspberry says "timeoffset" : -185, WorkPC says "timeoffset" : 0,
I have no idea whats wrong...


Raspberry

ntpdate -d time1.google.com | sed -n '$s/.*offset //p'
-0.008269 sec

cli getpeerinfo | grep timeoffset
    "addr" : "67.191.63.234:31174",
    "timeoffset" : -182,
   (...)
Work PC (currently syncing)
ntpdate -d time1.google.com | sed -n '$s/.*offset //p'
host found : time1.google.com
0.000309 sec

        "addr" : "178.62.8.78:31174",
        "timeoffset" : 0,
        "addr" : "67.191.63.234:31174",
        "timeoffset" : -1,
        "addr" : "158.69.32.10:31174",
(...)

I have some difficulties staking recently. I should obtain one coin every ~30 hours, but my last stake dates back to 2 of January 2019.
I am wondering, if something is wrong with my configuration. The wallet seems to be fine.
Just a few minutes ago I got an orphaned block... :-(

Is it normal, to wait such a long time?