Search results

Jump to: navigation, search
  • | <code>getrawmempool</code> || || '''version 0.7''' Returns all transaction ids in memory pool || N
    13 KB (1,835 words) - 12:49, 27 June 2020
  • ...ShortIDs structure is used to relay a block header, the short transactions IDs used for matching already-available transactions, and a select few transact ...used to encode array lengths elsewhere || The number of short transaction IDs in shortids (ie block tx count - prefilledtxn_length)
    59 KB (8,369 words) - 19:28, 12 April 2021
  • ...is information can't identify anyone because the addresses and transaction IDs are just random numbers. However, if ''any'' of the addresses in a transact ...hod that has been deployed. Examples of (likely) [[CoinJoin]] transactions IDs on bitcoin's blockchain are <code>402d3e1df685d1fdf82f36b220079c1bf44db227d
    157 KB (24,673 words) - 16:15, 29 April 2021
  • ...firm their identity and share them with other users about so-called public IDs.
    629 bytes (95 words) - 02:03, 10 June 2019
  • ...r_id not specified the return value is a dict indexed by the currency pair ids<br/>
    3 KB (425 words) - 23:37, 6 April 2014
  • ...ibly including real names, contact information, previous projects, twitter IDs)
    7 KB (1,117 words) - 04:20, 13 August 2014
  • returns a list of all the cancelled trades this last month, list of trade ids in json format .
    35 KB (5,897 words) - 20:32, 30 May 2013
  • '''Adaptive difficulty''' is a Bitcoin protocol change proposal by [[User:Ids|Iain Stewart]], with the goal of letting the typical time interval from one ...here for historical completeness, but not continue working on it.) [[User:Ids|Iain Stewart]] 01:00, 23 November 2012 (GMT)''
    11 KB (1,772 words) - 02:51, 25 November 2012
  • ...hain fair sharing''' is a draft Bitcoin protocol change proposal by [[User:Ids|Iain Stewart]], with the goal of allowing the network to continue to settle ...gher, goal. I hope this indicates the general direction I'm headed. [[User:Ids|Iain Stewart]] 11:15, 21 May 2012 (GMT)
    13 KB (2,096 words) - 22:42, 6 May 2013
  • * 2*N bytes: hardware component ids
    7 KB (981 words) - 20:27, 14 July 2012
  • ...y possible variants of proof of burn. This page currently describes [[User:Ids|Iain Stewart]]'s version. Other people can add variant versions that still
    32 KB (5,261 words) - 12:10, 15 January 2018
  • This BIP describes the use of normalized transaction IDs (NTXIDs) in order to eliminate transaction malleability, both in the third- The use of normalized transaction IDs is introduced as a softfork. The specification is divided into three parts:
    15 KB (2,249 words) - 07:56, 2 August 2020
  • ...structure, <code>witness</code>, is defined. Each transaction will have 2 IDs. ...prove the spending of a non-existing input without showing all transaction IDs in the blockchain way back to the genesis block.
    25 KB (3,861 words) - 21:20, 12 February 2021
  • The list of reserved network IDs is as follows:
    8 KB (1,248 words) - 21:27, 12 February 2021
  • transactions' tx-ids but appended to that are the v4 hashes that include the
    12 KB (1,921 words) - 17:03, 21 August 2020
  • //TODO consider BIP44 coin type ids instead:
    10 KB (1,567 words) - 17:59, 24 September 2019
  • ...n this mode, peers send new block announcements with the short transaction IDs already (via a <code>cmpctblock</code> message), possibly even before fully ...request, which will receive a response of the header and short transaction IDs. In some cases no further round-trip is needed, and the receiver can recons
    30 KB (4,803 words) - 07:56, 2 August 2020
  • ====32-bit short transaction IDs==== During reconciliation, significantly abbreviated transaction IDs are used of just 32 bits in size. To prevent attackers from constructing se
    20 KB (3,092 words) - 23:56, 5 November 2019