6556c33f13
|
||
---|---|---|
.. | ||
blockchain_ancestry.cpp | ||
blockchain_blackball.cpp | ||
blockchain_depth.cpp | ||
blockchain_export.cpp | ||
blockchain_import.cpp | ||
blockchain_prune.cpp | ||
blockchain_prune_known_spent_data.cpp | ||
blockchain_stats.cpp | ||
blockchain_usage.cpp | ||
blockchain_utilities.h | ||
blocksdat_file.cpp | ||
blocksdat_file.h | ||
bootstrap_file.cpp | ||
bootstrap_file.h | ||
bootstrap_serialization.h | ||
CMakeLists.txt | ||
README.md |
Monero Blockchain Utilities
Copyright (c) 2014-2020, The Monero Project
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