Unconfirmed premine gets swept with newly minted rune

[danpaquin]

This may be resolved on newer versions of ord, but we've observed patterns where a newly etched premine may be swept to the destination address of a newly minted rune, specifically when you:

• Etch a new rune with premine (no address provided)
• Wait for maturation process to complete
• Execute rune mint (with destination address) before etch reveal is confirmed
• The newly etched premine amount may be swept with the freshly minted rune to the destination address

[casey]

Thanks for the report!

I was thinking that this could be due to ord failing to lock the premine output, due to the transaction not having been included in a block and indexed yet.

However, according to the docs for fundrawtransaction, you have to set include_unsafe to true, which is false by default, in order to select unconfirmed transactions.

In any case, we should see if we can reproduce this.