Since unspendable outputs can’t be spent, there is no threshold at which it would be uneconomic to spend them.
This primarily targets transaction outputs with OP_RETURN
, and allows funding of data-only transactions with "fundrawtransaction"
.
Since unspendable outputs can’t be spent, there is no threshold at which it would be uneconomic to spend them.
This primarily targets transaction outputs with OP_RETURN
, and allows funding of data-only transactions with "fundrawtransaction"
.
utACK
Pretty obvious fix, regardless of what we do with the IsDust() code in the future re: refactoring.
{
and }
Since unspendable outputs can't be spent, there is no threshold at which it would be uneconomic to spend them.
This primarily targets transaction outputs with `OP_RETURN`.
---
Initially based on:
commit 9cf0ae26350033d43d5dd3c95054c0d1b1641eda
Author: zathras-crypto <zathrasc@gmail.com>
Date: Wed Mar 25 02:04:02 2015 -0700
Changes:
- cherry-picked on top of bitcoin:master
- added RPC test for fundrawtransaction
utACK
minor nit: one line if, please remove { and }
We don’t actually have a coding style rule that says that.