-
Notifications
You must be signed in to change notification settings - Fork 581
feat: wallet SDK better flow, mitm protection #19477
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
feat: wallet SDK better flow, mitm protection #19477
Conversation
| sharedKey, | ||
| }); | ||
| } catch { | ||
| // Failed to derive key, skip this wallet |
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.
Logs?
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.
console.log is forbidden by the linter and I'm reluctant to add an opinionated logger here (we have a lot of that as it is...)
| const EMOJI_ALPHABET = [ | ||
| '🔵', | ||
| '🟢', | ||
| '🔴', |
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.
wow
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.
You'll love it
| # Wallet SDK Integration Guide for Third-Party Wallet Developers | ||
|
|
||
| This guide explains how to integrate your wallet with the Aztec Wallet SDK, enabling dApps to discover and interact with your wallet implementation. | ||
|
|
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.
Thanks claude
Improved discovery on the SDK: * Avoid "connect" messages and handle everything on the discovery * Hash the derived shared key and expose it (independently) at the app and extension levels, so the user can visually inspect they're connected to the expected wallet Co-authored-by: thunkar <gregojquiros@gmail.com>
1d85840 to
49a5954
Compare
Flakey Tests🤖 says: This CI run detected 2 tests that failed, but were tolerated due to a .test_patterns.yml entry. |
Improved discovery on the SDK: * Avoid "connect" messages and handle everything on the discovery * Hash the derived shared key and expose it (independently) at the app and extension levels, so the user can visually inspect they're connected to the expected wallet
Improved discovery on the SDK: