Continuing the discussion about noinput / anyprevout



Summary:

A recent renewed interest in eltoo and clean abstractions for off-chain protocols has led Christian Decker to revisit the "sighash_noinput" proposal (BIP-118) and AJ's "bip-anyprevout" proposal. The open questions that remain to be addressed are general agreement on the usefulness of noinput/ anyprevoutanyscript/ anyprevout, strong support or opposition to chaperone signatures, and the same for output tagging/ explicit opt-in. AJ thinks an important open question missed from this list is whether we really understand the dangers of noinput/anyprevout-style constructions. Regarding the first 3.5 q's, there is general agreement on the usefulness of noinput/ anyprevoutanyscript/ anyprevout, weak opposition for requiring chaperone sigs, and mixed (weak) support/opposition for output tagging. AJ's current thinking is that anyprevout signatures make the address you're signing for less safe, so being able to guarantee that an address can never be signed for with an anyprevout signature is valuable. Receiving funds spent via an anyprevout signature does not involve any qualitatively new double-spending/malleability risks, and output tagging is unnecessary. AJ suggests having a public testnet with fake exchanges/merchants and scheduled reorgs to demo every weird noinput/anyprevout case anyone can think of to work out if any extra code/tagging/whatever is needed to keep those fake exchanges/merchants from losing money. It would also be good to write up the weird cases found in a wiki or paper so people can easily tell if something obvious was missed.


Updated on: 2023-05-23T02:15:33.530879+00:00