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

[Michail1]

Sir I am already done with bootstrap and it makes my wallet sync fast by " importing files " now it's back to "synchronizing with the network and it takes a day now and it is so slow . I thought  bootstrap can go up to 2M blocks now it is just 1.8 M blocks ( approx 19 weeks behind ) is this correct or is there another patch I need to download ?

Well, it's basically the issue being reported.

The client only imports blocks to a certain point and then goes to sync with network.  It's either a 2GB file limit for the error or the public bootstrap is broken.
In any case, I've also encountered that the client keeps stopping and has to be restarted, but no indication on the UI.  Only that the bkl0002 stops changing in size.

I've been trying for 2 days now with no less than 20 restarts.
At block 1853826 now.... 18 weeks behind.

[cherry11800]

Hi,Dev,I want to know the latest road map of CLAM and hope to get your help. Thank you

[lolika]

whats the ETA of new wallet ? and what futures will contain ?

[Enzo05]

Sir I am already done with bootstrap and it makes my wallet sync fast by " importing files " now it's back to "synchronizing with the network and it takes a day now and it is so slow . I thought  bootstrap can go up to 2M blocks now it is just 1.8 M blocks ( approx 19 weeks behind ) is this correct or is there another patch I need to download ?

Well, it's basically the issue being reported.

The client only imports blocks to a certain point and then goes to sync with network.  It's either a 2GB file limit for the error or the public bootstrap is broken.
In any case, I've also encountered that the client keeps stopping and has to be restarted, but no indication on the UI.  Only that the bkl0002 stops changing in size.

I've been trying for 2 days now with no less than 20 restarts.
At block 1853826 now.... 18 weeks behind.

Oh not a good news but I am hoping that they do some changes or either fixed the issue . I really want to do staking with clam .

[dooglus]

I don't think we expect the blk* files to be identical between different clients. They can contain orphaned blocks for example. But the total size of the blk files should be at least as big as the bootstrap.dat file since the bootstrap.dat file doesn't contain orphaned blocks.

This makes me think you're doing more than simply "cat blk*.dat > bootstrap.dat", so how are you generating the bootstrap?

A bootstrap.dat file has to contain the blocks in the correct order, or it won't import. The blk*.dat files contain the blocks in the order they were received from peers, and so are often not in the correct order.

I create my bootstrap.dat files using the "dumpbootstrap" RPC in the client, which dumps the blocks out to a file in the correct order.

[dooglus]

Question is why my client stopped importing blocks in the middle which appears to have happened to you.  Space and Ram is not an issue and running on SSD.

I'm trying an import of the same bootstrap.dat from scratch. I'll let you know how it goes.

Here's how it started:

~/.clam$ sha256sum boot*
713b93b7458e88500f1e32557f0bc58b9f05a6b13e1de31576f25f5300184c96  bootstrap.dat
~/.clam$ ls -al
total 2504976
drwxrwxr-x 2 user user       4096 May 18 00:10 .
drwxr-xr-x 5 user user       4096 May 18 00:05 ..
-rw-rw-r-- 1 user user 2565076446 May 18 00:08 bootstrap.dat
-rw-rw-r-- 1 user user        148 May 18 00:09 clam.conf
~/.clam$ cat clam.conf
flushwallet=0
rpcuser=...
rpcpassword=...
keypool=1
upnp=0
server=1
daemon=1
irc=0
logtimestamps=1
port=45319
rpcport=45318
connect=0
~/.clam$ clamd
Clam server starting
~/.clam$ head -30 debug.log | grep Clam
2018-05-18 00:10:53 Clam version v1.4.17-139-gf0707d3 (2017-04-10 17:28:15 +0000)
~/.clam$ while :; do echo $(date) - $(tail debug.log | grep height= | tail -1); sleep 10; done
Fri May 18 00:11:41 UTC 2018 - 2018-05-18 00:11:41 SetBestChain: new best=000003b6025e531c9e165989bbbfd8a19be5ba2511a3d2d070498c1aa1136dd3 height=5717 trust=7401805469 blocktrust=1063958 date=05/16/14 11:09:36
Fri May 18 00:11:51 UTC 2018 - 2018-05-18 00:11:51 SetBestChain: new best=00000b2c5bbbc95cfbb045a8ca58e3820b07aa5dd5472461995addcb780590a2 height=6776 trust=8515692837 blocktrust=1048577 date=05/16/14 16:25:59
Fri May 18 00:12:01 UTC 2018 - 2018-05-18 00:12:01 SetBestChain: new best=000004730c32869e48fc4cd6dc1a99d7c3aae99fcbfa1037f682a6d8fe95ec35 height=8012 trust=9815316936 blocktrust=1048577 date=05/16/14 20:28:13
[...]
Fri May 18 01:36:23 UTC 2018 - 2018-05-18 01:36:23 SetBestChain: new best=f9243b101d293abc7099795aafd26fadffc708069fae803c9ec322ce63297754 height=293123 trust=6608808633831582027 blocktrust=152735179784970 date=01/12/15 19:51:44
Fri May 18 01:36:33 UTC 2018 - 2018-05-18 01:36:33 SetBestChain: new best=ebf8f79f2f8123797277110086d1a6c3446875787755633b61dbcbce9f92d1c5 height=293539 trust=6670194310946165725 blocktrust=157644268458826 date=01/13/15 02:52:16
Fri May 18 01:36:43 UTC 2018 - 2018-05-18 01:36:43 SetBestChain: new best=a1e6fc4fcfc1f384544617095a4405582e0c3bfc3328d5eca6217349acaba834 height=293958 trust=6728348153276871682 blocktrust=152354218550930 date=01/13/15 09:47:44
[...]
Fri May 18 10:45:27 UTC 2018 - 2018-05-18 10:45:27 SetBestChain: new best=47125008d327c11c4716e9df01ece7567fd3e12d5d9622bb34544ae6f7649bf2 height=1322104 trust=380221172138139629293 blocktrust=213286745834214 date=01/02/17 15:27:12
Fri May 18 10:45:37 UTC 2018 - 2018-05-18 10:45:37 SetBestChain: new best=83a65fd9b981138876b2a310da465b2ce9556fec651417f59bf204f0eb7004de height=1322299 trust=380267370908500849341 blocktrust=271563185633458 date=01/02/17 18:36:48
Fri May 18 10:45:47 UTC 2018 - 2018-05-18 10:45:47 SetBestChain: new best=8c3e5bbbe2d94f9448f328df91aefac9acb94dc410c32192118769c29fdcaae0 height=1322533 trust=380329215185451050218 blocktrust=246752776608651 date=01/02/17 22:34:24

What version of the CLAM client are you using? You'll see it in the debug.log. Mine is "Clam version v1.4.17-139-gf0707d3 (2017-04-10 17:28:15 +0000)".

[dooglus]

Net results for me...
It works great until block 1781476.  It then runs into an error.
If I had to guess though, I would say this is when the client hits a kind of 2GB windows file limit, an error is flagged and the client then goes into syncing mode instead of importing blocks from the bootstrap.

It could be an issue with 2GB filesize limit I guess, or a signed 32 bit variable in the code perhaps. 2^31 = 2147483648.

I would suggest putting "connect=0" in the clam.conf to stop the client ever going to "live sync".

[Enzo05]

Net results for me...
It works great until block 1781476.  It then runs into an error.
If I had to guess though, I would say this is when the client hits a kind of 2GB windows file limit, an error is flagged and the client then goes into syncing mode instead of importing blocks from the bootstrap.

It could be an issue with 2GB filesize limit I guess, or a signed 32 bit variable in the code perhaps. 2^31 = 2147483648.

I would suggest putting "connect=0" in the clam.conf to stop the client ever going to "live sync".

Hello ! I also have the same issue and supposed to go 2M blocks but I am stack at 1.85 M blocks and its not importing anymore . Where can I find this ( calm.conf ) ?

[dooglus]

Where can I find this ( calm.conf ) ?

clam.conf is a file in the same folder as your wallet.dat. You make it yourself - it's a regular text file.

[dooglus]

It could be an issue with 2GB filesize limit I guess, or a signed 32 bit variable in the code perhaps. 2^31 = 2147483648.

I see a problem when the bootstrap.dat reaches 4 GB, due to the use of an unsigned int, but don't see a 2 GB limit yet:

https://github.com/nochowderforyou/clams/blob/v1.4.17/src/main.cpp#L2870

Code:

unsigned int nPos = 0;
[...]
fseek(blkdat, nPos, SEEK_SET);

Edit: I tried making a bootstrap.dat file which started with 4000 MB of zero bytes and then had the regular block data. The client quickly skipped the first 4000 MB and started complaining:

2018-05-18 12:16:03 ERROR: ProcessBlock() : already have block 0 00000c3ce6b3d823a35224a39798eca9ad889966aeb5a9da7b960ffb9869db35
2018-05-18 12:16:03 ERROR: ProcessBlock() : already have block 1 00000feca63cbde350712358668e0fe90e96c97efab3f0ff5fd9f3147dd2f53e
2018-05-18 12:16:03 ERROR: ProcessBlock() : already have block 2 0000042f7f9811948352d2ecc9215916f2276a5259ca4cdc4ccfb77a72ed8ebc

as expected. But then, after 96 MB of block data it wrapped around:

2018-05-18 12:16:10 ERROR: ProcessBlock() : already have block 8571 000006ff5c3a5829e0da80d9afb609435e887c51123f5afeb5f6afe5da819423
2018-05-18 12:16:10 ERROR: ProcessBlock() : already have block 8572 0000022cc43c5975e8ec01d978179b1fa3b26e9fad73aa2306c85f82854fad35
2018-05-18 12:16:10 ERROR: ProcessBlock() : already have block 8573 00000574ef1a20a79eb9c3525ed69af881e778f2100559d340fbc06ca1252240
2018-05-18 12:16:10 ERROR: ProcessBlock() : already have block 0 00000c3ce6b3d823a35224a39798eca9ad889966aeb5a9da7b960ffb9869db35
2018-05-18 12:16:10 ERROR: ProcessBlock() : already have block 1 00000feca63cbde350712358668e0fe90e96c97efab3f0ff5fd9f3147dd2f53e
2018-05-18 12:16:10 ERROR: ProcessBlock() : already have block 2 0000042f7f9811948352d2ecc9215916f2276a5259ca4cdc4ccfb77a72ed8ebc

So that's the 4 GB bug, but we won't be seeing that yet.

I tried putting 2100 MB of zero bytes before the bootstrap data and it seemed to be able to skip the >2 GB of junk just fine. So I don't know what the problem is yet.

My import that I started earlier is still running. I'll leave it running and see whether it eventually fails or not.

[criptocambio]

Sir I am already done with bootstrap and it makes my wallet sync fast by " importing files " now it's back to "synchronizing with the network and it takes a day now and it is so slow . I thought  bootstrap can go up to 2M blocks now it is just 1.8 M blocks ( approx 19 weeks behind ) is this correct or is there another patch I need to download ?

Well, it's basically the issue being reported.

The client only imports blocks to a certain point and then goes to sync with network.  It's either a 2GB file limit for the error or the public bootstrap is broken.
In any case, I've also encountered that the client keeps stopping and has to be restarted, but no indication on the UI.  Only that the bkl0002 stops changing in size.

I've been trying for 2 days now with no less than 20 restarts.
At block 1853826 now.... 18 weeks behind.

The restarts are needed to remove the orphan blocks that are currently in memory, hardcoded to 99 in earlier versions of bitcoin if i remember correctly. To avoid this, try

Code:

maxorphanblocks=<high number here>

in clam.conf

[dooglus]

The restarts are needed to remove the orphan blocks that are currently in memory, hardcoded to 99 in earlier versions of bitcoin if i remember correctly. To avoid this, try

Code:

maxorphanblocks=<high number here>

in clam.conf

We're talking about importing from a bootstrap.dat file. Bootstrap files don't contain orphans, and no network connections are made until the bootstrap.dat import finishes.

[criptocambio]

The restarts are needed to remove the orphan blocks that are currently in memory, hardcoded to 99 in earlier versions of bitcoin if i remember correctly. To avoid this, try

Code:

maxorphanblocks=<high number here>

in clam.conf

We're talking about importing from a bootstrap.dat file. Bootstrap files don't contain orphans, and no network connections are made until the bootstrap.dat import finishes.

Right, but the use of this config makes the process of syncing a lot faster without the need for a bootstrap as he is only 18 weeks behind. Maybe in the new version this problem with the bootstrap file is corrected, but until there they need to sync as fast as possible.

Talking about bootstrap, what version of windows did you try? I think windows limits memory usage for each process to 2gb in the 32 bits version, maybe this have any correlation

https://en.wikipedia.org/wiki/2_GB_limit

[dooglus]

Talking about bootstrap, what version of windows did you try?

I don't use Windows and haven't for many years. I think the last version I used was XP.

[Enzo05]

Where can I find this ( calm.conf ) ?

clam.conf is a file in the same folder as your wallet.dat. You make it yourself - it's a regular text file.

Sir I am already done with bootstrap and it makes my wallet sync fast by " importing files " now it's back to "synchronizing with the network and it takes a day now and it is so slow . I thought  bootstrap can go up to 2M blocks now it is just 1.8 M blocks ( approx 19 weeks behind ) is this correct or is there another patch I need to download ?

Well, it's basically the issue being reported.

The client only imports blocks to a certain point and then goes to sync with network.  It's either a 2GB file limit for the error or the public bootstrap is broken.
In any case, I've also encountered that the client keeps stopping and has to be restarted, but no indication on the UI.  Only that the bkl0002 stops changing in size.

I've been trying for 2 days now with no less than 20 restarts.
At block 1853826 now.... 18 weeks behind.

The restarts are needed to remove the orphan blocks that are currently in memory, hardcoded to 99 in earlier versions of bitcoin if i remember correctly. To avoid this, try

Code:

maxorphanblocks=<high number here>

in clam.conf

Thanks but I do not think I need to this since I am able to see my clam client is already at 1970000 blocks which is 6 weeks behind and still counting . Is it necessary to do those things you mentioned or I am good to go ?

[criptocambio]

Where can I find this ( calm.conf ) ?

clam.conf is a file in the same folder as your wallet.dat. You make it yourself - it's a regular text file.

Sir I am already done with bootstrap and it makes my wallet sync fast by " importing files " now it's back to "synchronizing with the network and it takes a day now and it is so slow . I thought  bootstrap can go up to 2M blocks now it is just 1.8 M blocks ( approx 19 weeks behind ) is this correct or is there another patch I need to download ?

Well, it's basically the issue being reported.

The client only imports blocks to a certain point and then goes to sync with network.  It's either a 2GB file limit for the error or the public bootstrap is broken.
In any case, I've also encountered that the client keeps stopping and has to be restarted, but no indication on the UI.  Only that the bkl0002 stops changing in size.

I've been trying for 2 days now with no less than 20 restarts.
At block 1853826 now.... 18 weeks behind.

The restarts are needed to remove the orphan blocks that are currently in memory, hardcoded to 99 in earlier versions of bitcoin if i remember correctly. To avoid this, try

Code:

maxorphanblocks=<high number here>

in clam.conf

Thanks but I do not think I need to this since I am able to see my clam client is already at 1970000 blocks which is 6 weeks behind and still counting . Is it necessary to do those things you mentioned or I am good to go ?

Only if you have problems syncing, i think. I use 400 during sync, but remove it completely from config file after that, and it keeps synced without any issues

[Enzo05]

Where can I find this ( calm.conf ) ?

clam.conf is a file in the same folder as your wallet.dat. You make it yourself - it's a regular text file.

Sir I am already done with bootstrap and it makes my wallet sync fast by " importing files " now it's back to "synchronizing with the network and it takes a day now and it is so slow . I thought  bootstrap can go up to 2M blocks now it is just 1.8 M blocks ( approx 19 weeks behind ) is this correct or is there another patch I need to download ?

Well, it's basically the issue being reported.

The client only imports blocks to a certain point and then goes to sync with network.  It's either a 2GB file limit for the error or the public bootstrap is broken.
In any case, I've also encountered that the client keeps stopping and has to be restarted, but no indication on the UI.  Only that the bkl0002 stops changing in size.

I've been trying for 2 days now with no less than 20 restarts.
At block 1853826 now.... 18 weeks behind.

The restarts are needed to remove the orphan blocks that are currently in memory, hardcoded to 99 in earlier versions of bitcoin if i remember correctly. To avoid this, try

Code:

maxorphanblocks=<high number here>

in clam.conf

Thanks but I do not think I need to this since I am able to see my clam client is already at 1970000 blocks which is 6 weeks behind and still counting . Is it necessary to do those things you mentioned or I am good to go ?

Only if you have problems syncing, i think. I use 400 during sync, but remove it completely from config file after that, and it keeps synced without any issues

Apparently I am near to finished it so I guess I do not need to do anything since I'm almost done . It is already @ 2M blocks 3 weeks behind . Yeheey!!! 

[dooglus]

Apparently I am near to finished it so I guess I do not need to do anything since I'm almost done . It is already @ 2M blocks 3 weeks behind . Yeheey!!!  

Yes, so long as it's syncing fast enough for you you don't need the bootstrap.dat file.

My client is still importing the bootstrap.dat I gave it about 24 hours ago. It's at block 1954760 at the moment, which these blk* file sizes:

-rw------- 1 user user 2097155946 May 18 20:10 blk0001.dat
-rw------- 1 user user  304629563 May 19 01:18 blk0002.dat

The sha256 for the first file:

510d0cabb4208d9a545a0e05fab2c0c29c225d699e0601a16b2891facbd2ce98  blk0001.dat

Will report back when the import crashes or finishes.

Edit: it finished:

2018-05-19 03:43:53 ProcessBlock: ACCEPTED
2018-05-19 03:43:53 SetBestChain: new best=fac44401cb18358bb21f44fac9054194b44c610f3c56296e5bdb6eb7c8e2f3fc  height=2027899  trust=678497555062587320383  blocktrust=428714885044844  date=05/12/18 01:36:00
2018-05-19 03:43:53 ProcessBlock: ACCEPTED
2018-05-19 03:43:53 SetBestChain: new best=f09e869c172819e3a57cf7b6e9bf7d30a8278437e46a4404fbbdde3e6fc027e9  height=2027900  trust=678497983558384619095  blocktrust=428495797298712  date=05/12/18 01:37:52
2018-05-19 03:43:53 ProcessBlock: ACCEPTED
2018-05-19 03:43:53 Loaded 73140 blocks from external file in 8423188ms

That's all the blocks:

I made an updated bootstrap.dat file for people having trouble syncing their client.

It goes up to block 2027900 which was staked on Sat May 12 01:37:52 UTC 2018.

I don't know why some people are having trouble importing my bootstrap.dat file. Maybe it doesn't work on Windows? Did anyone try on a proper OS?

[gjhiggins]

I don't know why some people are having trouble importing my bootstrap.dat file. ... Did anyone try on a proper OS?

I will try that with a fresh compilation of master on Ubuntu 17.10 (assuming for the sake of argument that it broadly qualifies as a proper OS)

Cheers

Graham

[dooglus]

I don't know why some people are having trouble importing my bootstrap.dat file. ... Did anyone try on a proper OS?

I will try that with a fresh compilation of master on Ubuntu 17.10 (assuming for the sake of argument that it broadly qualifies as a proper OS)

It's close enough...

I just noticed that the sum of the sizes of my blk* files is *exacly* the size of the bootstrap.dat I imported:


-rw------- 1 user user 2097155946 May 18 20:10 blk0001.dat
-rw------- 1 user user  467920500 May 19 03:43 blk0002.dat
-rw-rw-r-- 1 user user 2565076446 May 18 00:08 bootstrap.dat.old


I still have "connect=0" in the clam.conf, so it hasn't had a chance to find any blocks newer than the ones in the bootstrap.

Edit: it turns out the two blk files put end to end are identical to the bootstrap file:


~/.clam$ head -c 2097155946 bootstrap* | sha256sum
510d0cabb4208d9a545a0e05fab2c0c29c225d699e0601a16b2891facbd2ce98  -
~/.clam$ sha256sum blk*1*
510d0cabb4208d9a545a0e05fab2c0c29c225d699e0601a16b2891facbd2ce98  blk0001.dat
~/.clam$ tail -c 467920500 bootstrap* | sha256sum
a2d30d536d57eab41d930e2f8d753e60d4af83c1d1fe5dad6c7f5c39475b3d42  -
~/.clam$ sha256sum blk*2*
a2d30d536d57eab41d930e2f8d753e60d4af83c1d1fe5dad6c7f5c39475b3d42  blk0002.dat