155 - addrv2 message
BIP: 155 source Layer: Peer Services Title: addrv2 message Author: Wladimir J. van der Laan 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 Table of ContentsIntroductionAbstractCopyrightMotivationSpecificationSignaling support and compatibilityReference implementationAcknowledgementsAppendix A: Tor v2 address encodingAppendix B: Tor v3 address encodingAppendix C: I2P address encodingAppendix D: Cjdns address encodingAppendix E: Yggdrasil address encodingReferences 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 addr message. Copyright This BIP is licensed under the 2-clause BSD license. Motivati...
103 - Block size following technological growth
BIP: 103 source Layer: Consensus (hard fork) Title: Block size following technological growth Author: Pieter Wuille Comments-Summary: No comments yet. Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0103 Status: Withdrawn Type: Standards Track Created: 2015-07-21 License: BSD-2-Clause Table of ContentsAbstractCopyrightMotivationSpecificationRationaleCompatibilityAcknowledgements Abstract This BIP proposes a block size growth intended to accommodate for hardware and other technological improvements for the foreseeable future. Copyright This BIP is licensed under the 2-clause BSD license. Motivation Many people want to see Bitcoin scale over time, allowing an increasing number of transactions on the block chain. It would come at an increased cost for the ecosystem (bandwidth, processing, and storage for relay nodes, as well as an impact on propagation speed of blocks on the network), but technology also improves over time. When all technologies depen...