-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
2483d embedded wallets pass #2603
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
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Caution MetaMask internal reviewing guidelines:
|
| The client then assembles these shares and reconstructs the users key in the front-end. | ||
| The client then assembles these shares and reconstructs the user's key in the frontend. | ||
|
|
||
| <!-- The phrase "reconstructs the user's key in the frontend" sounds incorrect and potentially misleading. In an MPC/TSS design, the private key should never be reconstructed client-side. Should this instead say something like: "The client combines the required shares as part of a threshold signing protocol, ensuring that the full private key is never reconstructed or exposed"? Also, can we clarify whether "frontend" refers to the dApp client or a Torus-controlled client environment? --> |
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.
Review comment accidentally committed to documentation
An HTML comment containing a developer review note was left in the documentation. The comment questions whether the preceding text about reconstructing the user's key in the frontend is accurate for an MPC/TSS design, and suggests alternative wording. While HTML comments are hidden from rendered output, this internal review note with suggested rewrites should not be in the committed documentation.
| label: "Compliance, Audits and Trust", | ||
| href: "https://trust.web3auth.io", | ||
| label: "Compliance, Audits and Trust", | ||
| href: "https://trust.web3auth.io", // needs proofing (landing page missing stop) |
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.
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.
indeed -- this note need to become actionable item elsewhere, hence "do not merge" label on this PR
| @@ -0,0 +1,14 @@ | |||
| --- | |||
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.
This PR has "do not merge" label because vercel wont like meta in the single sourced mdx --> need to finalize this ahead of final review
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.
MPC is only supported in MPC Core Kit SDK, which is not documented here due to enterprise plan issues.
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.
It has a different document, just for integration for particular customers.
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.
Yeah, I had run the issue down that far. So, to use this table and make clear for end users -- I would need to know if all the same platforms are supported my this "MPC Core Kit SDK" -- in which case, the platforms column is redundant and can go
| This document provides an in-depth exploration of the technical architecture of the Multi-Party Computation (MPC)-based SDK, this includes the MPC Core Kit SDK. | ||
|
|
||
| The only difference between the SSS-based SDKs and MPC SDKs are that during usage/login MPC SDKs do not reconstruct user private keys. | ||
| <!-- This deserves link to the SDK: which of these docs pages covers the Core Kit SDK? Alt is this is enterprise grade option only, in which case consider importing ./_partials/_sdk-key-model-table.mdx--> |
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.
comments still in play, hence "do not merge" label on this PR
Description
Simplification how the cryptography is presented
Proofs
Applies docs style
DOES NOT - touch images
Issue(s) fixed
Partial fix for 2483 #
Preview
Checklist
External contributor checklist
Note
Updates and streamlines the Embedded Wallets cryptography documentation and enables proper math rendering.
_sdk-key-model-table.mdxand embeds it ininfrastructure/README.mdxinfrastructure/README,mpc-architecture.mdx,sss-architecture.mdx,nodes-and-dkg.mdx, andglossary.mdxto clarify terminology, flows, security assumptions, and protocolsdocusaurus.config.jsand bumpskatexdependency (and lockfile) to support math notationew-sidebar.jsWritten by Cursor Bugbot for commit 13e7748. This will update automatically on new commits. Configure here.