oxen-core/src/blockchain_utilities
Jason Rhinelander 7b00cb251b Add snode revision soft forks & drop hard fork voting code
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.
2021-06-19 15:13:57 -03:00
..
blockchain_ancestry.cpp rebrand lns -> ons 2021-04-12 10:27:57 +10:00
blockchain_blackball.cpp shorten wire names 2021-02-09 11:54:27 +11:00
blockchain_depth.cpp rebrand lns -> ons 2021-04-12 10:27:57 +10:00
blockchain_export.cpp shorten wire names 2021-02-09 11:54:27 +11:00
blockchain_import.cpp Add snode revision soft forks & drop hard fork voting code 2021-06-19 15:13:57 -03:00
blockchain_objects.h initial loki -> oxen pass 2021-01-04 11:09:45 +11:00
blockchain_prune.cpp rebrand lns -> ons 2021-04-12 10:27:57 +10:00
blockchain_prune_known_spent_data.cpp rebrand lns -> ons 2021-04-12 10:27:57 +10:00
blockchain_stats.cpp rebrand lns -> ons 2021-04-12 10:27:57 +10:00
blockchain_usage.cpp rebrand lns -> ons 2021-04-12 10:27:57 +10:00
blockchain_utilities.h utils: Increase max block size for import/export 2019-10-17 19:14:41 -06:00
blocksdat_file.cpp executable names changed 2021-01-04 14:19:42 +11:00
blocksdat_file.h std::filesystem 2020-10-24 12:45:37 -03:00
bootstrap_file.cpp executable names changed 2021-01-04 14:19:42 +11:00
bootstrap_file.h std::filesystem 2020-10-24 12:45:37 -03:00
bootstrap_serialization.h Update monero copyright to 2019 pre-emptively to make merge simpler 2019-04-12 14:36:43 +10:00
CMakeLists.txt Rename lokimq -> oxenmq 2021-01-14 19:35:00 -04:00
README.md executable names changed 2021-01-04 14:19:42 +11:00
sn_key_tool.cpp Add warning if restoring an ed25519 key to a file name .../key 2021-04-20 00:27:48 -03:00

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