This message relates to an edge case which BIP322 only partially solves, and
that is Proof of Payment.
When you make a transaction to any business, it keeps the transaction in its
records and generates an invoice so anyone can verify the transaction took
place.
When you do a P2P transaction, w
Since I mailed the original scheme, some people have suggested to me that this
delegation scheme can be written in TapScript, to avoid revealing the unspent
public keys. I think that is a good idea.
Here is a very helpful slideshow about implementing Multisig scripts in Taproot
by Jimmy Song[1]
(Note: I'm going to stick with this thread for all proposals for BIP322
polishing, not just delegation - unless the subject matter changes radically as
other people discuss it.)
Instead of the admittingly complicated scheme using transactions, I've created
one that utilizes multisig to make the
[A similar message was posted in the Bitcointalk BIP322 thread.]
OK, I just figured out how to solve the delegation problem. It builds on Jeremy
Rubin's transaction delegation post which I linked to a few days ago.
In BIP322, there is a [planned] provision for some person to delegate signing
to
