Update to 1.10.0

1 files changed, 106 insertions, 0 deletions

diff --git a/fulcrum.conf b/fulcrum.conf
index f99b30370c56..11dd0a09da60 100644
--- a/fulcrum.conf
+++ b/fulcrum.conf
@@ -330,6 +330,14 @@ rpcpassword = hunter1
 #banner = /path/to/banner.txt
 
 
+# Anonymize Client IP addresses and TxIDs in logs - 'anon_logs' - DEFAULT: false
+#
+# If true, client IP addresses and transaction IDs will be hidden from the
+# "normal" log level.  The "debug" or "trace" log levels may still contain this
+# information in some cases.
+#
+#anon_logs = false
+
 
 #-------------------------------------------------------------------------------
 # PEER DISCOVERY AND PUBLIC SERVER OPTIONS
@@ -619,6 +627,22 @@ rpcpassword = hunter1
 #bitcoind-tls = false
 
 
+# Daemon RPC Passthrough - 'daemon_passthrough_subnets' - DEFAULT: (None)
+#
+# Specify a comma-delimited list of subnets for which to allow the RPC method
+# "daemon.passthrough". This RPC method is potentially dangerous for public
+# servers and should only be used for private or trusted networks. It allows
+# clients to directly issue RPC commands to the bitcoin daemon.
+#
+# Clients connecting from one of the subnets specified by this paremeter will
+# be allowed to access this RPC method. The default is that no clients are
+# allowed.
+#
+# Examples: 10.10.2.0/24, 128.0.0.0/8, 123.45./16, 99.74.0.0/16
+#
+#daemon_passthrough_subnets =
+
+
 # Keep RocksDB Log Files - 'db_keep_log_file_num' - DEFAULT: 5
 #
 # The maximum number of database log files to keep around on disk, per database.
@@ -980,3 +1004,85 @@ rpcpassword = hunter1
 # higher than the number of cores on the system.
 #
 #worker_threads = 0   # <--- autodetect to number of cores on the system.
+
+
+# PID file - 'pidfile' - DEFAULT: None
+#
+# If specified, Fulcrum will write its process ID to this file on startup (and
+# the file will be auto-deleted on app-shutdown). Enabling a PID file may be
+# useful for admins wishing to integrate Fulcrum with monitoring software.
+#
+#pidfile = /path/to/fulcrum.pid
+
+
+
+#-------------------------------------------------------------------------------
+# Reusable Payment Address (RPA) Options
+#-------------------------------------------------------------------------------
+
+# Enable RPA indexing - `rpa` - DEFAULT: 1 for BCH, 0 for all other coins
+#
+# Whether or not to enable the BCH-specific "RPA" index.
+#
+# See: https://github.com/imaginaryusername/Reusable_specs/blob/master/reusable_addresses.md
+#
+# This index takes ~42M of space currently on mainnet (but may grow to >3GB as
+# the blockchain advances over time).  If this index is enabled, the
+# `blockchain.rpa.*` and/or the `blockchain.reusable.*` RPC methods will be
+# available to clients, and the `server.features` map will contain an "rpa"
+# key to indicate that the server supports RPA.
+#
+# If unspecified, then the RPA index and associated RPCs will only be enabled
+# for BCH, and will be disabled for all coins.
+#
+#rpa = 1
+
+
+# RPA starting block height - `rpa_start_height` - DEFAULT: 825000 for mainnet
+#                                                           0 all other nets
+#
+# Limit the RPA index to start at this block height. Blocks before this height
+# will not have their data indexed by the RPA index. The default for mainnet is
+# to save space and cycles since before a certain block height, no RPA wallets
+# were in existence anyway since RPA had not yet been invented.
+#
+#rpa_start_height = 825000
+
+
+# RPA history scan block limit - `rpa_history_blocks` - DEFAULT: 60
+#
+# For the `blockchain.rpa.get_history` and/or `blockchain.reusable.get_history`
+# RPC methods, limit the number of blocks that client can request to scan for RPA
+# transactions in a single RPC call to this number of blocks. In other words,
+# results will be truncated if the client requests a wider height range in their
+# request than this number. The reason for this limit is that clients should be
+# making many frequent fast calls to the server so as to maximize the server's
+# ability to multiplex requests (many small requests is better than a few larger
+# ones when it comes to perceived server responsiveness). Specifying this to be
+# a large value (say, >1000) is a potential DoS vector.
+#
+#rpa_history_blocks = 60
+
+
+# RPA maximum history results limit - `rpa_max_history` - DEFAULT: `max_history`
+#
+# This is similar to the configuration option `max_history` (search for it above),
+# but it can be independently specified for the RPA subsystem to be larger or
+# smaller than the app-level `max_history`.  If unspecified, this option will
+# inherit whatever the app-level `max_history` setting is.
+#
+#rpa_max_history = 125000
+
+
+# RPA prefix bits minimum - `rpa_prefix_bits_min` - DEFAULT: 8
+#
+# Affects the minimum "prefix" value that is accepted by the
+# `blockchain.rpa.get_history` RPC method, in terms of number of bits. Specify
+# a value in the range: [4, 16]. This is a low-level configuration variable and
+# the default of 8 should be good for all extant RPA clients. 4 offers a larger
+# anonymity set to clients when they perform queries (as they will get more
+# haystack to their 1 needled they are looking for), but it comes with a
+# performance penalty on the server-side, which is why we set the default
+# minimum to 8 in Fulcrum.
+#
+#rpa_prefix_bits_min = 8