Post
Topic
Board Announcements (Altcoins)
Re: [ANN][CLAM] CLAMs, Proof-Of-Chain, Proof-Of-Working-Stake, a.k.a. "Clamcoin"
by
zazarb
on 15/05/2018, 23:46:14 UTC

I did it twice adding new downloaded bootstrap, but always ends with same result. And importing of files switched to sync when the sum of the sizes of the blk* files reach ~2GB( bootstrap.dat.old have 2.37)

Yesterday I download newest bootstrap 2,38 GB (2 565 076 446 ) after adding in clam directory and launch client, importing blocks lasted few minute, than again switched to sync, although I am still  in 26th January.

blk0001- 1,95 GB (2 097 155 946 bytes
blk0002- 195 MB (204 685 437 bytes)
bootstrap.dat.old - 2,38 GB (2 565 076 446 )


I'll bite.
Did you check the checksum? Seems that is a step being ignored, or I missed your response.

Quote
To verify that you have the right file:

Quote
$ sha256sum bootstrap.dat
713b93b7458e88500f1e32557f0bc58b9f05a6b13e1de31576f25f5300184c96  bootstrap.dat

and/or force your torrent client to check it.

Note:  Your blk1 and blk2 should att up to the bootstrap file which is 2.38.   It doesn't.   So, either your bootstrap is corrupt, or your blk files are corrupt if if you now have a corrected (redownloaded bootstrap file).

Step 1 - confirm the checksum is correct on the bootstrap.  
Step 2 - if you pass step 1, then delete the two blk files and let it rerun on the blk files.

PS.  Pay attention to the file sizes.  A confirmed one is:  2097152626  whereas yours is: 2097155946



I check checksum, it's correct(at least last bootstrap)
blk1&2 files I already have deleted several time with older bootstrap, since already I am in block of 4th Feb , in event of bad scenario, I don't want risk again start sync since Nov. 2017

regarding file size
I see -size 1,95 GB (2 097 155 946 bytes) and size on disk 1,95 GB (2 097 156 096 bytes)