Remove dust avoidance for OP_RETURN output #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
OP_RETURN outputs don't require a non-dust output value. If a non-zero value is put into the output, the amount becomes unspendable and lost forever.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
OP_RETURN outputs don't require a non-dust output value. If a non-zero
value is put into the output, the amount becomes unspendable and lost
forever.
I've tested the change with a small html file which I have not included in the pull request at this time. The results of the test can be found on memo.cash by searching for "sorry dave" and and viewing the tx on one of the block explorers.
One concern: the datacash code allows for arbitrary scripts to be passed in. If something other than a dataout type script is given, then the zero value output would cause the tx to be rejected.