d0s3t3ch/wownero
1
0
Fork 0
mirror of https://git.wownero.com/wownero/wownero.git synced 2024-08-15 01:03:23 +00:00
Code Issues Projects Releases Wiki Activity
wownero/src/blockchain_utilities
History
Riccardo Spagni d855f9bb92
Merge pull request #4901 
a48f2dab blockchain_prune_known_spent_data: blackball file is now optional (moneromooo-monero)
17b45725 Outputs where all amounts are known spent can now be pruned (moneromooo-monero)
2018-12-12 11:57:31 +02:00
..
blockchain_ancestry.cpp blockchain_utilities: simplify getting block blob from height 2018-10-22 16:04:28 +00:00
blockchain_blackball.cpp blockchain_blackball: spot when all outputs of an amount are spent 2018-11-24 11:07:15 +00:00
blockchain_depth.cpp blockchain_utilities: simplify getting block blob from height 2018-10-22 16:04:28 +00:00
blockchain_export.cpp Stagenet 2018-03-05 11:55:05 +09:00
blockchain_import.cpp remove some unused code 2018-11-23 15:37:36 +00:00
blockchain_prune_known_spent_data.cpp blockchain_prune_known_spent_data: blackball file is now optional 2018-11-27 15:45:47 +00:00
blockchain_stats.cpp blockchain_stats: don't use gmtime_r on Windows 2018-11-21 00:50:53 +00:00
blockchain_usage.cpp Merge pull request #3543 2018-05-31 14:36:33 -05:00
blockchain_utilities.h Update 2018 copyright 2018-01-26 10:03:20 -05:00
blocksdat_file.cpp blockchain_export: fix buffer overflow in exporter 2018-02-02 16:11:15 +00:00
blocksdat_file.h Update 2018 copyright 2018-01-26 10:03:20 -05:00
bootstrap_file.cpp blockchain_utilities: fix logs and cout output colliding 2018-10-27 17:40:01 +00:00
bootstrap_file.h Update 2018 copyright 2018-01-26 10:03:20 -05:00
bootstrap_serialization.h v8: per byte fee, pad bulletproofs, fixed 11 ring size 2018-09-11 13:38:07 +00:00
CMakeLists.txt Outputs where all amounts are known spent can now be pruned 2018-11-27 15:45:42 +00:00
README.md Update 2018 copyright 2018-01-26 10:03:20 -05:00

README.md

Monero Blockchain Utilities

Copyright (c) 2014-2018, 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