@@ -19,6 +19,10 @@ block-relay-only connections that are currently in use on the network.
19
19
20
20
==Motivation ==
21
21
22
+ This proposal is part of an effort to increase the number of inbound
23
+ connections that a peer can service, by distinguishing peers which will not
24
+ relay transactions from those that do.
25
+
22
26
Since 2019, software has been deployed[1] which initiates
23
27
connections on the Bitcoin network and sets the transaction relay field
24
28
(introduced by BIP 37 and also defined in BIP 60) to false, to prevent
@@ -45,10 +49,15 @@ receive announced addresses instead.
45
49
46
50
This proposal adds a new, optional message that a node can send a peer when
47
51
initiating a connection to that peer, to indicate that connection should not be
48
- used for transaction- relay for the connection's lifetime. In addition, without
52
+ used for transaction relay for the connection's lifetime. In addition, without
49
53
a current mechanism to negotiate whether addresses should be relayed on a
50
54
connection, this BIP suggests that address messages not be sent on links where
51
- tx-relay has been disabled.
55
+ transaction relay has been disabled.
56
+
57
+ After this BIP is deployed, nodes could more easily implement inbound
58
+ connection limiting that differentiates low-resource nodes (such as those
59
+ sending disabletx) from full-relay peers, potentially allowing for an increase
60
+ in the number of block-relay-only connections that can be made on the network.
52
61
53
62
==Specification ==
54
63
0 commit comments