Hot answers tagged

6

As far as I can tell, P2TR is better than P2WSH in almost every way. I cannot think of a case in which it would be a significant advantage to use P2WSH over P2TR, except that P2WSH is already established. Privacy P2TR outputs will stand out at first since there will be few of them. In the long term, the anonymity set of P2TR is likely to be larger since both ...


4

In addition to the rationale given in BIP 341, I know of two arguments for not supporting P2SH-wrapped taproot outputs: backwards-compatibility: P2SH-wrapped segwit outputs were included in BIP 141 as a way to allow unupgraded wallets to send outputs to upgraded segwit wallets[0]. Segwit activation happened around 4 years ago, and almost all wallets/...


4

Because P2SH addresses are too short to provide typically desirable levels of security security level we expect from Bitcoin, against certain attacks. On top of that, they use bech32 encoding rather than base58, which means they're slightly longer for the same amount of data, but are case insensitive instead. For any kind of "multi party" address (...


3

P2PKH addresses are 33-34 characters long, use Base58Check encoding, and (on mainnet) start with "1". P2SH addresses are 34 characters long, use Base58Check encoding, and (on mainnet) start with "3". P2WPKH addresses are 42 characters long, use bech32 encoding, and (on mainnet) start with "bc1q". P2WSH addresses are 62 ...


2

The encoding is bech32 not base58, which is slightly longer but vastly easier to type due to a lack of capital letters, and the inclusion of error correction rather than error detection. SegWit scripts use SHA256 not RIPEMD160 for the hash function, which is longer and stronger.


2

This is a transaction with three P2WPKH (native segwit v0 single-sig) inputs and a single P2WPKH output. For P2WPKH, the scriptPubKey (the locking script encoded in an output) contains a witness program that commits to the hash of a public key. The witness in the input therefore reveals the corresponding pre-image of the hash in the form of the public key (...


1

TL;DR: A 2-of-2 P2WSH input should be conservatively estimated with 96 vbytes. Standard 2-of-2 P2WSH inputs generally weigh 95.5, 95.75 or 96.0 vbytes, depending on whether the r-values in the signatures are low or high. A wallet using signature grinding (which is highly recommended) will always produce 95.5 vbyte inputs. 96.0 vbytes is the conservative ...


Only top voted, non community-wiki answers of a minimum length are eligible