0

Talking to just one node (baby steps), I want to call /v2/signer/verifymessage giving the output of lncli signmessage "Hello, Jessica". On the alice node on Polar, I get:

d9aa91ggo54ouho9axcw3itokb5u697tigi1r8o1kq4qkx87acduoz5f5wnxyts8dt8emhie9r3gnkxkwo5ogzo5xwsrfkhzpg5qnnmh

How do I encode this to send over to /v2/signer/verifymessage? I'm only slightly familiar with low-level string manipulation. The api says to send bytes, but what format (hoping this question makes sense)?

If it helps, I'm comfortable with Ruby, but I can probably figure it out if I see examples in JS or Python.

1 Answer 1

0

Guggero from lightningcommunity.slack.com told me:

The v2 signmessage isn‘t used by the CLI and the signature format is also different. Look at the v1 signmessage, that signs with the node key and is used by lncli. The v2 here isn‘t really an upgrade, the two signmessage RPCs have completely different use cases. Unfortunately that‘s not very apparent when only looking at the REST URLs

So I shouldn't be using v2 if I am to compare the results of lncli signmessage.

True enough, when you use v1 you get the expected signature.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.