History

Riccardo Spagni 313a56a2da Merge pull request #5406 `bea1918a` blockchain_import: error out if preparing to handle blocks fails (moneromooo-monero)		2019-04-16 22:32:27 +02:00
..
CMakeLists.txt	Update 2019 copyright	2019-03-05 22:05:34 +01:00
README.md	Update 2019 copyright	2019-03-05 22:05:34 +01:00
blockchain_ancestry.cpp	Update 2019 copyright	2019-03-05 22:05:34 +01:00
blockchain_blackball.cpp	Update 2019 copyright	2019-03-05 22:05:34 +01:00
blockchain_depth.cpp	Update 2019 copyright	2019-03-05 22:05:34 +01:00
blockchain_export.cpp	Update 2019 copyright	2019-03-05 22:05:34 +01:00
blockchain_import.cpp	blockchain_import: error out if preparing to handle blocks fails	2019-04-07 13:48:19 +00:00
blockchain_prune.cpp	Allow pruning before v10	2019-04-01 14:06:49 +00:00
blockchain_prune_known_spent_data.cpp	Update 2019 copyright	2019-03-05 22:05:34 +01:00
blockchain_stats.cpp	blockchain_stats: fix sign in formatting function	2019-04-01 19:24:47 +00:00
blockchain_usage.cpp	Update 2019 copyright	2019-03-05 22:05:34 +01:00
blockchain_utilities.h	Update 2019 copyright	2019-03-05 22:05:34 +01:00
blocksdat_file.cpp	Update 2019 copyright	2019-03-05 22:05:34 +01:00
blocksdat_file.h	Update 2019 copyright	2019-03-05 22:05:34 +01:00
bootstrap_file.cpp	Make difficulty 128 bit instead of 64 bit	2019-03-24 21:03:19 +00:00
bootstrap_file.h	Make difficulty 128 bit instead of 64 bit	2019-03-24 21:03:19 +00:00
bootstrap_serialization.h	Make difficulty 128 bit instead of 64 bit	2019-03-24 21:03:19 +00:00

README.md

Monero Blockchain Utilities

Introduction

The blockchain utilities allow one to import and export the blockchain.

Usage:

See also each utility's "--help" option.

Export an existing blockchain database

$ monero-blockchain-export

This loads the existing blockchain and exports it to $MONERO_DATA_DIR/export/blockchain.raw

Import the exported file

$ monero-blockchain-import

This imports blocks from $MONERO_DATA_DIR/export/blockchain.raw (exported using the monero-blockchain-export tool as described above) into the current database.

Defaults: --batch on, --batch size 20000, --verify on

Batch size refers to number of blocks and can be adjusted for performance based on available RAM.

Verification should only be turned off if importing from a trusted blockchain.

If you encounter an error like "resizing not supported in batch mode", you can just re-run the monero-blockchain-import command again, and it will restart from where it left off.

## use default settings to import blockchain.raw into database
$ monero-blockchain-import

## fast import with large batch size, database mode "fastest", verification off
$ monero-blockchain-import --batch-size 20000 --database lmdb#fastest --verify off

Import options

--input-file specifies input file path for importing

default: <data-dir>/export/blockchain.raw

--output-file specifies output file path to export to

default: <data-dir>/export/blockchain.raw

--block-stop stop at block number

--database <database type>

--database <database type>#<flag(s)>

database type: lmdb, memory

flags:

The flag after the # is interpreted as a composite mode/flag if there's only one (no comma separated arguments).

The composite mode represents multiple DB flags and support different database types:

safe, fast, fastest

Database-specific flags can be set instead.

LMDB flags (more than one may be specified):

nosync, nometasync, writemap, mapasync, nordahead

Examples:

$ monero-blockchain-import --database lmdb#fastest

$ monero-blockchain-import --database lmdb#nosync

$ monero-blockchain-import --database lmdb#nosync,nometasync