Repository navigation
NUT-11: hash blinded outputs in SIG_ALL - #461
Closed
SatsAndSports wants to merge 2 commits into
Closed
SatsAndSports wants to merge 2 commits into
SatsAndSports wants to merge 2 commits into
Conversation
41 tasks
Author
|
I've decided to close this PR that I made I'm not against hashing the blinded outputs, and am happy for anyone else to advocate for this. It's just that I now have another solution (Unpoisonable Blinded Outputs) that fixes the poison issue directly, allowing us to keep using adverserial multi-party e-cash transactions (e.g. Spilman with non-interactive setup) |
This file contains hidden or 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
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.
Summary
SIG_ALLconstruction in NUT-11: typed, length-framed SIG_ALL message over output hashes #404SHA256(B_)instead of revealing each raw blinded point to the signerB_Point encoding
SHA256is applied to the exact canonical raw point encoding decoded from theB_hex string. For secp256k1 this is the 33-byte compressed SEC1 encoding,including the
0x02or0x03parity prefix. It is not the 32-byte x-onlyrepresentation and not the UTF-8 hexadecimal representation.
Including parity ensures that
B_and-B_have distinct commitments eventhough they share an x-coordinate. Defining the preimage as the canonical raw
encoding also extends naturally to other point types.
Verification
npx prettier@3.9.1 --check 11.md tests/11-test.md