Search results

Jump to navigation Jump to search
View (previous 20 | ) (20 | 50 | 100 | 250 | 500)

Page title matches

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

Page text matches

  • Title: Payment Protocol MIME types Wallet or server software that sends payment protocol messages over ...
    1 KB (145 words) - 18:00, 24 September 2019
  • ...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
  • ...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
  • An alternate implementation of the Bitcoin network protocol. * [[Protocol specification|Bitcoin Network Protocol]] ...
    678 bytes (77 words) - 16:55, 25 June 2011
  • 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
  • == Specification == See [[BIP 0070]] for the current specification. ...
    1 KB (144 words) - 12:06, 10 February 2015
  • Title: bitcoin: uri extensions for Payment Protocol support the payment protocol (BIP 70). ...
    2 KB (375 words) - 18:00, 24 September 2019
  • explicitly. It also bumps the protocol version to allow peers to == Specification == ...
    3 KB (518 words) - 18:00, 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== ## Protocol version >= 60002 ...
    2 KB (241 words) - 20:16, 30 April 2024
  • This BIP describes two changes to the p2p protocol to support transaction relay ==Specification== ...
    3 KB (490 words) - 17:17, 21 August 2020
  • 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
  • ...ation: [https://github.com/chromaway/ngcccbase/wiki/EPOBC_simple The EPOBC protocol] which allows you to store assets on the [[http://chromawallet.com|Bitcoin ...nting the [https://github.com/chromaway/ngcccbase/wiki/EPOBC_simple EPOBC] protocol. ...
    2 KB (278 words) - 14:53, 2 November 2015
  • why they are being banned for not following the protocol helps ==Specification== ...
    5 KB (662 words) - 21:45, 30 April 2024
  • 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
  • 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
  • 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
  • Title: Allow zero value OP_RETURN in Payment Protocol This BIP alters the Payment Protocol to allow for zero value OP_RETURN outputs in serialized PaymentRequests. ...
    6 KB (975 words) - 17:59, 24 September 2019
  • 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
  • ==Specification== # Feature discovery is enabled by checking protocol version >= 70012 ...
    3 KB (429 words) - 18:00, 24 September 2019
View (previous 20 | ) (20 | 50 | 100 | 250 | 500)