No description
8e5f4262c2This is the initial, experimental implementation of pruning, related to https://github.com/nanocurrency/nano-node/issues/1094. Node ledger pruning is designed to safely discard parts of the ledger. Now ledger size can be reduced from 23.8 GB to 7.5GB after vacuum. And from 18.8 GB to 5.2 GB after database rebuild. Configuration and considerations - This version of ledger pruning is for experimental use only: - Enable optional ledger pruning with node CLI `--debug_prune` for manual pruning & node launch flag `--enable_pruning` for automatic node background actions. - Pruning rules can be configured in [node.experimental] config with “max_pruning_age” (Time in seconds to limit for blocks age after pruning. Also period for automatic node pruning task, default 1 day, 5 minutes for beta network) & “max_pruning_depth” (Limit for full blocks in chain after pruning, default 0 - unlimited). By default all confirmed blocks older than 1 day can be pruned, except genesis block & last confirmed block in each account chain. - Last confirmed block in account chain & all unconfirmed blocks cannot be pruned from ledger. Pruning is relying on confirmation height, so confirmation height reset or too low online_weight_minimum config can cause issues. - Pruned blocks hashes are located in database table “pruned” & can be used by node internally (https://github.com/nanocurrency/nano-node/pull/2946). RPC, CLI and other changes - Several RPC calls are modified to support pruned blocks related to main request block (https://github.com/nanocurrency/nano-node/pull/2977). - RPC “history”: if previous block is pruned, “amount” field is not returned for all blocks, “account” field is not returned for state blocks, also state block type/subtype is “unknown” . If source is pruned, then “account” field is not returned for receive/open legacy & for receive/open state blocks (https://github.com/nanocurrency/nano-node/pull/2977). - Same as above for QT wallet history (https://github.com/nanocurrency/nano-node/pull/2977). - RPC “block_info”/“blocks_info”: if previous block is pruned, “amount” field is not returned. RPC “block_count”: for nodes with enabled pruning returns 2 new fields: “full” blocks & “pruned” blocks. “full” + “pruned” = total “blocks” (https://github.com/nanocurrency/nano-node/pull/2977). - Block count for CLI/RPC/telemetry is sum of full blocks & pruned blocks (https://github.com/nanocurrency/nano-node/pull/2977). - RPC "pruned_exists" to chekc pruned block existence in local database. Other notes - Node is aggressively pruning ledger during initial bootstrap (until hardcoded block count) to limit node disk space usage, pruning config settings are ignored. If you want to avoid this behavior, finish full bootstrap before pruning start. - `--enable_pruning` flag & config option “enable_voting” are mutually exclusive to prevent representatives start with pruned ledger. Pruning is not available for any representatives (https://github.com/nanocurrency/nano-node/pull/2947). - Pruned node can serve as bootstrap server for remaining blocks in ledger (https://github.com/nanocurrency/nano-node/pull/2976). - Multiple internal functions are modified to use pruned blocks in block processor (https://github.com/nanocurrency/nano-node/pull/2974), internal node wallet actions (https://github.com/nanocurrency/nano-node/pull/2992), confirmation height processor (https://github.com/nanocurrency/nano-node/pull/2978) and rep crawler (https://github.com/nanocurrency/nano-node/pull/2975). - Development: consider using ledger safe functions for code with possible pruned blocks (https://github.com/nanocurrency/nano-node/pull/2968). Additional updates being reviewed - Include pruned count in telemetry. - Improve RocksDB pruned block count calculation. Co-authored-by: Wesley Shillingford <650038+wezrule@users.noreply.github.com> Co-authored-by: Guilherme Lawless <guilherme@nano.org> |
||
|---|---|---|
| .github | ||
| api/flatbuffers | ||
| ci | ||
| CL | ||
| cmake/legacyModules | ||
| cpptoml@5399650056 | ||
| crypto | ||
| debian-control | ||
| docker | ||
| etc | ||
| flatbuffers@3b458f7a17 | ||
| gtest@dea0216d0c | ||
| images | ||
| lmdb@e931980823 | ||
| miniupnp@582375b64f | ||
| nano | ||
| nano-pow-server@00591aeae9 | ||
| rocksdb@38e99ec803 | ||
| util | ||
| valgrind | ||
| .clang-format.base | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .gitmodules | ||
| asan_blacklist | ||
| CMakeLists.txt | ||
| doxygen.config | ||
| Info.plist.in | ||
| LICENSE | ||
| logo.png | ||
| Nano.icns | ||
| Nano.ico | ||
| Nano.rc | ||
| nanocurrency-beta.spec.in | ||
| nanocurrency.spec.in | ||
| qt.conf | ||
| README.md | ||
| rep_weights_beta.bin | ||
| rep_weights_live.bin | ||
| resources.qrc | ||
| SECURITY.md | ||
| tsan_clang_blacklist | ||
| tsan_suppressions | ||
| valgrind.supp | ||
What is Nano?
Nano is a digital payment protocol designed to be accessible and lightweight, with a focus on removing inefficiencies present in other cryptocurrencies. With ultrafast transactions and zero fees on a secure, green and decentralized network, this makes Nano ideal for everyday transactions.
Guides & Documentation
Other documentation details can be found at https://docs.nano.org.
Links & Resources
Want to Contribute?
Please see the contributors guide.
Contact us
We want to hear about any trouble, success, delight, or pain you experience when using Nano. Let us know by filing an issue, joining us on Reddit, or joining us on Discord.