signmessage returns 65-byte signature in unknown format
See original GitHub issueIssue Description
Summary
When using signmessage
a 65-byte (130-hex digits) signature is returned but #1496 says it should be 64 bytes.
Expected behavior
signmessage
returns 64-byte signature
Actual behavior
signmessage
returned 65-byte signature, seems to be prefixed by constant 1f
It also seems to be in some undocumented format since it can not be verified by libsecp256k1
(I’m using the Rust crate).
Is the hash algorithm sha256?
Steps to reproduce
- use
signmessage
API with any message - observe the
sigature
field of returned Json Eclair version: 0.6.2
Environment
Linux, ARM64 openjdk 11.0.9
Issue Analytics
- State:
- Created a year ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
The Magic of Digital Signatures on Ethereum | MyCrypto
The {r, s, v} signature can be combined into one 65-byte-long sequence: 32 bytes for r , 32 bytes for s , and...
Read more >Unable to verify message signed by sol-wallet-adapter
sign message with privateKey; POST signature (to API server); verify signature with stored publicKey. I've attempted to use nodeJS crypto ...
Read more >Difference between Sign Message and Sign Transaction
The output of "Sign Message" is a 65-byte ECDSA signature, and it's not in DER format (can easily be converted).
Read more >Verify the digital signature on a signed email message
Open the digitally signed message. Look at the Signed By status line to check the email address of the person who signed the...
Read more >Documentation - Ethers.js
Returns the transaction with hash or null if the transaction is unknown. ... a common Signature format where the r, s and v...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Gotcha, if you think documenting the code isn’t very important let’s skip it. I’ll update the API doc next time I change it (I tend to batch updates to the API doc and test APIs before I publish), it’s been added to my todo-list.
Decided to draft the bLIP, please take a look. 😃