Search results
Create the page "Protocol specification)" on this wiki! See also the search results found.
- This BIP describes a change to the p2p protocol to allow a node to tell a peer ==Specification==6 KB (903 words) - 15:33, 5 May 2022
- ==Specification== ...a specific implementation and does not deprecate scriptPubKey to maintain protocol consistency.9 KB (1,269 words) - 17:58, 24 September 2019
- This document describes a trivial protocol extension that makes it easier for clients to detect dead peer connections. All of these can be solved by a backwards compatible protocol modification.3 KB (473 words) - 17:59, 24 September 2019
- == Specification == ...blockchain services. This proposal deals with that issue by designing this protocol in such a way that the implementation can resolve the common history betwee7 KB (1,007 words) - 07:56, 2 August 2020
- Title: Protocol for Dedicated Mining Hardware ==Specification==7 KB (981 words) - 20:27, 14 July 2012
- Title: Abstract JTAG Protocol ==Specification==6 KB (928 words) - 21:03, 4 August 2012
- ==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
- ==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 a9 KB (1,505 words) - 04:40, 1 August 2012
- ==Specification== ## Protocol version >= 600022 KB (241 words) - 20:16, 30 April 2024
- ...nd support for custom transports. However, without a general framework for protocol extensions, these custom services are likely to collide in various ways. Th ==Specification==10 KB (1,423 words) - 07:38, 2 August 2020
- 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
- ...y:Clients|client]] built using Python 2 and implements the Bitcoin network protocol. * [[Protocol specification|Bitcoin Network Protocol]]581 bytes (72 words) - 01:00, 26 September 2012
- 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
- == Specification == See [[BIP 0070]] for the current specification.1 KB (144 words) - 12:06, 10 February 2015
- On connect, [[Protocol specification#version|version]] and [[Protocol specification#verack|verack]] messages are exchanged, in order to ensure compatibility be682 bytes (109 words) - 15:44, 27 August 2018
- The Bitcoin [[Protocol specification]] previously supported the broadcast of [[Alerts]]. In the past, an unoffic2 KB (227 words) - 13:15, 6 January 2018
- * 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
- * lock_time in [[Protocol_specification#tx|the protocol specification]]2 KB (320 words) - 07:15, 17 February 2022
- The protocol version was upgraded to 70001, and the (now accepted) BIP 0037 became imple ...ict adherence to standard messages with field length compliance with every protocol version.4 KB (607 words) - 21:22, 23 April 2024
- ...All Type-1 SINs must conform to the sacrifice protocol described in this specification, to be considered valid. ...it_Sacrifices Announce/Commit Sacrifices]. That author's feedback on this protocol was very helpful.6 KB (890 words) - 04:50, 14 May 2015
