In the 29.0 release-note, ephemeral dust are described as:
Ephemeral dust is a new concept that allows a single
dust output in a transaction, provided the transaction
is zero fee. In order to spend any unconfirmed outputs
from this transaction, the spender must also spend
this dust in addition to any other desired outputs.
In other words, this type of transaction
should be created in a transaction package where
the dust is both created and spent simultaneously.
Does it mean that given a 0-fee transaction with 2 outputs: ephemeral dust output & CSV-locked output. It’s impossible to spend the dust anchor alone? Why?
If I try on regtest, the parent transaction always fails with "dust" error.
For example, the following package fail:
parent:
03000000000101a7eaabba2d0413cc97c1429e7047c5ea64d0cf5d33b4cfb2900a8503430126cc0000000000ffffffff02204e000000000000225120509793bf1a1427fe1798e30912fa6a0b131251caee19c1f0854f82e2db289db600000000000000000451024e73014036a43b2e755960ec0833368baa81b6f98002bf4af95c28ab1c686129e55289295f3de4fbce2d85e9bf14b78c4d213e1c9d0fe610a2f1c521c753a78916f29f4300000000
child
03000000000102e4a961990401ecbc96f4cb221d87dd3955ed44e14bbdbb06ee53c459853ac0cf0100000000ffffffffc729cef83b41118840cad7c97e30c19e73daefa46ad237a6911604e563154a250100000000ffffffff016685010000000000225120f1bb13933f39b04f10e232025f823aaa37c628797f34780e0bcd3eda3b37241e0001407a694df2f356f78360bb86ee77d5a4ec47759dca8e7f31d887e166f46c9ee5db6bb6e81db7a1846a8eaedcdd94574619316ff3716f225f52aafaa1f3dff40fe400000000
