BIPs bitcoin improvement proposals

159 - NODE_NETWORK_LIMITED service bit

<pre> BIP: 159 Layer: Peer Services Title: NODE_NETWORK_LIMITED service bit Author: Jonas Schnelli <dev@jonasschnelli.ch> Comments-Summary: No comments yet. Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0159 Status: Draft Type: Standards Track Created: 2017-05-11 License: BSD-2-Clause </pre> == Abstract == Define a service bit that allow pruned peers to signal their limited services ==Motivation== Pruned peers can offer the same services as traditional peer except of serving all historical blocks. Bitcoin right now only offers the NODE_NETWORK service bit which indicates that a peer can serve all historical blocks. # Pruned peers can relay blocks, headers, transactions, addresses and can serve a limited number of historical blocks, thus they should have a way how to announce their service(s) # Peers no longer in initial block download should consider connecting some of its outbound connections to pruned peers to allow other peers to bootstrap f...

150 - Peer Authentication

<pre> BIP: 150 Layer: Peer Services Title: Peer Authentication Author: Jonas Schnelli <dev@jonasschnelli.ch> Comments-Summary: Discouraged for implementation (one person) Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0150 Status: Draft Type: Standards Track Created: 2016-03-23 License: PD </pre> == Abstract == This BIP describes a way for peers to authenticate to other peers to guarantee node ownership and/or allow peers to access additional or limited node services, without the possibility of fingerprinting. == Motivation == We assume peer operators want to limit the access of different node services or increase datastream priorities to a selective subset of peers. Also we assume that peers want to connect to specific peers to broadcast or filter transactions (or similar actions that reveal sensitive information) and therefore operators want to authenticate the remote peer and ensure that they have not connected to a MITM (man-in-the-middle) a...

151 - Peer-to-Peer Communication Encryption

<pre> BIP: 151 Layer: Peer Services Title: Peer-to-Peer Communication Encryption Author: Jonas Schnelli <dev@jonasschnelli.ch> Comments-Summary: Controversial; some recommendation, and some discouragement Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0151 Status: Withdrawn Type: Standards Track Created: 2016-03-23 License: PD </pre> == Abstract == This BIP describes an alternative way that a peer can encrypt their communication between a selective subset of remote peers. == Motivation == The Bitcoin network does not encrypt communication between peers today. This opens up security issues (eg: traffic manipulation by others) and allows for mass surveillance / analysis of bitcoin users. Mostly this is negligible because of the nature of Bitcoin's trust model, however, for SPV nodes this can have significant privacy impacts [1] and could reduce the censorship-resistance of a peer. Encrypting peer traffic will make analysis and specific user targ...

136 - Bech32 Encoded Tx Position References

<pre> BIP: 136 Layer: Applications Title: Bech32 Encoded Tx Position References Author: Велеслав <veleslav.bips@protonmail.com> Jonas Schnelli <dev@jonasschnelli.ch> Daniel Pape <dpape@dpape.com> Comments-Summary: No comments yet. Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0136 Status: Draft Type: Informational Created: 2017-07-09 License: BSD-2-Clause </pre> == Introduction == === Abstract === This document proposes a convenient, human usable encoding to refer to a '''confirmed transaction position''' within the Bitcoin blockchain--known as '''"TxRef"'''. The primary purpose of this encoding is to allow users to refer to a confirmed transaction (and optionally, a particular outpoint index within the transaction) in a standard, reliable, and concise way. ''Please note: Unlike a transaction ID, '''"TxID"''', where there is a strong cryptographic link between the ID and the actual transaction, a '''TxRef''' only provides a w...

155 - addrv2 message

<pre> BIP: 155 Layer: Peer Services Title: addrv2 message Author: Wladimir J. van der Laan <laanwj@gmail.com> Comments-Summary: No comments yet. Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0155 Status: Draft Type: Standards Track Created: 2019-02-27 License: BSD-2-Clause </pre> ==Introduction== ===Abstract=== This document proposes a new P2P message to gossip longer node addresses over the P2P network. This is required to support new-generation Onion addresses, I2P, and potentially other networks that have longer endpoint addresses than fit in the 128 bits of the current <code>addr</code> message. ===Copyright=== This BIP is licensed under the 2-clause BSD license. ===Motivation=== Tor v3 hidden services are part of the stable release of Tor since version 0.3.2.9. They have various advantages compared to the old hidden services, among which better encryption and privacy <ref>[https://gitweb.torproject.org/torspec.git/tree/rend-spec-v3.txt ...