Re: [bitcoin-dev] BIP 118 and SIGHASH_ANYPREVOUT

2020-08-04 Thread ZmnSCPxj via bitcoin-dev
Good morning Matt, > Hmm, apologies that little context was provided - this was meant in the > context of the current crop of relay-based attacks that have been discovered. > As we learned in those contexts, “just handle it when it confirms” doesn’t > provide the types of guarantees we were hop

Re: [bitcoin-dev] BIP 118 and SIGHASH_ANYPREVOUT

2020-08-04 Thread Matt Corallo via bitcoin-dev
Hmm, apologies that little context was provided - this was meant in the context of the current crop of relay-based attacks that have been discovered. As we learned in those contexts, “just handle it when it confirms” doesn’t provide the types of guarantees we were hoping for as placing commitmen

Re: [bitcoin-dev] BIP 118 and SIGHASH_ANYPREVOUT

2020-08-04 Thread Christian Decker via bitcoin-dev
> Ah, right. > > A feasible attack, without the above, would be to connect to the > fullnode of the victim, and connect to miners separately. Then you > broadcast to the victim one of the old txes, call it tx A, but you > broadcast to the miners a *different* old tx, call it B. The victim > react