Ready to jump right in? Quickly learn how you can integrate Programmable Key Pairs (PKPs) into your own product:
- Resource: Minting a PKP using the Lit Explorer
- Resource: Testnet Faucet
- Concept: Assigning an Authentication Method (and associated blog post)
- SDK Package: Using PKPs as Wallets
Each Programmable Key Pair (PKP) is a versatile MPC wallet that can be utilized by developers to:
- Provide users of web3 with seamless, "seed-phraseless" onboarding experiences.
- Facilitate transaction execution on blockchains, storage networks, and other state machines.
- Build fully decentralized application backends.
- Blockchain Agnostic: PKPs can be used to sign transactions on any blockchains or state machines using ECDSA for digital signatures. Currently, the SDK provides easy-to-use methods for creating wallets on EVM and Cosmos based chains.
- Programmable: Lit Actions contain the application logic that each PKP should follow. This is useful for defining signing automations, handling authentication, or generating conditional proofs.
- Fault-tolerant: Each PKP is generated collectively by the Lit nodes through a process called Distributed Key Generation (DKG). As a network, this allows Lit to generate a new key-pair where the private key never exists in its entirety.
- Interoperable: Use WalletConnect to connect PKPs to your favorite dApps, just like any other EOA wallet.
Examples and Use Cases
PKPs can be used to power a wide array of potential applications and use cases: