Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node crashes when calling "blindrawtransaction" on a 0-valued non-OP_RETURN output #1235

Open
apoelstra opened this issue Apr 24, 2023 · 3 comments
Assignees
Labels

Comments

@apoelstra
Copy link
Member

elementsd: blind.cpp:621: int BlindTransaction(std::vector<uint256>&, const std::vector<uint256>&, const std::vector<CAsset>&, const std::vector<long int>&, std::vector<uint256>&, std::vector<uint256>&, const std::vector<CPubKey>&, const std::vector<CKey>&, const std::vector<CKey>&, CMutableTransaction&, std::vector<std::vector<unsigned char> >*): Assertion `rangeresult' failed.

We don't really care about blindrawtransaction but we probably shouldn't crash.

@delta1
Copy link
Member

delta1 commented May 3, 2023

Is it fine to return an error, or should it be possible to blind the 0-valued non-OP_RETURN output ?

@apoelstra
Copy link
Member Author

@delta1 fine to return an error. Consensus rules forbid having a blinded 0-valued non-RETURN output.

@delta1
Copy link
Member

delta1 commented May 3, 2023

Cool, I'll put in a PR for that when I have a spare cycle

@delta1 delta1 self-assigned this Sep 17, 2024
@delta1 delta1 added the bug label Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants