-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: sign raw bytes #1332
fix: sign raw bytes #1332
Conversation
SignContent::Message(_) => match signature { | ||
MultiSignature::Sr25519(a) => hex::encode(a), | ||
MultiSignature::Ed25519(a) => hex::encode(a), | ||
MultiSignature::Ecdsa(a) => hex::encode(a), | ||
}, |
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.
I don't think that this is right
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.
Is it conceptually wrong, or is there a better way to write it? I struggle to find another solution.
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.
- I think that it is not a good pattern to turn a return type from
MultiSignature
toString
- Are you sure that this should be just the bare signature that is returned, not
MultiSignature
? How the users are going to tell the difference between different signature schemes? In case of a transactionMultiSignature
is returned
Purpose
Fixing #1014, #997
Scope
Expect messages to be wraped in
<Bytes>...</Bytes>
. It works like that in polkadotjs extension and StyloScreenshots
Signing up to https://polkadot.polkassembly.io/