From a631221175eb26dbf48e482849935858023155d0 Mon Sep 17 00:00:00 2001 From: Vishal Menon Date: Fri, 4 Jun 2021 05:00:39 +0530 Subject: [PATCH] Updated cyphernodeconf_docker/help.json --- cyphernodeconf_docker/help.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cyphernodeconf_docker/help.json b/cyphernodeconf_docker/help.json index e42b3a49d..743891f61 100644 --- a/cyphernodeconf_docker/help.json +++ b/cyphernodeconf_docker/help.json @@ -29,7 +29,7 @@ "bitcoin_rpcpassword": "Bitcoin Core's RPC password used by Cyphernode when calling the node.", "bitcoin_prune": "If you don't have at least 350GB of disk space, you should run Bitcoin Core in prune mode. NOTE: when running Bitcoin Core in prune mode, the incoming transactions' fees cannot be computed by Cyphernode and won't be part of the addresses watching's callbacks payload.", "bitcoin_prune_size": "Minimum size is 550. This option specifies the maximum number in MB Bitcoin Core will allocate for raw block & undo data.", - "bitcoin_cbf": "Compact Block Filters have a storage over-head of ~6GB & significant networking overhead while serving CBF to neutrino clients.", + "bitcoin_cbf": "Compact Block Filters serve filtered block data to neutrino clients and have a networking overhead.", "bitcoin_uacomment": "User Agent string used by Bitcoin Core. (Optional)", "bitcoin_datapath": "Path name to where Bitcoin Core's data files (blockchain data, wallets, configs, etc.) are stored. This directory will be mounted into the Bitcoin node's container. If you already have a sync'ed node, you can copy data there to be used by the node, instead of resyncing everything. NOTE: only copy chainstate/ and blocks/ contents. If running on OSX, check mountable directories in Docker's File Sharing configs.", "bitcoin_datapath_custom": " ",