Search results

Create the page "0x01" on this wiki! See also the search results found.

• Protocol documentation
  | 0x01 || REJECT_MALFORMED||
  59 KB (8,414 words) - 18:08, 30 July 2021
• Script
  |0x01-0x4b
  27 KB (4,450 words) - 22:25, 26 April 2024
• OP CHECKSIG
  raw_data = {0x04, 0x11, 0xdb, 0x93, 0xe1, 0xdc, 0xdb, 0x8a, 0x01, 0x6b, 0x49, 0x84, 0x0f, 0x8c, 0x53, 0xbc, 0x1e, 0xb6, 0x8a, 0x38, 0x2e, 0x raw_data = {0x04, 0x11, 0xdb, 0x93, 0xe1, 0xdc, 0xdb, 0x8a, 0x01, 0x6b, 0x49, 0x84, 0x0f, 0x8c, 0x53, 0xbc, 0x1e, 0xb6, 0x8a, 0x38, 0x2e, 0x
  16 KB (2,703 words) - 21:44, 16 January 2019
• Wallet import format
  ...net addresses or <code>0xef</code> for testnet addresses. Also add a <code>0x01</code> byte at the end if the private key will correspond to a compressed p ...ed to a compressed public key, also drop the last byte (it should be <code>0x01</code>). If it corresponded to a compressed public key, the WIF string will
  4 KB (673 words) - 19:54, 11 March 2024
• List of address prefixes
  ...n for the compressed form starting with a different character is because a 0x01 byte is appended to the private key before base58 encoding.
  6 KB (935 words) - 21:13, 7 January 2024
• BIP 0032
  * 1 byte: depth: 0x00 for master nodes, 0x01 for level-1 derived keys, ....
  27 KB (4,535 words) - 16:56, 24 April 2024
• BIP 0038
  * 0x01 0x42 + ''flagbyte'' + ''salt'' + ''encryptedhalf1'' + ''encryptedhalf2'' * 0x01 0x43 + ''flagbyte'' + ''addresshash'' + ''ownerentropy'' + ''encryptedpart1
  31 KB (4,685 words) - 23:00, 26 April 2024
• Identity protocol v1
  SIN_Type 0x01 (bitcoin main chain) or 0x11 (testnet) # SIN_Type = [0x01 | 0x02 | 0x11] -- See above for discussion of SIN types.
  6 KB (890 words) - 04:50, 14 May 2015
• Colored Coins
  0x01 0x00 Version 1 of the protocol.
  15 KB (2,058 words) - 01:44, 13 May 2020
• BIP 0061
  | 1 || reject-code || uint8_t || 0x01 through 0x4f (see below) | 0x01-0x0f || Protocol syntax errors
  5 KB (662 words) - 21:45, 30 April 2024
• BIP 0062
  * sighash-type: 1-byte hashtype flag (only 0x01, 0x02, 0x03, 0x81, 0x82 and 0x83 are allowed). * Pushing a 1-byte sequence of byte 0x01 through 0x10 must use OP_n.
  11 KB (1,640 words) - 17:58, 24 September 2019
• BIP 0120
  | &lt;version> || 2 || Version, little endian, currently 0x01 0x00
  9 KB (1,453 words) - 17:59, 24 September 2019
• Avalon6
  Chip_SYSCTL_Map(0x01);<br />
  22 KB (3,104 words) - 07:59, 15 August 2016
• BIP 0047
  * Byte 0: version. required value: 0x01 # If the first byte of the payload in a notification transaction is 0x01:
  22 KB (3,425 words) - 18:29, 24 April 2024
• BIP 0141
  The <code>flag</code> MUST be a 1-byte non-zero value. Currently, <code>0x01</code> MUST be used.
  26 KB (3,935 words) - 23:08, 26 April 2024
• BIP 0144
  * '''Rationale for the 0x01 flag byte in between''': this will allow us to easily add more extra non-co
  5 KB (805 words) - 18:00, 24 September 2019
• BIP 0322
  .../code>: the argument of <code>IF</code>/<code>NOTIF</code> must be exactly 0x01 or empty push
  11 KB (1,659 words) - 14:18, 1 May 2024
• BIP 0098
  ...ficant bit <code>0x80</code> and ends with the least significant bit <code>0x01</code>.
  20 KB (3,076 words) - 17:58, 24 September 2019
• BIP 0155
  | <code>0x01</code>
  8 KB (1,315 words) - 22:59, 26 April 2024
• BIP 0174
  | <tt>PSBT_GLOBAL_XPUB = 0x01</tt> | <tt>PSBT_IN_WITNESS_UTXO = 0x01</tt>
  130 KB (21,097 words) - 21:38, 30 April 2024

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