# Wallet Infrastucture Comparisons | | Web3Auth | Coinbase MPC | Binance Extension | Binance Custody | ZenGo Wallet | Particle Network | Unipass | | --------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | ----------------- | ----------------------- | ------------------------- | --------------------| --------------------| | SSS vs Full MPC vs Smart Contract Wallet | Both/either | Full MPC | SSS | Full MPC | Full MPC | MPC | Smart Contract Wallet with MPC | | Wallet Infrastucture or Wallet | Wallet Infrastucture | Wallet | Wallet | Walllet | Wallet | Wallet | Wallet | | Schemes used | GG19, GG20 DKLS19, FROST | FROST, DKLS18 | SSS | GG19 | Lindell18 | GG20/19 (Unknown for Solana) | Unknown | | Signature Support | ECDSA, EDDSA, Schnorr | ECDSA, EDDSA | All | ECDSA | ECDSA, (EDDSA not on wallet ) | ECDSA, EDDSA | Depends on chain | Key management setup: i.e. restricted to 2/2 or is >2/3 enabled | Either | 2/2 "Semi-custodial" | >2/3 | >2/3 | 2/2 "Semi-custodial" | 2/2 "custodial" TEE + Particle Network owns /can access share | 2/2 "semi-custodial" | | Signature Performance | Depending on scheme, GG19/GG20 globally, for 2 party, 4-7s pre-compute on browser, on application level 2-3s pre-compute. DKLS19 is a lot faster at ~1.5-2.5s | Unknown | Instant | 3-4 party 8s precompute | 2 party 2-3s | 3-4 party 8s precompute | 1 transaciton/block timing | | Regionally distributed infrastructure for performance | Yes | Eventually | Yes | No | No | Unknown | Yes | | Gassless | Can be built on top | Yes | No | Yes | No | No | Yes|
Last changed by  
 
Web3Auth
Torus Labs
795

Read more

Web3Auth Integration Questionaire

This document lays out a series of questions that helps identify the design principles and choices that fit the ideal key management architecture for your wallet or application.

7/27/2023
Web3Auth Full MPC & Application Technical Interaction Document v1.5

This document is a technical description of Web3Auth’s MPC infrastructure and its interactions with applications. Its a high-level document, Web3Auth reserves the right to make changes to this document as needed.

7/25/2023
Web3Auth Full MPC User Key Architecture (tKey v2)

This document is a technical description of Web3Auth’s User Key Architecture in our full MPC solution. Its a high-level document, Web3Auth reserves the right to make changes to this document as needed.

6/28/2023
tKey - User-centric threshold key management

Existing private key management solutions have come a long way in terms of user experience. However, many of these solutions make tradeoffs with reduced guarantees on custody and censorship-resistance. For example, password-manager key management solutions can restrict user access by refusing to return the encrypted key from their servers. Which then ultimately derives down to resorting to the usual approach of protecting private keys via redundant backups. We propose a model of key management, tKey, that uses Shamir Secret Sharing to achieve this without sacrificing user experience, while retaining end-user autonomy and control over the private key. tKey manages private keys using the user's device, private input, and wallet service provider. As long as a user has access to 2 out of 3 (2/3) of these shares, they will be able to retrieve their private key. We describe the architecture of tKey and detail several core user flows for onboarding, key recovery, and device management. To achieve these flows, tKey leverages heavily on its service provider and its properties, which could be a centralized provider or something distributed, such as the Torus Network. tKey also depends on a persistent storage layer (e.g. IPFS, Arweave, Sia) to store encrypted metadata. tKey Overview The user starts by generating (client-side) a 2 out of 3 (2/3) Shamir secret sharing, $f_0(x) = a_0 + a_1x$, with three shares: $f_0(1), f_0(z_1), f_0(z_2)$ where $z_1,z_2 \in \mathbb{Z}_q$

7/6/2022
Read more from Web3Auth
Published on HackMD