-
Notifications
You must be signed in to change notification settings - Fork 7
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
Create a stable and reviewed version of signed message #779
Comments
Proposal based on https://dbdiagram.io/d/60decc3d0b1d8a6d3963df6f
Questions
|
"Capture App" might be a candidate, and let's discuss it in the product channel. I also suggest moving
|
I got |
Updated example
|
@shc261392 One small question: Do you know what is Sean's design concept to use
instead of
|
No idea, I guess it's just that key with dots are not accessible with JavaScript dot notation so it makes the syntax of handling these objects messier. Have to use bracket to access the property instead. |
Signature example Android (Exodus 1, Android 9)Signed Message (string)
Signed Message (parsed)
Signature
Wallet address
iOS (iPhone 7 Plus, iOS 14)Signed Message (string)
Signed Message (parsed)
Signature
Wallet address
|
Concept
Currently, there are two version of signed messages created from Capture App.
Pre 0.34.2 example:
0.34.2 or later example:
Reason/Hypothesis
Signature is not something that we'd like to see it changes from time to time. We should make sure the current signature contains all the information we want, and make it stable and lasting.
┆Issue is synchronized with this Asana task by Unito
The text was updated successfully, but these errors were encountered: