mirror of
https://github.com/bitcoin/bips.git
synced 2025-01-18 21:35:13 +01:00
Add more language in hope of BIP number assignment
This commit is contained in:
parent
794f20a131
commit
55a31eb8ee
@ -19,6 +19,10 @@ block-relay-only connections that are currently in use on the network.
|
||||
|
||||
==Motivation==
|
||||
|
||||
This proposal is part of an effort to increase the number of inbound
|
||||
connections that a peer can service, by distinguishing peers which will not
|
||||
relay transactions from those that do.
|
||||
|
||||
Since 2019, software has been deployed[1] which initiates
|
||||
connections on the Bitcoin network and sets the transaction relay field
|
||||
(introduced by BIP 37 and also defined in BIP 60) to false, to prevent
|
||||
@ -45,10 +49,15 @@ receive announced addresses instead.
|
||||
|
||||
This proposal adds a new, optional message that a node can send a peer when
|
||||
initiating a connection to that peer, to indicate that connection should not be
|
||||
used for transaction-relay for the connection's lifetime. In addition, without
|
||||
used for transaction relay for the connection's lifetime. In addition, without
|
||||
a current mechanism to negotiate whether addresses should be relayed on a
|
||||
connection, this BIP suggests that address messages not be sent on links where
|
||||
tx-relay has been disabled.
|
||||
transaction relay has been disabled.
|
||||
|
||||
After this BIP is deployed, nodes could more easily implement inbound
|
||||
connection limiting that differentiates low-resource nodes (such as those
|
||||
sending disabletx) from full-relay peers, potentially allowing for an increase
|
||||
in the number of block-relay-only connections that can be made on the network.
|
||||
|
||||
==Specification==
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user