Search results

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

Page title matches

• Protocol Specification
  #REDIRECT [[Protocol documentation]]
  36 bytes (3 words) - 19:52, 15 April 2015
• Protocol specification
  #REDIRECT [[Protocol documentation#Block_Headers]]
  50 bytes (5 words) - 16:10, 6 November 2018

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) - 17:59, 24 September 2019

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