0
I am familiar with Bitcoin's model, but a complete noob in real-world details. I am entertaining the idea of a service that receives transactions (A->B) and "wraps" or completes them to include (A->B & B->C).
Is it possible to create a transaction requiring 2 wallets to participate?
For example, to create a transaction sending coins from Alice to Bob, and from Bob to Charlie?
I had in mind a process where Alice creates the first half-baked transaction (Alice -> Bob), send it to Bob, Bob "adds" its piece (Bob -> Charlie), and the result is a valid transaction.
Obviously, the (Alice -> Bob) part must not be reusable by anyone else.
Can that be achieved? How? What's a good starting point / alternatives?
not sure I got it, what would be the difference to a multisig spend? Is the difference the reverse order? I don't need a redeem script with lighthouse? – pebwindkraft – 2017-05-05T06:54:18.597
Thanks! While I am still fuzzy on the details, it's certainly a better starting point :) – UriCS – 2017-05-05T12:31:17.400
@pebwindkraft A multisig output only allows a spend if enough signatures agree. In the example above, Alice could defect and send her money to David before Bob signs the transaction. However, this would cause the combined Alice-Bob transaction to fail, so the property the OP asked for still holds. – Nick ODell – 2017-05-05T17:25:26.860