0
In regards to P2SH-P2WSH transactions, are Txout-script values identical between transactions? Is it reasonable to expect a business or vendor that accepts bitcoin to be using the same redeemScript for all transactions and use the same Txout-script value? Would users benefit from this value rotating?
0
Let's look at an example of this type of transaction:
The following example is the same 1-of-2 multi-signature P2WSH script, but nested in a BIP16 P2SH output.
witness: 0 <signature1> <1 <pubkey1> <pubkey2> 2 CHECKMULTISIG>
scriptSig: <0 <32-byte-hash>>
(0x220020{32-byte-hash})
scriptPubKey: HASH160 <20-byte-hash> EQUAL
(0xA914{20-byte-hash}87)
So, let's say the user that created this script accepts multiple payments to this same script. In order to spend the Bitcoin received at the script, they must provide the same redeemScript, but one thing will change with each transaction, and that is the <signature1>. Since the transactions are not exactly the same each time, the data being signed will change, and even though it was signed with potentially the same key (could use key2), it will produce a different signature.
This isn't necessarily bad, but it is more common to see a business or vendor generate new script/addresses for each payment they receive so it can be easily tracked and verified.
2Do you mean the same policy being reused, or the actual script being reused? (usually the keys will change, but all of them will be 2-of-3 or something like that) – Pieter Wuille – 2019-07-15T20:07:17.843
@PieterWuille Both, but this is a technical question. – Rook – 2019-07-15T22:07:52.067