aboutsummaryrefslogtreecommitdiff
path: root/doc/man/bitcoind.1
diff options
context:
space:
mode:
authorWladimir J. van der Laan <laanwj@gmail.com>2019-07-19 19:50:25 +0200
committerWladimir J. van der Laan <laanwj@gmail.com>2019-07-19 19:50:47 +0200
commita6cba19831da9de6c5f968849d07c2a006557fe4 (patch)
tree3bb511e3b8e7807ff393bffd5cebdf9d7ff5f84a /doc/man/bitcoind.1
parentaa2d12a592d48c562190627914cccc7677697d1c (diff)
downloadbitcoin-0.18.1rc1.tar.xz
doc: Update manpages for rc1v0.18.1rc1
Tree-SHA512: 805a6931e2bd059ee2da42634f687828a50b2ccd3a1ac0071cd626e9a2f52b7afc79af3c8f3d5b013a853d5e59068314e744a4694dceef598710f0694babbd99
Diffstat (limited to 'doc/man/bitcoind.1')
-rw-r--r--doc/man/bitcoind.120
1 files changed, 12 insertions, 8 deletions
diff --git a/doc/man/bitcoind.1 b/doc/man/bitcoind.1
index 5aa481784c..7c95a0dc79 100644
--- a/doc/man/bitcoind.1
+++ b/doc/man/bitcoind.1
@@ -1,12 +1,12 @@
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.6.
-.TH BITCOIND "1" "March 2019" "bitcoind v0.18.0.0" "User Commands"
+.TH BITCOIND "1" "July 2019" "bitcoind v0.18.1.0" "User Commands"
.SH NAME
-bitcoind \- manual page for bitcoind v0.18.0.0
+bitcoind \- manual page for bitcoind v0.18.1.0
.SH SYNOPSIS
.B bitcoind
[\fI\,options\/\fR] \fI\,Start Bitcoin Core Daemon\/\fR
.SH DESCRIPTION
-Bitcoin Core Daemon version v0.18.0.0
+Bitcoin Core Daemon version v0.18.1.0
.SH OPTIONS
.HP
\-?
@@ -41,6 +41,11 @@ Extra transactions to keep in memory for compact block reconstructions
.IP
Specify blocks directory (default: <datadir>/blocks)
.HP
+\fB\-blocksonly\fR
+.IP
+Whether to reject transactions from network peers. Transactions from the
+wallet or RPC are not affected. (default: 0)
+.HP
\fB\-conf=\fR<file>
.IP
Specify configuration file. Relative paths will be prefixed by datadir
@@ -292,9 +297,7 @@ Bind to given address and whitelist peers connecting to it. Use
.IP
Whitelist peers connecting from the given IP address (e.g. 1.2.3.4) or
CIDR notated network (e.g. 1.2.3.0/24). Can be specified multiple
-times. Whitelisted peers cannot be DoS banned and their
-transactions are always relayed, even if they are already in the
-mempool, useful e.g. for a gateway
+times. Whitelisted peers cannot be DoS banned
.PP
Wallet options:
.HP
@@ -519,8 +522,9 @@ mining and transaction creation (default: 0.00001)
.HP
\fB\-whitelistforcerelay\fR
.IP
-Force relay of transactions from whitelisted peers even if they violate
-local relay policy (default: 0)
+Force relay of transactions from whitelisted peers even if the
+transactions were already in the mempool or violate local relay
+policy (default: 0)
.HP
\fB\-whitelistrelay\fR
.IP