-
Notifications
You must be signed in to change notification settings - Fork 11.6k
Show Transaction Hash of Ledger in MultiSig Toolkit #19965
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
🚀
"@radix-ui/react-slot": "^1.1.0", | ||
"@radix-ui/react-tabs": "^1.1.0", | ||
"@tanstack/react-query": "^5.50.1", | ||
"blake2b": "link:@noble/hashes/blake2b", |
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.
why are we aliasing blak2b like this?
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 good (other than the blake2b link in package.json)
Description
Show the Transaction Hash the user sees on the Ledger as an option for the User in the Multisig Toolkit.
Currently, any user signing a Sui transaction with a ledger has a hard time verifying the transaction they are signing is the transaction they expect to sign.
This feature provides a way for the user to verify the Transaction Hash presented by the Ledger from the MultiSig Toolkit Interface
Test plan
Tested Locally
created transaction:
Compute Transaction hash in multisig toolkit:
0x46ac3b8e4f61981f7c016e0bcb53cc2bbd4bc52f8d5e51e335e0a5dc15ab9cb5
Verify same hash Ledger shows
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.