Search results
Jump to navigation
Jump to search
- ...uffix indicating whether the corresponding public key is compressed (<code>0x01</code>) or not (through suffix absence), there is no way of knowing what ki |<code>0x01</code>||P2PKH_COMPRESSED||Yes||Compressed legacy public key. Unknown public ...4 KB (574 words) - 18:00, 24 September 2019
- ...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
- | 1 || reject-code || uint8_t || 0x01 through 0x4f (see below) | 0x01-0x0f || Protocol syntax errors ...5 KB (662 words) - 21:45, 30 April 2024
- 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
- ...which is precisely the single byte vector <code>0x01</code><ref>'''Use of 0x01 public key type''' ...signature opcodes are modified by removing keys with the first byte <code>0x01</code> and length of either 1-byte or 33-bytes from the list of unknown pub ...20 KB (3,134 words) - 23:13, 29 September 2022
- ...termine if this input's signature hash type is standard (0x00 for Taproot, 0x01 for Legacy/Segwit). | Input Hash Type || 0x00 for Taproot, 0x01 for Legacy || 7 Bits For Each Input ...13 KB (1,873 words) - 19:37, 28 May 2024
- * 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
- HA = H(0x01|H(SA)) = H(0x015acb54166e0db370cd1b05a29120373568dacea2abc3748459ec3da2106e HG = H(0x01|H(SG)) = 0xaa5fbdf58264650eadec33691ba1e7606d0a62f570eea348a465c55bc86ffc10 ...23 KB (3,500 words) - 19:01, 13 May 2024
- * '''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
- ...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
- | <code>0x01</code> ...8 KB (1,315 words) - 22:59, 26 April 2024
- 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
- | <version> || 2 || Version, little endian, currently 0x01 0x00 ...9 KB (1,453 words) - 17:59, 24 September 2019
- * Byte 0: version. required value: 0x01 # If the first byte of the payload in a notification transaction is 0x01: ...22 KB (3,422 words) - 04:56, 31 May 2024
- .../code>: the argument of <code>IF</code>/<code>NOTIF</code> must be exactly 0x01 or empty push ...11 KB (1,699 words) - 18:07, 31 May 2024
- * 0x01 0x42 + ''flagbyte'' + ''salt'' + ''encryptedhalf1'' + ''encryptedhalf2'' * 0x01 0x43 + ''flagbyte'' + ''addresshash'' + ''ownerentropy'' + ''encryptedpart1 ...31 KB (4,670 words) - 12:32, 22 May 2024
- | <tt>PSBT_GLOBAL_XPUB = 0x01</tt> | <tt>PSBT_IN_WITNESS_UTXO = 0x01</tt> ...130 KB (21,097 words) - 21:38, 30 April 2024
- 0x01 0x00 Version 1 of the protocol. ...15 KB (2,058 words) - 01:44, 13 May 2020
- '''Accepted scripts:''' 0x03 (legacy + segwit) (0x01 | 0x02) ...16 KB (2,596 words) - 04:31, 29 May 2024
- If none of the conditions fail, a single true value (<code>0x01</code>) is left on the stack. If none of the conditions fail, a single true value (<code>0x01</code>) is left on the stack. ...43 KB (6,456 words) - 04:35, 29 May 2024