@@ -19,6 +19,10 @@ block-relay-only connections that are currently in use on the network.
1919
2020==Motivation ==
2121
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+
2226Since 2019, software has been deployed[1] which initiates
2327connections on the Bitcoin network and sets the transaction relay field
2428(introduced by BIP 37 and also defined in BIP 60) to false, to prevent
@@ -45,10 +49,15 @@ receive announced addresses instead.
4549
4650This proposal adds a new, optional message that a node can send a peer when
4751initiating 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
4953a current mechanism to negotiate whether addresses should be relayed on a
5054connection, 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.
5261
5362==Specification ==
5463
0 commit comments