This folder contains a snapshot of steemd's block_log file.

The last time the block_log was updated is displayed when browsing this folder. As of the time this README was written (18 Jun 2019), the 
block_log was last updated on: 30 Mar 2019

Note: The snapshot is only updated occasionally by hand. if you would like us to update this snapshot, please contact us: https://www.privex.io/contact/

========================================================================================================================================

This file server (files.privex.io) is operated by Privex Inc. https://www.privex.io - it uses our very own self-hosted GeoDNS to 
automatically direct you to the closest file server (we have one in each of these countries: Germany, Finland and Sweden).

If you experience download speed issues when using files.privex.io - try using one of the country-specific servers directly:

 - de1.files.privex.io (Germany, 1gbps dedicated)
 - se1.files.privex.io (Sweden, 10gbps dedicated)
 - fin1.files.privex.io (Finland, 1gbps dedicated)

========================================================================================================================================

Using our snapshots with Steem-in-a-box
---------------------------------------

If you're using Steem-in-a-box (steem-docker) by @someguy123 ( https://github.com/someguy123/steem-docker ) - just use 
the `dlblocks` function, as the Privex file server is the default download source for the block_log. 

It will automatically choose between HTTP and Rsync depending on whether you're downloading the block_log from fresh, 
or resuming/repairing an existing block_log.

    cd ~/steem-docker
    ./run.sh dlblocks
    ./run.sh replay


Manual download (for those not using steem-in-a-box)
----------------------------------------------------


For Ubuntu, you may need to install lz4 using:

    apt update -qy
    apt install -y liblz4-tool


To download this snapshot efficiently, make sure to download over HTTP (not HTTPS), as SSL severely impedes the download speed. 
You should decompress it on the fly with lz4 as below, allowing it to decompress while downloading, instead of after downloading:

    export DATA_DIR='/your/steem/data/witness_node_data_dir'
    cd ${DATA_DIR}/blockchain
    
    # Download the block_log.lz4 and pipe it into lz4, allowing it to be decompressed on-the-fly while it downloads,
    # and outputted uncompressed to the file `block_log`
    curl -fsSL http://files.privex.io/steem/block_log.lz4 -o - | lz4 -d - block_log

    # Replay the Steem blockchain
    steemd --data-dir="$DATA_DIR" --replay
    

If you have a fast connection, and want a guaranteed, corruption-free reliable download, then you should use rsync to download
the uncompressed block_log instead. Rsync can also repair a corrupted block_log, it will download only the pieces required to
make your local block_log match the snapshot on the server, and uses rolling checksums to ensure it matches the server copy.

    export DATA_DIR='/your/steem/data/witness_node_data_dir'
    cd ${DATA_DIR}/blockchain
    
    # Download the block_log using rsync. It will automatically checksum the file as it downloads, ensuring no corruption,
    # and if there's a connection error, it will resume without any issues.
    rsync -av --progress --append-verify rsync://files.privex.io/steem/block_log block_log

    # Replay the Steem blockchain
    steemd --data-dir="$DATA_DIR" --replay