BIPs bitcoin improvement proposals

122 - URI scheme for Blockchain references / exploration

BIP: 122 source Layer: Applications Title: URI scheme for Blockchain references / exploration Authors: Marco Pontello Status: Draft Type: Specification Assigned: 2015-08-29 License: PD Discussion: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-August/010712.html Table of ContentsAbstractMotivationSpecificationABNF grammarDefinition of chain IDExamplesRationaleSample implementationAcknowledgementsCopyright Abstract This BIP proposes a URI scheme for looking up blocks, transactions and addresses on a Blockchain explorer, or in general to make proper Blockchain references. Motivation The purpose of this URI scheme is to enable users to handle all the requests for details about blocks, transactions, etc. with their preferred tool (being that a web service or a local application). Currently a Bitcoin client usually points to an arbitrary blockchain explorer when the user looks for the details of a transaction or allows the user to choose from a set of altern...

123 - BIP Classification

BIP: 123 source Title: BIP Classification Authors: Eric Lombrozo Status: Deployed Type: Process Assigned: 2015-08-26 License: CC0-1.0 OR FSFAP Table of ContentsAbstractCopyrightMotivationSpecification1. Consensus LayerSoft ForksHard Forks2. Peer Services Layer3. API/RPC Layer4. Applications LayerClassification of existing BIPs Abstract This document describes a classification scheme for BIPs. BIPs are classified by system layers with lower numbered layers involving more intricate interoperability requirements. The specification defines the layers and sets forth specific criteria for deciding to which layer a particular standards BIP belongs. Copyright This BIP is dual-licensed under the Creative Commons CC0 1.0 Universal and FSF All Permissive licenses. Motivation Bitcoin is a system involving a number of different standards. Some standards are absolute requirements for interoperability while others can be considered optional, giving implementers a choice of whether to su...