Lit Actions are still heavily in development and things may change. We're grateful for feedback on how to improve the docs and examples!
To start developing with Lit Actions, check out examples here. For an in-depth review of the functionality provided by the Lit Actions SDK, take a look at our API docs.
Ready to jump right in? Quickly learn how you can integrate Lit Actions into your own application:
- Guide: Hello World with Lit Actions
- Guide: Using Lit Actions for Access Control
- Tool: GetLit CLI
- Example Implementation: Fetching Off-Chain Data in a Lit Action
- Example Implementation: Conditional Signing with Lit Actions
Every Lit Action gets executed across Lit’s threshold cryptography network in parallel, meaning the result of each program is independently verified by each node. Once a threshold of nodes have verified the result (more than two-thirds of network participants), the signing or decryption logic defined therein can be executed.
A trivial example would be a Lit Action and associated PKP that checks if a number is prime, only returning a signature if the number is prime. Each node will execute the Lit Action with a submitted input and verify that it meets the required conditions. If it does, the node will provision an independent key share. Only after more than two-thirds of these shares have been collected can the complete signature be formed.
- Blockchain Agnostic: Lit Actions can be used to write data to blockchains using PKPs
- Immutable: Once a Lit Action has been published, it cannot be modified
- Atomicity: Using Mint/Grant/Burn, you can atomically link a PKP to an authorized set of Lit Actions. This method guarantees that a particular PKP can only ever be used to sign data from within the approved set
- Off-Chain Compatibility: Lit Actions can pull in data from off-chain sources natively, without requiring the use of a third party oracle