BIPs bitcoin improvement proposals

38 - Passphrase-protected private key

BIP: 38 source Layer: Applications Title: Passphrase-protected private key Authors: Mike Caldwell Aaron Voisine Comments-Summary: Unanimously Discourage for implementation Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0038 Status: Draft (Some confusion applies: The announcements for this never made it to the list, so it hasn't had public discussion) Type: Specification Assigned: 2012-11-20 License: PD Table of ContentsAbstractMotivationCopyrightRationaleSpecificationPrefixProposed specificationEncryption when EC multiply flag is not usedEncryption when EC multiply mode is usedConfirmation codeDecryptionBackwards compatibilitySuggestions for implementers of proposal with alt-chainsDiscussion item: scrypt parametersReference implementationTest vectorsNo compression, no EC multiplyCompression, no EC multiplyEC multiply, no compression, no lot/sequence numbersEC multiply, no compression, lot/sequence numbers Abstract A method is proposed for...

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...