tKey is the underlying SDK used to implement Web3Auth Plug n Play. This package can also be used to self host Web3Auth in your own system. tKey stands for Threshold Key, which refers to the management keys & shares generated using threshold cryptography.
The tKey SDK manages private keys by generating shares of it using Shamir Secret Sharing. For example, for a 2 out of 3 (2/3) setup, we give the
user three shares: ShareA, ShareB, and ShareC.
- ShareA is stored on the user’s device: Implementation is device and system specific. For example, on mobile devices, the share could be stored in device storage secured via biometrics.
- ShareB is managed and split across Web3Auth's Auth Network, accessed by an OAuth login provider that a user owns.
- ShareC is a recovery share: An extra share to be kept by the user, possibly kept on a separate device, downloaded or based on user input with enough entropy (eg. password, security questions, hardware device etc.).
Similar to existing 2FA systems, a user needs to prove ownership of at least 2 out of 3 (2/3) shares, in order to retrieve his private key.
For more information, check out the technical overview. Before integrating you can also check out the example for tKey.
To use the SDK in your application, please refer to our SDK Reference in Web3Auth Documentation
- Typescript compatible. Includes Type definitions
- Fully composable API
- Module support (Include only those modules which you require)
- Audited
| Packages | @latest Version |
Size | Description |
|---|---|---|---|
| 🐉 tKey Standard Package | |||
@tkey-mpc/default |
 |
 |
Bundles Core and Modules into one importable package |
| 🏠 Core | |||
@tkey-mpc/core |
 |
 |
Core functionalities for creating a tkey |
| 🐕🦺 Service Provider | |||
@tkey-mpc/service-provider-torus |
 |
 |
@service-provider-base with DirectAuth functionality |
| 🗳 Storage Layer | |||
@tkey-mpc/storage-layer-torus |
 |
 |
get/set metadata for various shares |
| 🔌 Modules | |||
@tkey-mpc/chrome-storage |
 |
 |
Add/remove a share from chrome extension storage |
@tkey-mpc/web-storage |
 |
 |
Add/remove a share from local and file storage |
@tkey-mpc/security-questions |
 |
 |
Add/remove a security question and password as a share for tkey |
@tkey-mpc/share-transfer |
 |
 |
Transfer share from another device |
@tkey-mpc/seed-phrase |
 |
 |
Store and use seedphrases on metadata |
@tkey-mpc/private-keys |
 |
 |
Store extra private keys on tKey metadata |
@tkey-mpc/share-serialization |
 |
 |
Import/export a share from tKey |
| 🐉 Low-Level | |||
@tkey-mpc/common-types |
 |
 |
Shared TypeScript Types |
- This package requires a peer dependency of
@babel/runtime - Node 18+
npm install
npm run pack:lerna
Each sub package is distributed in 3 formats
esmbuilddist/<MODULE_NAME>.esm.jsin es6 formatcommonjsbuilddist/<MODULE_NAME>.cjs.jsin es5 formatumdbuilddist/<MODULE_NAME>.umd.min.jsin es5 format without polyfilling corejs minified
By default, the appropriate format is used for your specified usecase You can use a different format (if you know what you're doing) by referencing the correct file
The cjs build is not polyfilled with core-js. It is upto the user to polyfill based on the browserlist they target
CDN's serve the non-core-js polyfilled version by default. You can use a different
jsdeliver
<script src="https://cdn.jsdelivr.net/npm/<MODULE_NAME>"></script>unpkg
<script src="https://unpkg.com/<MODULE_NAME>"></script>This is a plugin that works only on the client side. So please register it as a ssr-free plugin.