Search results

Jump to: navigation, search

Create the page "Protocol specification)" on this wiki! See also the search results found.

Page title matches

Page text matches

  • Bitcoind
    '''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
  • Original Bitcoin client/API calls list
    ....com/bitcoin/bitcoin/blob/62f2d769e45043c1f262ed45babb70fe237ad2bb/src/rpc/protocol.h#L30 rpcprotocol.h] for the list of error codes and their meanings. * [[Protocol specification]]
    13 KB (1,835 words) - 12:49, 27 June 2020
  • Protocol documentation
    ...articular, while this page is quite complete in describing the [[network]] protocol, it does not attempt to list all of the rules for block or transaction vali For protocol used in mining, see [[getblocktemplate]].
    59 KB (8,414 words) - 18:08, 30 July 2021
  • Network
    More information and in-depth technical information is in the [[Protocol Specification]]. * [[Protocol Specification]]
    8 KB (1,270 words) - 14:13, 13 June 2018
  • Transaction
    ...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
  • Payment channels
    A full description of the protocol is in [[Contract#Example_7:_Rapidly-adjusted_.28micro.29payments_to_a_pre-d ...in-dev mailing lists<ref name="bitcoin_dev_bip65"/>, and included a design specification in [https://github.com/bitcoin/bips/blob/master/bip-0065.mediawiki BIP65].
    15 KB (2,209 words) - 07:45, 4 October 2021
  • Tonal Bitcoin
    ...oves usability by allowing for infinite binary division (note that Bitcoin protocol support is still finite). == Specification ==
    9 KB (1,334 words) - 23:59, 3 May 2017
  • New York Agreement
    The protocol change specification is given in [https://github.com/btc1/specifications/blob/master/PCS/PCS-201
    903 bytes (127 words) - 15:07, 11 January 2018
  • BIP 0045
    ==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
  • BitDroid
    An alternate implementation of the Bitcoin network protocol. * [[Protocol specification|Bitcoin Network Protocol]]
    678 bytes (77 words) - 16:55, 25 June 2011
  • Wallet protocol
    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
  • Pycoin
    ...y:Clients|client]] built using Python 3 and implements the Bitcoin network protocol. ...cointalk.org/index.php?topic=4084.0 Announcing Pycoin, a (partial) bitcoin protocol implementation in python3]</ref>
    583 bytes (70 words) - 18:46, 19 February 2012
  • Protocol rules
    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
  • Alternative chain
    ...e "transaction" described using [http://code.google.com/p/protobuf/ Google protocol buffers] syntax. ...odebase. It can be written in whatever language you like, use whatever P2P protocol you like, store its data however you like and so on.
    24 KB (3,974 words) - 19:05, 7 June 2017
  • Getwork
    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
  • P2SH²
    ...want to destroy their bitcoins. But what is a problem is that the Bitcoin protocol has no way to determine that the bitcoins spent to pseudo-hashes are imposs ...hes than in an OP_RETURN output. So it would still be nice if the Bitcoin protocol could otherwise discourage people from storing data in hash fields.
    11 KB (1,738 words) - 07:11, 6 January 2018
  • BIP 0001
    ...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
  • Using USB-DFU Protocol
    | 2 || bcdUSB || 2 || 0100h || USB specification release number in binary coded decimal. | 7 || bInterfaceProtocol || 1 || 01h || Runtime protocol.
    4 KB (507 words) - 03:13, 8 January 2016
  • Merged mining specification
    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
  • BIP 0015
    [[bip-0070.mediawiki|BIP 0070]] (payment protocol) may be seen as the alternative to Aliases. ...areful argument, a bitcoin alias system. This is a big modification to the protocol that is not easily changed in the future and has big ramifications. There i
    19 KB (2,806 words) - 21:51, 30 April 2024
  • BIP 0338
    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
  • BIP 0018
    ==Specification== ...a specific implementation and does not deprecate scriptPubKey to maintain protocol consistency.
    9 KB (1,269 words) - 17:58, 24 September 2019
  • BIP 0031
    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
  • BIP 0033
    == 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 betwee
    7 KB (1,007 words) - 07:56, 2 August 2020
  • BIP MinerHardwareBinaryProtocol
    Title: Protocol for Dedicated Mining Hardware ==Specification==
    7 KB (981 words) - 20:27, 14 July 2012
  • BIP AbstractJTAGProtocol
    Title: Abstract JTAG Protocol ==Specification==
    6 KB (928 words) - 21:03, 4 August 2012
  • BIP 0023
    ==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
  • BIP Draft - Instant Partial Confirmation
    ==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
  • BIP 0035
    ==Specification== ## Protocol version >= 60002
    2 KB (241 words) - 20:16, 30 April 2024
  • BIP 0036
    ...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
    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
  • Pynode
    ...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
  • BIP 0037
    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
  • Payment Request
    == Specification == See [[BIP 0070]] for the current specification.
    1 KB (144 words) - 12:06, 10 February 2015
  • Version Handshake
    On connect, [[Protocol specification#version|version]] and [[Protocol specification#verack|verack]] messages are exchanged, in order to ensure compatibility be
    682 bytes (109 words) - 15:44, 27 August 2018
  • Alerts mailing list
    The Bitcoin [[Protocol specification]] previously supported the broadcast of [[Alerts]]. In the past, an unoffic
    2 KB (227 words) - 13:15, 6 January 2018
  • Prime Specification
    * 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
  • NLockTime
    * lock_time in [[Protocol_specification#tx|the protocol specification]]
    2 KB (320 words) - 07:15, 17 February 2022
  • BIP 0060
    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
  • Identity protocol v1
    ...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
  • BIP 0070
    Title: Payment Protocol This BIP describes a protocol for communication between a merchant and their customer, enabling
    16 KB (2,318 words) - 00:27, 1 October 2022
  • BIP 0071
    Title: Payment Protocol MIME types Wallet or server software that sends payment protocol messages over
    1 KB (145 words) - 18:00, 24 September 2019
  • BIP 0072
    Title: bitcoin: uri extensions for Payment Protocol support the payment protocol (BIP 70).
    2 KB (375 words) - 18:00, 24 September 2019
  • BIP 0073
    This BIP describes an enhancement to the payment protocol ([[bip-0070.mediawiki|BIP 70]]) generalizes the specification for the behavior of a payment request URL in a
    4 KB (686 words) - 17:59, 24 September 2019
  • Avalon1
    == [https://bitcointalk.org/index.php?topic=120184.msg1294416#msg1294416 Chip Specification] == ...er's performance, it is recommended that you choose pools with the stratum protocol supported. The default mining pool configured in Avalon is ozco.in. To chan
    29 KB (4,203 words) - 22:45, 13 April 2015
  • Colored Coins
    ...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
  • Stratum mining protocol
    ...to support pooled mining as a replacement for obsolete [[Getwork|getwork]] protocol in late 2012. ...site<ref>[http://mining.bitcoin.cz/stratum-mining/ Stratum mining protocol specification at slush's pool's website]</ref>.
    8 KB (1,147 words) - 05:29, 10 October 2015
  • BIP 0065
    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
  • BIP 0061
    why they are being banned for not following the protocol helps ==Specification==
    5 KB (662 words) - 21:45, 30 April 2024
  • BIP 0064
    This document describes a small P2P protocol extension that performs UTXO lookups given a set of outpoints. SPV wallet. This use case requires some other changes to the Bitcoin protocol however, so we will
    5 KB (844 words) - 07:47, 2 August 2020

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)

Retrieved from "https://en.bitcoin.it/wiki/Special:Search"