So it did not go unnoticed 😅

Reply to this note

Please Login to reply.

Discussion

What can I say, I'm an ASS man. 🍑

Jokes aside. Just trying to understand this.

So I can receive a thing that let's me sign for something but the signature is invalid until the sender of the thing adds their own signature.

Is that what I am reading here?

I was going to try to follow up with an example using cashu, but if the mint is the signature jssuer, then any "swap" thing must be between you and the mint right?

What is a practical example here?

I didn't want to give my nsec to play with the GM protocol. So I don't get that either.

This would allow me to defer the signing of something to someone else.

Like allowing a third party to sign a penalty transaction for a p2p exchange trade.

So I imagine:

Two parties agree to trade 1 BTC for $1M.

They create a multisig address and just like lightning, they first setup refund transactions, use this protocol to partially sign them and give this to an Arbiter.

The benefit here is that the arbiter cannot claim that the signatures were leaked if something unexpected happened because it requires the arbiters signature to become valid.

Now the deposit is made.

Then if the trade is successful, they collaboratively spend as appropriate.

If there is a dispute, then the arbiter decides who gets the 1BTC and releases the funds in the appropriate direction.

If combined with a timelock, then the dispute transactions can include a fee for the arbiter. Nice.

...... Or am I misunderstanding completely?