Skip to content

Commit

Permalink
docs: update smart-account-signer
Browse files Browse the repository at this point in the history
small typo fix
  • Loading branch information
Shenghu-Yang authored Jan 11, 2025
1 parent 18a9228 commit 017762f
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion site/pages/concepts/smart-account-signer.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ Multi-Party Computation (MPC) Signers split the Owner Account private key into k

Valid signatures do not always require all shares to sign a transaction. MPC Signers can set a threshold, requiring a certain number of shares for a signature to be valid. Common configurations are 2 of 2 shares or 2 of 3 shares. By requiring multiple shares, MPC models mitigate the risks associated with a single key being compromised.

Some MPC signers provide recovery services in which key share(s) are backed up in the service provider’s cloud, on the end user’s device, or in the end user’s cloud (e.g. iCloud or Google Drive). When evaluating an MPC provider, it’s important to under where each key share is stored.
Some MPC signers provide recovery services in which key share(s) are backed up in the service provider’s cloud, on the end user’s device, or in the end user’s cloud (e.g. iCloud or Google Drive). When evaluating an MPC provider, it’s important to understand where each key share is stored.

**Example**: Privy, Fireblocks MPC, Portal, Capsule, WalletKit

Expand Down

0 comments on commit 017762f

Please sign in to comment.