Search results
Jump to navigation
Jump to search
- It has mostly been superceded by the newer [[getblocktemplate]] mining protocol, but the data format is still often used internal to some miner structures. ==Protocol== ...10 KB (1,545 words) - 03:00, 1 April 2015
- ==Specification== This is a hard-forking change to the Bitcoin protocol; anybody running code that fully validates blocks must upgrade before the a ...5 KB (736 words) - 07:39, 2 August 2020
- == Specification == *BIP70 Payment protocol ...6 KB (918 words) - 17:58, 24 September 2019
- ==Specification== ...r [[bip-0141.mediawiki#Commitment_structure|BIP 141's commitment structure specification]] to be inserted into the generation (coinbase) transaction. ...6 KB (867 words) - 18:00, 24 September 2019
- ==Specification== ...posal]], as a safe runway prior to switching to Phase 2, while network and protocol infrastructure is improved ...6 KB (909 words) - 07:50, 2 August 2020
- ...hers' behalf even if it would not sign actual transactions. No signmessage protocol can fix these limitations. Full signatures follow an analogous specification to the BIP-325 challenges and solutions used by Signet. ...11 KB (1,699 words) - 18:07, 31 May 2024
- ==Specification== A new serialization format for tx messages is added to the peer-to-peer protocol. ...5 KB (805 words) - 18:00, 24 September 2019
- ==Specification== Our specification consists of two parts: ...11 KB (1,592 words) - 21:35, 30 April 2024
- ==Specification== ===Network protocol=== ...9 KB (1,468 words) - 17:10, 21 August 2020
- This is a project to define a new wallet protocol addressing problems with the current JSON-RPC implementation in bitcoind. This protocol aims to be a standard for communication between Wallets and User Interfaces ...15 KB (2,054 words) - 03:35, 20 August 2011
- ==Specification== ...to directly contact a large number of miners using a best-effort datagram protocol (specifically, UDP), send them their transaction, and in return, receive a ...9 KB (1,505 words) - 04:40, 1 August 2012
- Title: Abstract JTAG Protocol ==Specification== ...6 KB (928 words) - 21:03, 4 August 2012
- ...r its processes or environment. The BIP should provide a concise technical specification of the feature and a rationale for the feature. ...fects most or all Bitcoin implementations, such as a change to the network protocol, a change in block or transaction validity rules, or any change or addition ...16 KB (2,623 words) - 10:02, 1 January 2021
- More information and in-depth technical information is in the [[Protocol Specification]]. * [[Protocol Specification]] ...8 KB (1,270 words) - 14:13, 13 June 2018
- ==Specification== ...ctivation is achieved, the maximum block size shall be as described in the specification section, regardless of the version number of the block. ...10 KB (1,479 words) - 17:59, 24 September 2019
- Title: Bustapay :: a practical coinjoin protocol Bustapay is a simple and practical protocol for the sender and receiver of a payment to collaboratively sign a bitcoin ...12 KB (1,819 words) - 03:54, 9 June 2024
- ==Specification== ...a specific implementation and does not deprecate scriptPubKey to maintain protocol consistency. ...9 KB (1,269 words) - 17:58, 24 September 2019
- ==Specification== It indicates that the subtree of this node is used according to this specification. ...9 KB (1,520 words) - 13:01, 12 October 2019
- The specification defines the layers and sets forth specific criteria for deciding to which l ==Specification== ...16 KB (1,847 words) - 18:00, 24 September 2019
- getblocktemplate is the new decentralized Bitcoin mining protocol, openly developed by the Bitcoin community over mid 2012. It supercedes the old [[getwork]] mining protocol. ...15 KB (2,134 words) - 02:01, 26 March 2019