Clarification on signer methods and return types
See original GitHub issuesigner
params are very confusing at the moment.
ES256K signers are expected to produce ECDSASignature objects while Ed25519 signers are expected to produce strings.
The developer is notified of this by an error. See SignerAlgorithm.ts#L28 and SignerAlgorithm.ts#L41
This should be improved. Signers should only produce strings since that way, signing can be externalized and there would no longer be a need to understand all algorithms locally, thus allowing support for many more crypto suites.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Why does Signer use a promise for the address? #263 - GitHub
It has a getAddress method, that returns a Promise and all the classes ... When I import type of Signer from Ethers, it...
Read more >Notary Basics: Determining A Signer's Awareness | NNA
Seek Clarification: If you are unsure if a signer understands your questions, you can ask them to tell you the title of the...
Read more >Signing and Verifying Ethereum Signatures - Yos Riady
Accounts can use their private key to sign a piece of data, returning a signature of that data. Anyone can verify the generated...
Read more >CfnSigningProfile — AWS Cloud Development Kit 2.50.0 ...
A CloudFormation AWS::Signer::SigningProfile . Creates a signing profile. A signing profile is a code signing template that can be used to carry out...
Read more >Signing and Verifying Messages in Ethereum
The sign method calculates an Ethereum specific signature with: ... function recoverSigner(bytes32 message, bytes sig) internal pure returns ...
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 FreeTop 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
Top GitHub Comments
That sounds great 😃 FYI, we are likely to start using the
jose
library to do IPLD object signatures and encryption in Ceramic. But afaik, it should still be possible to verify signatures generated from that with the did-jwt library!🎉 This issue has been resolved in version 4.9.0 🎉
The release is available on:
Your semantic-release bot 📦🚀