diff --git a/README.md b/README.md
index 5bd300224..5e6209553 100644
--- a/README.md
+++ b/README.md
@@ -2,16 +2,15 @@
[Documentation](https://developers.credits.com/en/Articles/Platform) \|
[Guides](https://developers.credits.com/en/Articles/Guides) \|
-[News](https://credits.com/en/Home/News)
+[CREDITS website](https://credits.com/)
[](https://github.com/CreditsCommunity/node/actions/workflows/build.yml)
[](https://github.com/CreditsCommunity/node/releases/latest)
[](LICENSE)
[](https://twitter.com/intent/follow?screen_name=creditscom)
# Credits Node (community)
-A node is a client-side application that is installed on the user equipment.
-The Node processes and stores transactions, executes and confirms smart contract rules requests processing from third-party systems and provides data when requested.
-Written on C++.
+The node is the program that runs on the operator's machine and takes part in the CREDITS network.
+Written in C++.
## Version
This repository is the community continuation of [CREDITSCOM/node](https://github.com/CREDITSCOM/node), forked from the official release 4.2.532. Community releases are numbered `4.2.532-community.N`. They keep protocol version 532 and stay compatible with the mainnet.
@@ -28,189 +27,101 @@ This repository is the community continuation of [CREDITSCOM/node](https://githu
| Packages (Linux x86-64, Windows x64, macOS Apple Silicon; `config.ini` full and `config.pruned.ini` pruned, one package per system) | [Releases](https://github.com/CreditsCommunity/node/releases) |
| Guided set-up in every package: pruned or full, database, first start, snapshot sharing, contract executor (`csnode/setup.sh` on Linux and macOS, `csnode/setup.bat` on Windows) | [packaging/setup/](packaging/setup/) |
-Replacing the official binaries with the community ones, with the official `config.ini`, keeps the same BerkeleyDB database and the same behaviour on the network. The new features (other block databases, pruned storage, conversion) are opt-in.
-
-
What is Credits Node?
-Credits Node is the main module that provide an opportunity to run a node and participate in CREDITS blockhain network. The node performs processing and storage of transactions, execution and confirmation of the terms of smart contracts, processing requests from third-party systems, and provides data upon request. Each node on the network has the same functionality.
-The node consists of the following elements:
-
-- API
-- Desision-making module(Solver)
-- Storage(CSDB)
-- Transport protocol
-
-
-Build dependencies
-
-- Boost 1.70 or newest static prebuild
-- Compiler with C++17 support
-- Cmake 3.11 or newest
-- Requirements fo building Apache Thrift
-- The building Berkeley DB distribution uses the Free Software Foundation's autoconf and libtool tools to build on UNIX platforms.
-
-
-
-It is necessary to run in the terminal, which sets the environment variables for building a Visual Studio project
-For Windows:
->```sh
->git clone https://github.com/CREDITSCOM/node.git
->cd node
->git submodule update --init --recursive
->mkdir build
->cd build
->cmake -DCMAKE_BUILD_TYPE=Release -A x64 ..
->cmake --build . --target ALL_BUILD --config Release
-
-
-If necessary, full step-by-step instruction for Windows:
-
->```sh
-># Install cmake
-># After install you can try to run in command line version check:
->cmake --version
-># If installation was successful, the result will be like:
->cmake version 3.17.0-rc1
-># Install git, check the version the same way:
->git --version
-># and result result:
->git version 2.33.0.windows.2
-># Install Visual Studio, as result you can rut it
-># FLEX&BISON usually are installed automatically with Visual Studio and are not necessary to install yourself
-># DO NOT TRY TO INSTALL IT SEPARATELY IF IT ISN'T NECESSARY, IT CAN PREVENT YOU FROM CORRECT NODE BUILDING PROCESS
-># Check is made the same way by requesting Software version. System should give the correct answer.
-># Install boost from 1.68.0 to 1.72.0:
->wget -c $https://dl.bintray.com/boostorg/release/1.72.0/source/boost_1_72_0.tar.gz
-># or just load with your browser
-># unzip with any archiver, you prefer and go to directory:
->cd boost_1_72_0
->./bootstrap.sh
->./b2 --build-type=complete link=static threading=multi $runtime-link=static --layout=tagged install --prefix=../boost
-># do not forget to add BOOST_ROOT to your SYSTEM VARIABLES and set the value pointing your BOOST directory C:\boost\boost_1_72_0
-># Check it:
->echo %BOOST_ROOT%
-># Result: boost root variable value
-># and add the directories of boost-root and boost-libs to your SYSTEM PATHS like that:
-># C:\boost\boost_1_72_0
-># C:\boost\boost_1_72_0\stage\lib
-># Now you are ready to get node repository and build it:
->git clone https://github.com/CREDITSCOM/node.git
->cd node
->git submodule update --init --recursive
->mkdir build
->cd build
->cmake -DCMAKE_BUILD_TYPE=Release -A x64 ..
->cmake --build . --target ALL_BUILD --config Release
-
-
-
-For Linux:
->```sh
->git clone https://github.com/CREDITSCOM/node.git
->cd node
->git submodule update --init --recursive
->mkdir build
->cd build
->cmake -DCMAKE_BUILD_TYPE=Release ..
->make -j4
-
-If necessary, full step-by-step instruction for Linux:
-
-Update repos and install required package
->```sh
->sudo apt update
->apt upgrade -y
->sudo apt install build-essential libssl-dev autoconf -y
->sudo apt install flex bison libtool -y
-
-Create build directory
->```sh
->mkdir csbuild
->d csbuild
-
-Update gcc g++ (there is no need to update in version of Ubuntu 20 and later)
->```sh
->sudo apt install gcc-8 g++-8 -y
->sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-8 80 --slave /usr/bin/g++ g++ /usr/bin/g++-8 --slave /usr/bin/gcov gcov /usr/bin/gcov-8
->gcc --version
->gcc (Ubuntu 8.4.0-1ubuntu1~18.04) 8.4.0
->Copyright (C) 2018 Free Software Foundation, Inc.
->This is free software; see the source for copying conditions. There is NO
->warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE
-
-Update cmake to latest version
->```sh
->wget -c https://github.com/Kitware/CMake/releases/download/v3.17.0/cmake-3.17.0.tar.gz
->tar zxfv cmake-3.17.0.tar.gz
->cd cmake-3.17.0
->./bootstrap
->make
->sudo make install
->cd ..
-
-Install boost
->```sh
->wget -c $https://dl.bintray.com/boostorg/release/1.72.0/source/boost_1_72_0.tar.gz
->tar zxfv boost_1_72_0.tar.gz
->cd boost_1_72_0
->./bootstrap.sh
->./b2 --build-type=complete link=static threading=multi $runtime-link=static --layout=tagged install --prefix=../boost
->export PATH=~/csbuild/boost:$PATH
->export BOOST_ROOT=~/csbuild/boost
->cd ..
-
-Build node
->```sh
->git clone https://github.com/CREDITSCOM/node.git
->cd node
->git submodule update --init --recursive
->mkdir build
->cd build
->cmake -DCMAKE_BUILD_TYPE=Release ..
->make -j2
-
-System requirements:
-Minimum system requirements:
-Operating system: Windows® 7 / Windows® 8 / Windows® 10 64-bit (with the last update package)
-Processor (CPU): with frequency of 1 GHz (or faster) with PAE, NX and SSE2 support;
-Memory (RAM): 8 Gb
-HDD: 600Gb
-Internet connection: 3 Mbit/s.
-Recommended system requirements:
-
-Operating system: Windows® 7 / Windows® 8 / Windows® 10 64-bit (with the last update package)
-Processor (CPU): Intel® Core ™ i3 or AMD Phenom ™ X3 8650
-Memory (RAM): 8 Gb
-HDD: 3 Tb
-Internet connection: 5 Mbit/s.
-
-Contribution
-Thank you for considering to help out with the source code! We welcome contributions from anyone on the internet, and are grateful for even the smallest of fixes!
-If you'd like to contribute to Credits Node, please fork, fix, commit and send a pull request for the maintainers to review and merge into the main code base. If you wish to submit more complex changes though, please check up with the core devs first on our Developers portal and Contribution file to ensure those changes are in line with the general philosophy of the project and/or get some early feedback which can make both your efforts much lighter as well as our review and merge procedures quick and simple.
-Please make sure your contributions adhere to our coding guidelines:
-
-- Code must adhere to the Credits coding style
-
-- Pull requests need to be based on and opened against the master branch
-- Commit messages should be prefixed with the package(s) they modify
-
-Resources
-
-CREDITS Website
-
-Documentation
-
-Whitepaper
-
-Technical paper
-
-Developers portal
-
-Community links
- <
-
-
-
-
-
-
-
+Replacing the official binaries with the community ones, with the official `config.ini`, keeps the same BerkeleyDB database and the same behaviour on the network. The new features (other block databases, pruned storage, conversion, snapshots, backfill) are opt-in.
+
+## What is Credits Node?
+Credits Node is the program that runs a node of the CREDITS blockchain network. It processes and
+stores transactions, executes and confirms smart contracts, answers requests from third-party
+systems, and provides data on request. Every node on the network has the same functions. Its main
+parts are:
+
+- the API;
+- the decision-making module (Solver);
+- the storage (CSDB);
+- the transport protocol.
+
+## Running a node
+Most operators do not need to build: download the package for your system from the
+[Releases](https://github.com/CreditsCommunity/node/releases), unpack it and run the guided set-up
+(`csnode/setup.sh` on Linux and macOS, `csnode/setup.bat` on Windows), or use the
+[Docker image](packaging/docker/README.md).
+
+Indicative requirements:
+
+| | Pruned node | Full node |
+|---|---|---|
+| Operating system | Linux x86-64 (glibc 2.31 or later: Ubuntu 20.04, Debian 11 and later), Windows 10 or later (x64), macOS on Apple Silicon | same |
+| CPU | 2 cores | 4 cores or more (the backfill checks signatures on several threads) |
+| Memory | 4 GB (8 GB recommended) | 8 GB |
+| Disk | about 10 GB | about 200 to 250 GB with RocksDB, 400 GB or more with LMDB or BerkeleyDB; an SSD |
+| Network | 3 Mbit/s | 5 Mbit/s or more |
+
+See [docs/storage.md](docs/storage.md) for the storage options.
+
+## Building from source
+The builds that CI runs on every change are the reference:
+[build.yml](.github/workflows/build.yml) (Linux) and
+[build-platforms.yml](.github/workflows/build-platforms.yml) (Windows with Visual Studio 2022,
+macOS on Apple Silicon).
+
+Requirements: CMake 3.12 or later, a C++17 compiler (GCC 13 on Ubuntu 24.04 is what CI uses),
+[Boost 1.83](https://www.boost.org/users/history/version_1_83_0.html) built as static libraries with
+a static runtime, flex, bison, autoconf, automake and libtool (for Apache Thrift and BerkeleyDB).
+
+On Linux (Ubuntu 24.04):
+
+```sh
+sudo apt install build-essential cmake ninja-build flex bison autoconf automake libtool pkg-config
+
+# Boost, static with a static runtime
+curl -sSfLO https://archives.boost.io/release/1.83.0/source/boost_1_83_0.tar.bz2
+tar xjf boost_1_83_0.tar.bz2 && cd boost_1_83_0
+./bootstrap.sh --with-libraries=system,filesystem,program_options,date_time,regex,log,iostreams,thread,serialization,atomic,chrono
+./b2 -j"$(nproc)" variant=release link=static runtime-link=static threading=multi cxxflags=-fPIC \
+ --layout=tagged -sNO_BZIP2=1 -sNO_ZSTD=1 -sNO_LZMA=1 install --prefix="$HOME/boost"
+cd ..
+
+# the node
+git clone https://github.com/CreditsCommunity/node.git
+cd node
+git submodule update --init --recursive
+cmake -S . -B build -G Ninja -DCMAKE_BUILD_TYPE=Release \
+ -DBoost_ROOT="$HOME/boost" -DBoost_NO_SYSTEM_PATHS=ON \
+ -DCMAKE_CXX_FLAGS="-include cstdint -include cstddef" -DWITH_HASKELL=OFF
+cmake --build build -j"$(nproc)"
+```
+
+The binary is `build/client/node`. Add `-DENABLE_TESTS=ON` to build the unit tests, then run
+`ctest --test-dir build`.
+
+## Contribution
+Contributions are welcome. Fork the repository, make your change on a branch and open a pull
+request against `master` of [CreditsCommunity/node](https://github.com/CreditsCommunity/node).
+Please:
+
+- follow the [coding style](codingstyle.md);
+- prefix commit messages with the part they change (`csnode:`, `api:`, `ci:`...);
+- add a line to [docs/CHANGES.md](docs/CHANGES.md);
+- update the guided set-up (`packaging/setup/`) when a change adds or changes a setting an
+ operator chooses.
+
+Every pull request is built and tested on Linux, Windows and macOS.
+
+### Resources
+
+- [CREDITS website](https://credits.com/)
+- [Documentation](https://github.com/CREDITSCOM/Documentation)
+- [Whitepaper](https://github.com/CREDITSCOM/Documentation/blob/master/WhitePaper%20CREDITS%20Eng.pdf)
+- [Technical paper](https://github.com/CREDITSCOM/Documentation/blob/master/TechnicalPaper%20CREDITS%20Eng.pdf)
+- [Developers portal](https://developers.credits.com/)
+
+### Community links
+
+
+
+
+
+
+
+
+
diff --git a/client/config/config.cpp b/client/config/config.cpp
index 76cfaba13..8c3e7a5ee 100644
--- a/client/config/config.cpp
+++ b/client/config/config.cpp
@@ -33,7 +33,7 @@
const NodeVersion NODE_VERSION = 532;
// the community release (4.2.532-community.N); also announced to peers in host_data bits 32-47
-const uint8_t MINOR_NODE_VERSION = 15;
+const uint8_t MINOR_NODE_VERSION = 16;
const std::string BLOCK_NAME_PARAMS = "params";
const std::string BLOCK_NAME_HOST_INPUT = "host_input";
diff --git a/docs/CHANGES.md b/docs/CHANGES.md
index 6d0061b45..316b5a38f 100644
--- a/docs/CHANGES.md
+++ b/docs/CHANGES.md
@@ -40,6 +40,10 @@ lines under the new release.
## Not released yet
+Nothing yet.
+
+## community.16 — 2026-11-03
+
| PR | Change |
|---|---|
| #151 | csnode: every backfill progress line (each 100,000 blocks) is followed by the average cost of a block per phase (verify, store, confirmations), the transactions per block and the share of the processor thread the backfill took |
@@ -47,6 +51,12 @@ lines under the new release.
| #153 | docs: the README links the guided set-up (`packaging/setup/`, `csnode/setup.sh` / `setup.bat` in every package) |
| #154 | packaging: the guided set-up knows the backfill: a full node on lmdb or rocksdb starts from a snapshot by default and is asked whether to fetch the older blocks in the background (`backfill=on/off`, kept when not asked, `backfill_*` keys set by hand kept); a pruned folder can switch to full and fetches the blocks it removed (the set-up used to say a full node from a snapshot holds only the snapshot's blocks and defaulted full nodes to a sync from block 0) |
| #155 | the project moved to the GitHub organisation [CreditsCommunity](https://github.com/CreditsCommunity) (node, p2p, contract-executor, thrift-api-client; the old EnzinoBB addresses redirect): the default snapshot address, the p2p submodule, the workflows, the set-up's executor download, the packages' README and the Docker files use the new addresses; the Docker image is `ghcr.io/creditscommunity/credits-node`, and the release also pushes `ghcr.io/enzinobb/credits-node` for the nodes that still pull it |
+| #156 | docs: the README's broken links (news page, the Boost download from Bintray, the social icons) and outdated information (build steps with Boost 1.70 and GCC 8 cloning the official repository, Windows-only system requirements with 600 GB to 3 TB of disk) are replaced: how to run a node from the packages, indicative requirements for pruned and full nodes on Linux, Windows and macOS, the Linux build CI runs, how to contribute |
+| — | release: the version announced to peers (`MINOR_NODE_VERSION`) is 16; the first release from the CreditsCommunity organisation |
+
+Backfill (#151, #152). The signatures of the fetched blocks are checked on verifier threads: on the
+mainnet test node the backfill went from about 380 to about 980 blocks/s while the share of the
+processor thread it takes fell from 98 % to about 40 %. The guided set-up asks about it (#154).
## community.15 — 2026-11-01
diff --git a/docs/FEATURES.md b/docs/FEATURES.md
index 1fb36376c..2969e2a60 100644
--- a/docs/FEATURES.md
+++ b/docs/FEATURES.md
@@ -6,7 +6,7 @@ consensus with them. This page lists what it adds; each item links the pull requ
The full list of changes is in [CHANGES.md](CHANGES.md), the operational details in
[differences.md](differences.md).
-Everything listed here is in release 4.2.532-community.15 or earlier.
+Everything listed here is in release 4.2.532-community.16 or earlier.
## Storage
@@ -32,9 +32,10 @@ Everything listed here is in release 4.2.532-community.15 or earlier.
- **A full node in minutes, the history in the background.** A full node on lmdb or rocksdb starts
from the snapshot and then fetches the older blocks from its neighbours down to block 0, checking
each against the hash chain and its signatures; the API serves every block and history as it
- arrives. Consensus comes first: the backfill gets a bounded share of the processor thread, less
- while the node is a confidant. A pruned node switched to full fetches what it pruned the same way.
- [#122](https://github.com/CreditsCommunity/node/pull/122), [#123](https://github.com/CreditsCommunity/node/pull/123), [#125](https://github.com/CreditsCommunity/node/pull/125), [#129](https://github.com/CreditsCommunity/node/pull/129), [#130](https://github.com/CreditsCommunity/node/pull/130), [#133](https://github.com/CreditsCommunity/node/pull/133), [#140](https://github.com/CreditsCommunity/node/pull/140), [#145](https://github.com/CreditsCommunity/node/pull/145), [#146](https://github.com/CreditsCommunity/node/pull/146), [#147](https://github.com/CreditsCommunity/node/pull/147)
+ arrives. Consensus comes first: the signatures are checked on verifier threads and the storing
+ gets a bounded share of the processor thread, less while the node is a confidant (about 1,000
+ blocks/s on mainnet). A pruned node switched to full fetches what it pruned the same way.
+ [#122](https://github.com/CreditsCommunity/node/pull/122), [#123](https://github.com/CreditsCommunity/node/pull/123), [#125](https://github.com/CreditsCommunity/node/pull/125), [#129](https://github.com/CreditsCommunity/node/pull/129), [#130](https://github.com/CreditsCommunity/node/pull/130), [#133](https://github.com/CreditsCommunity/node/pull/133), [#140](https://github.com/CreditsCommunity/node/pull/140), [#145](https://github.com/CreditsCommunity/node/pull/145), [#146](https://github.com/CreditsCommunity/node/pull/146), [#147](https://github.com/CreditsCommunity/node/pull/147), [#148](https://github.com/CreditsCommunity/node/pull/148), [#151](https://github.com/CreditsCommunity/node/pull/151), [#152](https://github.com/CreditsCommunity/node/pull/152)
## Starting a node in minutes: snapshots
@@ -156,8 +157,9 @@ limits in the p2p layer (a fork of the p2p library), and two races in the cache
- **Drop-in upgrade.** An official node's folder upgrades to the community node and back.
[#43](https://github.com/CreditsCommunity/node/pull/43), [#44](https://github.com/CreditsCommunity/node/pull/44)
- **Guided set-up** in every package (`setup.sh`, `setup.bat`): pruned or full, database, how the
- first start gets the chain, snapshot sharing and the contract executor.
- [#131](https://github.com/CreditsCommunity/node/pull/131)
+ first start gets the chain, the history of a full node (backfill), snapshot sharing and the
+ contract executor.
+ [#131](https://github.com/CreditsCommunity/node/pull/131), [#154](https://github.com/CreditsCommunity/node/pull/154)
## Tested on every change
diff --git a/docs/storage.md b/docs/storage.md
index 1584a967c..0ada4feab 100644
--- a/docs/storage.md
+++ b/docs/storage.md
@@ -84,11 +84,11 @@ transaction lookups and wallet histories grow downwards while the node runs, wit
restart.
- **By default a full node started from a snapshot fetches the whole history to disk.** On mainnet
- that is about 186 million blocks: about five days (measured on mainnet: 300 to 450 blocks/s while
- the node is not a confidant, less while it is, since consensus comes first; see
- `backfill_idle_turn_budget_ms`), and the disk of a full node, about 400 GB with lmdb or
- berkeleydb, about 130 GB with rocksdb (the recent blocks take about 1.3 KB each in rocksdb: keep
- room to spare). Set `backfill=off` to keep only the blocks of the snapshot.
+ that is about 186 million blocks: about two to three days (measured on mainnet: about 1,000
+ blocks/s, the `backfill_rate` default, with the signatures checked on verifier threads; slower on
+ a node with few cores or a slow disk), and the disk of a full node: 400 GB or more with lmdb or
+ berkeleydb, about 200 to 250 GB with rocksdb (measured: 128 GB, transaction index included, for
+ the newest 75 million blocks; keep room to spare). Set `backfill=off` to keep only the blocks of the snapshot.
- Requests go out only while the node is in sync (not syncing forward, not in a bootstrap round,
not fetching a snapshot); a trusted node keeps fetching, at most `backfill_store_per_turn` blocks
per turn of the thread that also runs consensus.
diff --git a/packaging/docker/README.md b/packaging/docker/README.md
index fd6dc18f4..ff109a8a4 100644
--- a/packaging/docker/README.md
+++ b/packaging/docker/README.md
@@ -9,7 +9,7 @@ docker compose up -d && docker compose logs -f
A pruned node (the default) starts from a snapshot instead of syncing from block 0 for days. On its first start, with `CREDITS_SNAPSHOT=github` (the default), the container runs `node --download-snapshot`: it downloads the latest snapshot published on GitHub, checks every file against its signed manifest and restores it. When that fails, the node looks for a snapshot among its p2p neighbours (the community nodes that serve one) and, after `fetch_wait` (10 minutes) without one, syncs from block 0. `CREDITS_SNAPSHOT=p2p` skips the GitHub download, `off` syncs from block 0. The node checks a restored snapshot's state digest at its first start and stops if it differs.
-A full node on lmdb or rocksdb (`CREDITS_STORAGE=full`, `CREDITS_DB_BACKEND=lmdb` or `rocksdb`) starts from the snapshot the same way. Then it fetches the older blocks from its neighbours in the background, down to block 0 (backward sync). It takes part in the network meanwhile, and the API serves each block and history as it arrives. On mainnet that is about 186 million blocks: about five days, and the disk of a full node, about 400 GB with lmdb or 130 GB with rocksdb. `CREDITS_BACKFILL=off` keeps only the snapshot's blocks. A full node on berkeleydb (the full default) syncs from block 0, as the official node does: a berkeleydb database cannot start above block 0. See `docs/storage.md`, "Backward sync".
+A full node on lmdb or rocksdb (`CREDITS_STORAGE=full`, `CREDITS_DB_BACKEND=lmdb` or `rocksdb`) starts from the snapshot the same way. Then it fetches the older blocks from its neighbours in the background, down to block 0 (backward sync). It takes part in the network meanwhile, and the API serves each block and history as it arrives. On mainnet that is about 186 million blocks: about two to three days, and the disk of a full node, 400 GB or more with lmdb or about 200 to 250 GB with rocksdb. `CREDITS_BACKFILL=off` keeps only the snapshot's blocks. A full node on berkeleydb (the full default) syncs from block 0, as the official node does: a berkeleydb database cannot start above block 0. See `docs/storage.md`, "Backward sync".
The node also serves its own snapshots to its neighbours (`CREDITS_SERVE_SNAPSHOT=on`, the default; at most 2 MB/s, half while it is a confidant). See `docs/snapshots.md`.
diff --git a/packaging/make-package.sh b/packaging/make-package.sh
index 02f9148bb..f07dba0f5 100755
--- a/packaging/make-package.sh
+++ b/packaging/make-package.sh
@@ -135,8 +135,8 @@ Start: cd csnode && $start (full storage, as th
A pruned node can start from the published snapshot: $start --config-file config.pruned.ini --download-snapshot
A full node can too, on lmdb or rocksdb: set db_backend=lmdb (or rocksdb) in the [storage] section
of config.ini, run $start --download-snapshot, then start it. It fetches the older blocks from its
- neighbours in the background down to block 0 (backward sync: about five days and 400 GB with lmdb,
- 130 GB with rocksdb, on mainnet; [storage] backfill=off keeps only the snapshot's blocks). A
+ neighbours in the background down to block 0 (backward sync: about two to three days and 400 GB or more with lmdb,
+ 200 to 250 GB with rocksdb, on mainnet; [storage] backfill=off keeps only the snapshot's blocks). A
pruned node switched to full (prune_keep_blocks=0) fetches the blocks it pruned the same way.
https://github.com/CreditsCommunity/node/blob/master/docs/storage.md#a-full-node-from-a-snapshot
EOF