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

[BayAreaCoins]

zazarb,  Are you still running your little exchange service and buying CLAMS for fiat?

I have 1350 CLAMS that I need to sell for fiat if at all possible. (wire or check)

[1632021542]

1632021542

[1632021542]

1632021542

[zazarb]

any solution why wallet not imported  full bootstrap?

Did the bootstrap.dat file get renamed to bootstrap.dat.old? That's what happens when the client has finished importing blocks from it.

Yes, it's already renamed and wallet starts synchronizing with network, although still in Nov. 2017(now, after  week of sync reached 12 Jan.2018)

Appears you downloaded an older bootstrap.
Seems, from the post, that the file is now up to:  Sat May 12 01:37:52 UTC 2018

In any case, you're almost done.

I thought so too, but I downloaded it after this dooglus post https://bitcointalk.org/index.php?topic=623147.msg36115160#msg36115160
and reaped it after week again, but no change, also file same size as mentioned dooglus.
With such sync speed I need yet months to be done

zazarb,  Are you still running your little exchange service and buying CLAMS for fiat?

I have 1350 CLAMS that I need to sell for fiat if at all possible. (wire or check)

Sorry, I did it only via pp, but at moment out off stock even with this option.

[Michail1]

Appears you downloaded an older bootstrap.
Seems, from the post, that the file is now up to:  Sat May 12 01:37:52 UTC 2018

In any case, you're almost done.

I thought so too, but I downloaded it after this dooglus post https://bitcointalk.org/index.php?topic=623147.msg36115160#msg36115160
and reaped it after week again, but no change, also file same size as mentioned dooglus.
With such sync speed I need yet months to be done

So, it's taking you a week in syncing from the bootstrap file which was only 2 weeks ago?
Yes, you definately have a problem.

BUT... you said you see the file is the same size.  This doesn't mean anything if the file is corrupt.  A corrupt file is a corrupt file no matter how big/small the file is.
Did you check the checksum / the current file is:

To verify that you have the right file:

$ sha256sum bootstrap.dat
713b93b7458e88500f1e32557f0bc58b9f05a6b13e1de31576f25f5300184c96  bootstrap.dat

and/or force your torrent client to check it.

[BayAreaCoins]

zazarb,  Are you still running your little exchange service and buying CLAMS for fiat?

I have 1350 CLAMS that I need to sell for fiat if at all possible. (wire or check)

Sorry, I did it only via pp, but at moment out off stock even with this option.

Ah, ok!

Also, there is a good chance that the new CLAM wallet will come out this week (70% ish) and the new wallet won't require the bootstrap to sync.

[Enzo05]

Boss I am already at 352172 block and it says " 3 years and 11 weeks behind " What bootstrap I need to do ? To make sync fast . Please help Boss .

Enzo,
The OP (first post) has a link to Dooglus post on Bootstrap.
Read it here...   https://bitcointalk.org/index.php?topic=623147.msg9772191#msg9772191

Thanks. That's what I would have said if I was here to reply.

Thanks I am now downloading it . I hope this run smooth and works fine because I really want to do staking with clams .

Edit : I already download it but is this correct ? I paste the bootstrap here and restart client ?



 





I also didn't see this : "  If you are using the QT client, it will say "importing blocks" in the lower left corner while the bootstrap.dat file is imported. That is how you can tell that the file is being used. "




Please help me !

[Michail1]

Boss I am already at 352172 block and it says " 3 years and 11 weeks behind " What bootstrap I need to do ? To make sync fast . Please help Boss .

Enzo,
The OP (first post) has a link to Dooglus post on Bootstrap.
Read it here...   https://bitcointalk.org/index.php?topic=623147.msg9772191#msg9772191

Thanks. That's what I would have said if I was here to reply.

Thanks I am now downloading it . I hope this run smooth and works fine because I really want to do staking with clams .

Edit : I already download it but is this correct ? I paste the bootstrap here and restart client ?


(deleted directory image to save space)


I also didn't see this : "  If you are using the QT client, it will say "importing blocks" in the lower left corner while the bootstrap.dat file is imported. That is how you can tell that the file is being used. "




Please help me !

No....
"Download it, put it into the same folder as your CLAM wallet.dat, then restart the client."

That image is of your executable folder.  Your wallet.dat file is in:      
C:\Users\(youruserdirectory)\AppData\Roaming\Clam
or
%appdata%/clam

(For the above, I am assuming you are using defaults since you don't know where your wallet.dat file is.)

[Enzo05]

Boss I am already at 352172 block and it says " 3 years and 11 weeks behind " What bootstrap I need to do ? To make sync fast . Please help Boss .

Enzo,
The OP (first post) has a link to Dooglus post on Bootstrap.
Read it here...   https://bitcointalk.org/index.php?topic=623147.msg9772191#msg9772191

Thanks. That's what I would have said if I was here to reply.

Thanks I am now downloading it . I hope this run smooth and works fine because I really want to do staking with clams .

Edit : I already download it but is this correct ? I paste the bootstrap here and restart client ?


(deleted directory image to save space)


I also didn't see this : "  If you are using the QT client, it will say "importing blocks" in the lower left corner while the bootstrap.dat file is imported. That is how you can tell that the file is being used. "




Please help me !

No....
"Download it, put it into the same folder as your CLAM wallet.dat, then restart the client."

That image is of your executable folder.  Your wallet.dat file is in:      
C:\Users\(youruserdirectory)\AppData\Roaming\Clam
or
%appdata%/clam

(For the above, I am assuming you are using defaults since you don't know where your wallet.dat file is.)

Oh God It is now working I guess since I am able to see like  ( "IMPORTING BLOCKS")  . I am so thankful to you and people who helped me with this . My first time to do staking thanks for explaining it .

[Michail1]

Oh God It is now working I guess since I am able to see like  ( "IMPORTING BLOCKS")  . I am so thankful to you and people who helped me with this . My first time to do staking thanks for explaining it .

Nice!    All good.   Hopefully your download is good and everything works out. 

[BayAreaCoins]

I'm looking to sell $2500-$5000 worth of CLAM for a USA wire transfer if anyone is interested.

sold

[Enzo05]

Oh God It is now working I guess since I am able to see like  ( "IMPORTING BLOCKS")  . I am so thankful to you and people who helped me with this . My first time to do staking thanks for explaining it .

Nice!    All good.   Hopefully your download is good and everything works out. 

Yeah and it seems faster than previous client that I have but for me It is not that fast it takes time for importing files ? Can you tell me estimation days ?

[dooglus]

I thought so too, but I downloaded it after this dooglus post https://bitcointalk.org/index.php?topic=623147.msg36115160#msg36115160
and reaped it after week again, but no change, also file same size as mentioned dooglus.
With such sync speed I need yet months to be done

I don't understand what happened, but I would suggest stopping your client, renaming bootstrap.dat.old back to bootstrap.dat and starting the client again. It will re-read the bootstrap.dat file skipping the blocks it already has and importing the ones it doesn't have. That might work for you, but I'm not sure. I don't know why it didn't import all the blocks the first time through.

Could you show the size of your bootstrap.dat file and the size of any blk* files you have too?

For example, I have:

-rw------- 1 user user 2097152626 Oct 31  2017 blk0001.dat
-rw------- 1 user user  496629018 May 15 02:45 blk0002.dat
-rw-rw-r-- 1 user user 2565076446 May 12 03:46 bootstrap.dat

The sum of the sizes of the blk* files should be about the same as the size of the bootstrap.dat it imported from.

[dooglus]

Yeah and it seems faster than previous client that I have but for me It is not that fast it takes time for importing files ? Can you tell me estimation days ?

I seem to remember that the import goes slower at the start (because the block hash was using a slow algorithm (maybe scrypt?) for the first 203500 blocks). So it should speed up once you get past those early blocks. The faster blocks started on Tue Nov 11 2014.

[Michail1]

Yeah and it seems faster than previous client that I have but for me It is not that fast it takes time for importing files ? Can you tell me estimation days ?

I seem to remember that the import goes slower at the start (because the block hash was using a slow algorithm (maybe scrypt?) for the first 203500 blocks). So it should speed up once you get past those early blocks. The faster blocks started on Tue Nov 11 2014.

Could also be using a mechanic drive (slow hard drive vs SSD), etc.   Glad it's a lot faster though that before.

[zazarb]

I thought so too, but I downloaded it after this dooglus post https://bitcointalk.org/index.php?topic=623147.msg36115160#msg36115160
and reaped it after week again, but no change, also file same size as mentioned dooglus.
With such sync speed I need yet months to be done

I don't understand what happened, but I would suggest stopping your client, renaming bootstrap.dat.old back to bootstrap.dat and starting the client again. It will re-read the bootstrap.dat file skipping the blocks it already has and importing the ones it doesn't have. That might work for you, but I'm not sure. I don't know why it didn't import all the blocks the first time through.

Could you show the size of your bootstrap.dat file and the size of any blk* files you have too?

For example, I have:

-rw------- 1 user user 2097152626 Oct 31  2017 blk0001.dat
-rw------- 1 user user  496629018 May 15 02:45 blk0002.dat
-rw-rw-r-- 1 user user 2565076446 May 12 03:46 bootstrap.dat

The sum of the sizes of the blk* files should be about the same as the size of the bootstrap.dat it imported from.

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 )

[Michail1]

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.

To verify that you have the right file:

$ 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

[Enzo05]

Yeah and it seems faster than previous client that I have but for me It is not that fast it takes time for importing files ? Can you tell me estimation days ?

I seem to remember that the import goes slower at the start (because the block hash was using a slow algorithm (maybe scrypt?) for the first 203500 blocks). So it should speed up once you get past those early blocks. The faster blocks started on Tue Nov 11 2014.

Oh ok not a problem so now I am already at 1,400,000 blocks you said 203500 blocks only or it is 2035000 ? because I already passed it if its 203500 blocks only .

[zazarb]

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.

To verify that you have the right file:

$ 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)

[dooglus]

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

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.

[dooglus]

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)

What does the first size refer to, if not size on disk? Where else does the file exist other than "on disk"? I guess the "on disk" figure could be rounded up to the next 4k boundary or something (it's a multiple of 4096).

I've no idea why the import isn't working for you. I've not heard of anyone else having that problem. I hope the bootstrap.dat file isn't corrupted. Did anyone else try using it recently? If so, how did it go?

[Michail1]

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)

What does the first size refer to, if not size on disk? Where else does the file exist other than "on disk"? I guess the "on disk" figure could be rounded up to the next 4k boundary or something (it's a multiple of 4096).

I've no idea why the import isn't working for you. I've not heard of anyone else having that problem. I hope the bootstrap.dat file isn't corrupted. Did anyone else try using it recently? If so, how did it go?

He means that in Windows, when you right click a file, it shows both.

Like....


File should be:

CRC32: A09CCD73
MD5: E6F9D182A072ABD9E63E9547B1197A3B
SHA-1: 9DBF6DE14B518094523E0E7DCD78B3358385775E
SHA-256: 713B93B7458E88500F1E32557F0BC58B9F05A6B13E1DE31576F25F5300184C96

Takes under an hour to download.

Client is importing blocks now.  Will be done by morning. 
On my laptop, it's at 30% after 3 hours.

Nite.