History

Alexander Blair 78d4d5ab79 Merge pull request #6094 `236d2a88` blockchain_stats: make it work on pruned blockchains (moneromooo-monero)		2020-02-06 00:30:48 -08:00
..
blockchain_ancestry.cpp	Removed Berkeley DB and db switching logic	2019-09-16 16:18:05 +02:00
blockchain_blackball.cpp	Merge pull request #5878	2019-09-24 10:10:28 -05:00
blockchain_depth.cpp	Removed Berkeley DB and db switching logic	2019-09-16 16:18:05 +02:00
blockchain_export.cpp	Removed Berkeley DB and db switching logic	2019-09-16 16:18:05 +02:00
blockchain_import.cpp	Adding support for hidden (anonymity) txpool	2019-11-02 20:36:03 +00:00
blockchain_prune_known_spent_data.cpp	Removed Berkeley DB and db switching logic	2019-09-16 16:18:05 +02:00
blockchain_prune.cpp	Removed Berkeley DB and db switching logic	2019-09-16 16:18:05 +02:00
blockchain_stats.cpp	blockchain_stats: make it work on pruned blockchains	2019-11-04 15:10:01 +00:00
blockchain_usage.cpp	Removed Berkeley DB and db switching logic	2019-09-16 16:18:05 +02:00
blockchain_utilities.h	utils: Increase max block size for import/export	2019-10-17 19:14:41 -06:00
blocksdat_file.cpp	monerod can now sync from pruned blocks	2019-09-27 00:10:37 +00:00
blocksdat_file.h	monerod can now sync from pruned blocks	2019-09-27 00:10:37 +00: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
CMakeLists.txt	Update 2019 copyright	2019-03-05 22:05:34 +01:00
README.md	Made code block usage consistent across all .md files	2019-05-12 05:16:26 +01: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