7b00cb251b
Snode revisions are a secondary version that let us put out a mandatory
update for snodes that isn't a hardfork (and so isn't mandatory for
wallets/exchanges/etc.).
The main point of this is to let us make a 9.2.0 release that includes
new mandatory minimums of future versions of storage server (2.2.0) and
lokinet (0.9.4) to bring upgrades to the network.
This slightly changes the HF7 blocks to 0 (instead of 1) because,
apparently, we weren't properly checking the HF value of the
pre-first-hf genesis block at all before. (In practice this changes
nothing because genesis blocks are v7 anyway).
This also changes (slightly) how we check for hard forks: now if we skip
some hard forks then we still want to know the height when a hard fork
triggers. For example, if the hf tables contains {7,14} then we still
need to know that the HF14 block height also is the height that
activates HF9, 10, etc.
|
||
|---|---|---|
| .. | ||
| blockchain_ancestry.cpp | ||
| blockchain_blackball.cpp | ||
| blockchain_depth.cpp | ||
| blockchain_export.cpp | ||
| blockchain_import.cpp | ||
| blockchain_objects.h | ||
| 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 | ||
| sn_key_tool.cpp | ||
Oxen Blockchain Utilities
Copyright (c) 2014-2019, The Monero Project Copyright (c) 2018, The Loki 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
$ oxen-blockchain-export
This loads the existing blockchain and exports it to $OXEN_DATA_DIR/export/blockchain.raw
Import the exported file
$ oxen-blockchain-import
This imports blocks from $OXEN_DATA_DIR/export/blockchain.raw (exported using the
oxen-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 oxen-blockchain-import command again, and it will restart from where it left off.
## use default settings to import blockchain.raw into database
$ oxen-blockchain-import
## fast import with large batch size, database mode "fastest", verification off
$ oxen-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:
$ oxen-blockchain-import --database lmdb#fastest
$ oxen-blockchain-import --database lmdb#nosync
$ oxen-blockchain-import --database lmdb#nosync,nometasync