MIN_STANDARD_TX_NONWITNESS_SIZE prevents efficient spending of P2A outputs #31155

1. 
   petertodd commented at 5:47 pm on October 25, 2024: contributor

   Please describe the feature you’d like to see added.

   The most efficient way to spend a single P2A output to an OP_RETURN results in a transaction 61 bytes in size, below the 65 byte limit enforced by MIN_STANDARD_TX_NONWITNESS_SIZE. For example:

   01000000017989c51d11e9e1e6aa634d471e31900141fe44bd491bcb5996f948b9039b232e0000000000ffffffff010000000000000000016a00000000

   This transaction should be standard.

   Is your feature related to a problem, if so please describe it.

   No response

   Describe the solution you’d like

   No response

   Describe any alternatives you’ve considered

   No response

   Please leave any additional context

   No response

2. petertodd added the label Feature on Oct 25, 2024
3. 
   jonatack commented at 6:15 pm on October 25, 2024: member

   See #26265 (merged, above 64 bytes allowed) and alternative #26398 (only 64 bytes disallowed).
4. maflcko removed the label Feature on Oct 28, 2024
5. maflcko added the label TX fees and policy on Oct 28, 2024
6. bitcoin deleted a comment on Oct 28, 2024

Contributors
petertodd jonatack

Labels
TX fees and policy