Relay Policies

(Psuedo-)Ephemeral Anchors

Context for idea here: https://bitcoinops.org/en/topics/ephemeral-anchors/

Implementation: #23

For first stage deployment, this supports OP_TRUE outputs as a standard output type, and allow the value of these outputs to be below the dust threshold.

Unlike the proper Ephemeral Anchors proposal, this does not require spending of the output in the package setting. This means it doesn't have all the desired anti-pinning properties and contributes to dust, but allows for basic testing of this transaction pattern type. Once V3/package relay is deployed, the rest of Ephemeral Anchors logic can be pulled in.

Annex data support

Implementation: #22

This is a strict subset of Always Look On The Bright Side of the Annex which allows up to 126 WU of data payload over a transaction, in a standard transaction.

This should allow for basic experimentation in specific use-cases, without allowing transaction malleability beyond 129 WU total, since taproot/tapscript signatures only commit to the annex in their own input.