Skip to content
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.

Sign up for GitHub

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

Jump to bottom

wallet connect: use a separate key for ecdh #748

Open
shamilovtim opened this issue Jul 13, 2024 · 0 comments · May be fixed by #964
Open

wallet connect: use a separate key for ecdh #748

shamilovtim opened this issue Jul 13, 2024 · 0 comments · May be fixed by #964
Assignees
@shamilovtim
Milestone
Web5 Connect

Comments

@shamilovtim
Copy link
Contributor

Right now wallet connect uses the same key for ecdh, signing, verification and impersonation. This should be split up in the future so that a unique key is used for ecdh.
@shamilovtim shamilovtim mentioned this issue Aug 5, 2024
Merged
@shamilovtim shamilovtim self-assigned this Aug 9, 2024
@shamilovtim shamilovtim moved this to Backlog in Web5 Roadmap Aug 9, 2024
@shamilovtim shamilovtim moved this from Backlog to Up Next in Web5 Roadmap Aug 9, 2024
@shamilovtim shamilovtim moved this from Up Next to Done in Web5 Roadmap Oct 24, 2024
@shamilovtim shamilovtim linked a pull request Oct 24, 2024 that will close this issue
add prerequisites for expansion of connect flow #964
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shamilovtim shamilovtim

Labels
None yet
Projects
None yet
Milestone
Web5 Connect
Development

Successfully merging a pull request may close this issue.

add prerequisites for expansion of connect flow decentralized-identity/web5-js
1 participant
@shamilovtim