snapsnapdown is a Snapchain Snapshot Downloader.

I wrote it because I had some issues when I was setting up my node.

It gives you more flexibility than the embedded downloader:

- You can stop/start and it will pick up where you left.

- When restarting, local chunk sizes will be compared to remote, and if they do not match they will be re-downloaded

- Concurrent chunk downloads: I have found that sometimes a chunk may download at very low speeds, having concurrent downloads removes the bottleneck and results in faster overall download.

- Downloaded chunks are not automatically deleted.

- It looks nicer :-)

snapsnapdown is a Snapchain Snapshot Downloader.

I wrote it because I had some issues when I was setting up my node.

It gives you more flexibility than the embedded downloader:

- You can stop/start and it will pick up where you left.

- When restarting, local chunk sizes will be compared to remote, and if they do not match they will be re-downloaded

- Concurrent chunk downloads: I have found that sometimes a chunk may download at very low speeds, having concurrent downloads removes the bottleneck and results in faster overall download.

- Downloaded chunks are not automatically deleted.

- It looks nicer :-)

https://github.com/vrypan/snapsnapdown

Dad, geek, conversation liquidity provider. vrypan.net (home), @l--o--l (fun). devcoin:$lemon3

Really nice, ty!

Does it know how to extract the chunks?

There is an extract subcommand, but it's very rough. The README has details on how to do it with tar.

Kind of. I basically want to know if it’s possible to extract any messages from any single chunk on its own

Does this help? https://github.com/vrypan/snapsnapdown/blob/main/lowlevel-details.md

Tar archives are read serially, so if you have downloaded chunks 1,2,3 of 10, you can do `cat chunk* | tar xvzf -` and extract what you can extract and tar will panic at the end when it encounters an unexpected end.

Do you know if it’s possible to read the rocksdb output if it hasn’t completed syncing yet?