Re: [bitcoin-dev] Coinjoin with less steps using ALL|ANYONECANPAY

2023-05-22 Thread Ben Carman via bitcoin-dev
The problem with using ALL|ANYONECANPAY is that you cannot verify beforehand that the other inputs are the inputs you want added to the transaction. Some examples of bad things that could happen: * Coordinator adds its own inputs, you still get your outputs but effectively paid fees for no

[bitcoin-dev] Using OP_VAULT to improve DLCs

2023-01-13 Thread Ben Carman via bitcoin-dev
Hi list, After reading through James's OP_VAULT proposal this week, I had a realization that this can be used for more than a deep cold storage wallet. Instead of vaulting and unvaulting, we can just send to a OP_UNVAULT output. When using OP_UNVAULT if we set the `recovery-spk-hash` to a burn a

Re: [bitcoin-dev] BIP proposal: Anti-fee-sniping protection with nSequence in taproot transactions to improve privacy for off-chain protocols

2021-06-28 Thread Ben Carman via bitcoin-dev
> If nSequence is set it should apply only to the first input of the transaction, if it has multiple inputs. This could have complications with DLCs and dual funded lightning. In both protocols the ordering of the inputs is not know until both parties have revealed all of their inputs, and durin