-
Notifications
You must be signed in to change notification settings - Fork 5
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice initiative to start documentation for this.
There are 2 things that need attention.
RNUportSigner
should probably not be promoted and kept only for compatibility- we need to mention the key protection levels and what their behaviors are.
README.md
Outdated
//Sign a JWT | ||
const exampleJwtPayload = { iss: this.props.address, aud: this.props.address, name: 'test'} | ||
|
||
RNUportSigner.signJwt(this.props.address, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this.props.address
is highly specific and can induce confusion.
I think address
is enough
README.md
Outdated
|
||
// TODO: What to do with the module? | ||
RNUportSigner; | ||
## Basic Signer Usage |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The non-hd signer should be marked as deprecated.
The main reason is that there is no way to recover the keys and that may not be obvious.
README.md
Outdated
rlpEncodedTx, //RLP Encoded eth transaction | ||
'simple' | ||
).then( txSig => { | ||
console.log(sig.r) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the lambda has txSig
param but the logs are using sig.r
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great
No description provided.