diff options
| author | Suhas Daftuar <sdaftuar@gmail.com> | 2020-08-07 15:37:03 -0400 |
|---|---|---|
| committer | Suhas Daftuar <sdaftuar@gmail.com> | 2020-08-07 15:37:03 -0400 |
| commit | f319663c04ea5796d6fec706a85f50599e146607 (patch) | |
| tree | 8a2ef9c4acdcd20d3467aa12c5d7482cc6c4b607 /bip-0339.mediawiki | |
| parent | 5909b91b939e9f9f11be7a99d3d1afe49af7d6f5 (diff) | |
BIP339: clarify fetching
A node may always fetch a transactions using the txid.
Diffstat (limited to 'bip-0339.mediawiki')
| -rw-r--r-- | bip-0339.mediawiki | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/bip-0339.mediawiki b/bip-0339.mediawiki index afdfe15..806ba1c 100644 --- a/bip-0339.mediawiki +++ b/bip-0339.mediawiki @@ -43,7 +43,8 @@ announcing and fetching transactions. # The protocol version of nodes implementing this BIP must be set to 70016 or higher. # The wtxidrelay message MUST be sent in response to a version message from a peer whose protocol version is >= 70016 and prior to sending a verack. A wtxidrelay message received after a verack message MUST be ignored or treated as invalid. # A new inv type MSG_WTX (0x00000005) is added, for use in both inv messages and getdata requests, indicating that the hash being referenced is a transaction's wtxid. In the case of getdata requests, MSG_WTX implies that the transaction being requested should be serialized with witness as well, as described in BIP 144. -# After a node has sent and received a wtxidrelay message to/from a given peer, the node is required to use the MSG_WTX inv-type when announcing transactions to that peer, or requesting announced transactions from that peer. +# After a node has received a wtxidrelay message from a peer, the node MUST use the MSG_WTX inv type when announcing transactions to that peer. +# After a node has received a wtxidrelay message from a peer, the node SHOULD use a MSG_WTX getdata message to request any announced transactions. A node MAY still request transactions from that peer using MSG_TX getdata messages, such as for transactions not recently announced by that peer (like the parents of recently announced transactions). ==Backward compatibility== |