Re: [bitcoin-dev] [Lightning-dev] CPFP Carve-Out for Fee-Prediction Issues in Contracting Applications (eg Lightning)

2018-12-02 Thread ZmnSCPxj via bitcoin-dev
Good morning Bob, Would `SIGHASH_SINGLE` work? Commitment transactions have a single input but multiple outputs. Regards, ZmnSCPxj Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Sunday, December 2, 2018 11:08 PM, Bob McElrath wrote: > I've long thought about using

Re: [bitcoin-dev] draft proposal: change forwarding (improved fungibility through wallet interoperability)

2018-12-02 Thread Yuval Kogman via bitcoin-dev
Hi, On Sat, 1 Dec 2018 at 05:06, James MacWhyte wrote: > Is the intention that someone would open their non-private wallet, and > choose an option that slowly siphons their funds into a different app? > Yes, that's the idea. And then send them back in a controlled manner. > Why would anyone

Re: [bitcoin-dev] CPFP Carve-Out for Fee-Prediction Issues in Contracting Applications (eg Lightning)

2018-12-02 Thread Bob McElrath via bitcoin-dev
I've long thought about using SIGHASH_SINGLE, then either party can add inputs to cover whatever fee they want on channel close and it doesn't have to be pre-planned at setup. For Lightning I think you'd want to cross-sign, e.g. Alice signs her input and Bob's output, while Bob signs his input