docs(nut14): clarify pubkey-less HTLC spends on preimage alone#396
Open
robwoodgate wants to merge 1 commit into
Open
docs(nut14): clarify pubkey-less HTLC spends on preimage alone#396robwoodgate wants to merge 1 commit into
robwoodgate wants to merge 1 commit into
Conversation
6b4d9c7 to
809f62e
Compare
This comment was marked as resolved.
This comment was marked as resolved.
809f62e to
2ea80f1
Compare
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
Clarifies that an HTLC with no
pubkeystag is spendable by the preimage alone, with no signature required.The Receiver Pathway currently says the receiver provides BOTH the preimage and a Locktime MultiSig signature, which reads as if a
pubkeystag is mandatory. But an HTLC locks to a hashlock inSecret.data(not a pubkey), so thepubkeystag is optional — when it is absent there are no keys to sign and the preimage alone should spend the proof.This adds a one-line
**NOTE:**to the Receiver Pathway, mirroring the existing note on the Sender Pathway that covers the absent-refund/locktimecases.Motivation
The absent-
pubkeyscase is currently undefined, so implementations diverge: the reference implementation (CDK) treats an empty pubkey list as a zero-signature receiver pathway and spends on the preimage alone, which is the behaviour this note documents.