Hi Andrew,
If you use SIGHASH_ALL it shall sign the COutPoints of all inputs which
commit to the scriptPubKeys of the txn.
Thus the 341 hash doesn't need to sign any additional data.
As a metadata protocol you can provide all input transactions to check the
scriptPubKeys.
Best,
Jeremy
--
@Jere
Hello ZmnSCPxj,
On 30/04/2020 09:54, ZmnSCPxj wrote:
> Good morning CB,
>
>
>> Equal-output-coinjoins and JoinMarket also have a version of the
>> common-input-ownership-heuristic (CIOH), because its often possible to
>> separate the inputs into sets of their owners of a equal-output-coinjoin
>>
https://github.com/bitcoin/bips/blob/master/bip-0069.mediawiki
--
Best Regards / S pozdravom,
Pavol "stick" Rusnak
CTO, SatoshiLabs
On Thu, Apr 30, 2020, 10:21 SatoshiSingh via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Hi list. I've been a lurker for quite sometime and this
Good morning CB,
> Equal-output-coinjoins and JoinMarket also have a version of the
> common-input-ownership-heuristic (CIOH), because its often possible to
> separate the inputs into sets of their owners of a equal-output-coinjoin
> using the input amounts. CoinSwap can be combined with somethin
Hi everyone,
In the current draft of BIP-0341 [1] the signature message commits to the
scriptPubKey of the output being spent by the input. I propose that the
signature message should commit to the scriptPubKeys of *all* transaction
inputs.
In certain applications like CoinJoin, a wallet has to d
Hi list. I've been a lurker for quite sometime and this is my first post.
The problem I'm addressing is that generally wallet devs construct the tx with
the 2nd output being of the sender as change. This helps chain analysers to
identity addresses and invade the users privacy.
I'm suggesting to