> Unfortunately, ACP | SINGLE is trivially pinable [0] (TL;DR: i can just
attach an output paying immediately to me, and construct a tx chain
spending it). We are using ACP | ALL for Revault,
> which is the reason why we need a well laid-out pool of fee-bumping UTXOs
(as you need to consume them en
Erik, I am sorry, I have little knowledge about proof-of-burn, I never found it
interesting up until now. Some of your recent claims seem quite strong to me
and I'd like to read more.
Forgive me if this has been mentioned recently, but is there a full
specification of the concept you are referr
best writeup i know of is here:
https://en.bitcoin.it/wiki/Proof_of_burn
no formal proposals or proofs that i know of.
On Fri, May 28, 2021 at 10:40 AM befreeandopen
wrote:
>
> Erik, I am sorry, I have little knowledge about proof-of-burn, I never found
> it interesting up until now. Some of y
> Oh yes, I should have mentioned this pinning vector. The witnessScript I've
> in mind to make secure that type of chain of transactions would be one MuSig
> key for all contract participants, where signature are committed with
> SIGHASH_ANYPREVOUT | SIGHASH_IOMAP, one pubkey per participant to
