bitcoin/bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-05-12 12:03:29 +00:00
Code Issues Releases Wiki Activity

BIP15,20: add missing words (#1822)

Browse Source 
* Update bip-0015.mediawiki

* Update bip-0020.mediawiki

* Update bip-0035.mediawiki
This commit is contained in:
FT 2025-04-12 16:55:08 +02:00 committed by GitHub
parent 1447ab990d
commit 8375f71ee6
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
bip-0015.mediawiki
View File

@ -12,7 +12,7 @@
[[bip-0070.mediawiki|BIP 0070]] (payment protocol) may be seen as the alternative to Aliases. [[bip-0070.mediawiki|BIP 0070]] (payment protocol) may be seen as the alternative to Aliases.
Using vanilla bitcoin, to send funds to a destination, an address in the form 1Hd44nkJfNAcPJeZyrGC5sKJS1TzgmCTjjZ is needed. The problem with using addresses is they are not easy to remember. An analogy can be thought if one were required to enter the IP address of their favourite websites if domain names did not exist. Using vanilla bitcoin, to send funds to a destination, an address in the form 1Hd44nkJfNAcPJeZyrGC5sKJS1TzgmCTjjZ is needed. The problem with using addresses is that they are not easy to remember. An analogy can be thought if one were required to enter the IP address of their favourite websites if domain names did not exist.
This document aims to layout through careful argument, a bitcoin alias system. This is a big modification to the protocol that is not easily changed in the future and has big ramifications. There is impetus in getting it correct the first time. Aliases have to be robust and secure. This document aims to layout through careful argument, a bitcoin alias system. This is a big modification to the protocol that is not easily changed in the future and has big ramifications. There is impetus in getting it correct the first time. Aliases have to be robust and secure.

2
bip-0020.mediawiki
View File

@ -54,7 +54,7 @@ Graphical bitcoin clients SHOULD register themselves as the handler for the "bit
*label: Label for that address (e.g. name of receiver) *label: Label for that address (e.g. name of receiver)
*address: bitcoin address *address: bitcoin address
*message: message that shown to the user after scanning the QR code *message: message that is shown to the user after scanning the QR code
*size: amount of base bitcoin units ([[#Transfer amount/size|see below]]) *size: amount of base bitcoin units ([[#Transfer amount/size|see below]])
*send: used to send bitcoin, rather than to request them *send: used to send bitcoin, rather than to request them
*(others): optional, for future extensions *(others): optional, for future extensions

2
bip-0035.mediawiki
View File

@ -24,7 +24,7 @@ Several use cases make it desirable to expose a network node's transaction memor
==Specification== ==Specification==
# The mempool message is defined as an empty message where pchCommand == "mempool" # The mempool message is defined as an empty message where pchCommand == "mempool"
# Upon receipt of a "mempool" message, the node will respond with an "inv" message containing MSG_TX hashes of all the transactions in the node's transaction memory pool, if any. # Upon receipt of a "mempool" message, the node will respond with an "inv" message containing MSG_TX hashes of all the transactions in the node's transaction memory pool, if any.
# The typical node behavior in response to an "inv" is "getdata". However, the reference Satoshi implementation ignores requests for transaction hashes outside that which is recently relayed. To support "mempool", an implementation must extend its "getdata" message support to querying the memory pool. # The typical node behavior in response to an "inv" is "getdata". However, the reference Satoshi implementation ignores requests for transaction hashes outside that which is recently relayed. To support "mempool", an implementation must extend its "getdata" message support to querying the memory pool.
# Feature discovery is enabled by checking two "version" message attributes: # Feature discovery is enabled by checking two "version" message attributes:
## Protocol version >= 60002 ## Protocol version >= 60002