While I admit I haven’t analyzed the feasibility, I want to throw one additional design consideration into the ring.
Namely, it would ideally be trivial, at the p2p protocol layer, to relay a transaction to a full node without knowing exactly which input transaction that full node has in its mempool/active chain. This is at least potentially important for systems like lighting where you do not know which counterparty commitment transaction(s) are in a random node’s mempool and you should be able to describe to that node that you are spending then nonetheless. This is (obviously) an incredibly nontrivial problem both in p2p protocol complexity and mempool optimization, but it may leave SIGHASH_NOINPUT rather useless for lighting without it. The least we could do is think about the consensus design in that context, even if we have to provide an external overlay relay network in order to make lighting transactions relay properly (presumably with miners running such software). Matt > On Jul 9, 2020, at 17:46, Anthony Towns via bitcoin-dev > <bitcoin-dev@lists.linuxfoundation.org> wrote: > > Hello world, > > After talking with Christina ages ago, we came to the conclusion that > it made more sense to update BIP 118 to the latest thinking than have > a new BIP number, so I've (finally) opened a (draft) PR to update BIP > 118 with the ANYPREVOUT bip I've passed around to a few people, > > https://github.com/bitcoin/bips/pull/943 > > Probably easiest to just read the new BIP text on github: > > https://github.com/ajtowns/bips/blob/bip-anyprevout/bip-0118.mediawiki > > It doesn't come with tested code at this point, but I figure better to > have the text available for discussion than nothing. > > Some significant changes since previous discussion include complete lack > of chaperone signatures or anything like it (if you want them, you can > always add them yourself, of course), and that ANYPREVOUTANYSCRIPT no > longer commits to the value (details/rationale in the text). > > Cheers, > aj > > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev _______________________________________________ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
