Search results
Jump to navigation
Jump to search
- Bitcoin's transaction spreading protocol is vulnerable to deanonymization Dandelion). We have shown that this routing protocol provides near-optimal ...17 KB (2,524 words) - 07:48, 2 August 2020
- ...ng code, so it is [https://github.com/Colored-Coins/Colored-Coins-Protocol-Specification/wiki/Faq#coloring-satoshis no longer the only case] that individual satoshi ==The EPOBC protocol== ...15 KB (2,058 words) - 01:44, 13 May 2020
- == Specification == The use of normalized transaction IDs is introduced as a softfork. The specification is divided into three parts: ...15 KB (2,249 words) - 04:35, 29 May 2024
- * Disallow small value orders, see [[Prime Specification|Performance]] settings in admin panel ===Correct use of HTTP protocol=== ...8 KB (1,182 words) - 22:35, 20 April 2013
- ==Specification== * Bitstream, a protocol for the atomic swap (fair exchange) of bitcoins for decryption keys, that e ...10 KB (1,649 words) - 20:08, 6 May 2024
- == Specification == ...gnature replay cannot cause loss of funds (eg due to other features of the protocol or other constraints on the transaction), or when such a loss of funds is a ...20 KB (3,134 words) - 23:13, 29 September 2022
- ==Specification== In the event that future protocol upgrades introduce new signature hash types, compliant software should appl ...12 KB (1,826 words) - 16:03, 15 December 2021
- ...r its processes or environment. The BIP should provide a concise technical specification of the feature and a rationale for the feature. ...d implementation, if applicable, must be solid and must not complicate the protocol unduly. ...34 KB (5,496 words) - 20:07, 24 April 2024
- ...t is undefined. Versions greater than 2 are reserved for future use by the protocol. Flag and Witness are mandatory for any transaction that includes [[Segwit] ...hash, which has a specific definition for scriptPubKey, and scriptSig. The specification places no limitations on the script, and hence absolutely any contract can ...15 KB (2,222 words) - 09:52, 17 January 2024
- ==Specification== Note that all sections of this specification are optional extensions on top of [[bip-0022.mediawiki|BIP 22]]. ...14 KB (2,058 words) - 18:00, 24 September 2019
- When receiving an Aux proof-of-work block in a [[Protocol specification#block|"<tt>block</tt>" network message]], the data received is similar to a | ? || coinbase_txn || [[Protocol specification#tx|txn]] || Coinbase transaction that is in the parent block, [[#Merged min ...17 KB (2,390 words) - 12:31, 8 August 2015
- ...n libsecp256k1 after #REPLACE_libsecp256k1_PR), it is still not a complete specification of the consensus rules. Since libconsensus doesn't manage the current state that there's many alternative implementations of the protocol (forks ...18 KB (2,863 words) - 21:58, 30 April 2024
- This BIP adds new support to the peer-to-peer protocol that allows peers to reduce the amount of transaction data they are sent. P ==Specification== ...17 KB (2,887 words) - 18:00, 24 September 2019
- The PayPub protocol makes it possible to pay for information in a trustless way ==Detailed Specification== ...13 KB (1,845 words) - 17:59, 24 September 2019
- '''bitcoind''' is a program that implements the Bitcoin protocol for remote procedure call (RPC) use. It is also the second Bitcoin [[Client * [[Protocol specification|Bitcoin network protocol]] ...17 KB (2,172 words) - 01:37, 10 June 2019
- This document proposes a protocol for two parties * Lack of basic versioning negotiation if the protocol evolves. ...40 KB (5,341 words) - 21:40, 30 April 2024
- ==Specification== ...termination. This was one of a major design flaws in the original bitcoin protocol as it permitted unconditional third party theft by placing an <code>OP_RETU ...24 KB (3,690 words) - 02:50, 27 February 2023
- The wiki substantially documents the [[Protocol_specification|Bitcoin protocol]], but equally important are the rules used by the client to process messag * [[Protocol specification]] ...12 KB (1,987 words) - 10:29, 23 June 2020
- This document specifies a protocol for static payment addresses in Bitcoin without on-chain linkability of pay ...transaction belong to the same entity as there is no formal proof that the protocol is secure in a collaborative setting. ...49 KB (7,978 words) - 04:49, 31 May 2024
- Title: Version 2 P2P Encrypted Transport Protocol This document proposes a new Bitcoin P2P transport protocol, which features opportunistic encryption, a mild bandwidth reduction, and t ...65 KB (9,770 words) - 08:04, 29 September 2023