Re: [bitcoin-dev] Safety of committing only to transaction outputs

2019-05-25 Thread Jeremy via bitcoin-dev
Hi Johnson, As noted on the other thread, witness replay-ability can be helped by salting the taproot key or the taproot leaf script at the last stage of a congestion control tree. I also think that chaperone signatures should be opt-in; there are cases where we may not want them. OP_COSHV is

Re: [bitcoin-dev] Safety of committing only to transaction outputs

2019-05-25 Thread Johnson Lau via bitcoin-dev
> On 25 May 2019, at 4:59 AM, Jeremy wrote: > > Hi Johnson, > > As noted on the other thread, witness replay-ability can be helped by salting > the taproot key or the taproot leaf script at the last stage of a congestion > control tree. > The salt will be published when it is first spent.

[bitcoin-dev] Safety of committing only to transaction outputs

2019-05-24 Thread Johnson Lau via bitcoin-dev
This is a meta-discussion for any approach that allows the witness committing to only transaction outputs, but not inputs. We can already do the following things with the existing bitcoin script system: * commit to both inputs and outputs: SIGHASH_ALL or SIGHASH_SINGLE, with optional