Calling signmessage returns an NotSupported instead of forwarding call to RPC - #740
Merged
Merged
Conversation
cdecker
force-pushed
the
fix/739-signmessage-unsupported
branch
from
September 4, 2026 14:59
289a451 to
7d2d4cc
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
2 participants
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.
Problem
signmessagenever returns, and takes the node's signing down with it.Change
Reject the RPC in
WrappedNodeServer::sign_messagewithUnimplemented, before it can reach lightningd, avoiding a JSON-RPC call.Test plan
test_node_signmessage_rejectedasserts the call fails fast and that an invoice still mints afterwards, i.e. the hsmd queue is intact.Fixes #739