Summary: Lit Protocol is a decentralized key-management and private-compute network for developers building wallets, AI agents, bridges, vaults, and user-owned-data applications. In the current docs pass, the strongest primary materials are centered on the “Lit Chipotle” product/docs stack, which frames Lit as a programmable KMS combining a TEE enclave, on-chain permissions on Base, and immutable IPFS-hosted Lit Actions.
What it does:
Provides programmable key management for wallets and applications via Programmable Key Pairs (PKPs) that can sign messages, transactions, and arbitrary data
Runs immutable JavaScript “Lit Actions” from IPFS, letting builders fetch external data, encrypt/decrypt secrets, and produce signed outputs tied to specific code and keys
Uses on-chain accounts, groups, and scoped API keys on Base to control which actions can use which PKPs, enabling different SaaS vs self-sovereign operating postures from the same system
Emphasizes TEE-based execution, attestation, and Zero-Trust TLS so developers can verify they are talking directly to an attested enclave rather than a generic hosted API edge
Ships SDKs, examples, and docs for integrating signing, encryption, and private-compute workflows into crypto-native and agentic applications
Key claims:
Homepage positions Lit Protocol as the decentralized network for managing keys and secrets, with use cases spanning AI agents, blockchain interoperability, crypto wallets, and user-owned data
Official architecture docs say Lit Chipotle is built from three layers: a TEE enclave for sensitive operations, on-chain authorization state on Base, and immutable Lit Actions stored on IPFS
Lit Actions docs say actions can sign data, encrypt/decrypt secrets, make arbitrary HTTP requests, and return proofs whose integrity is tied to a PKP and immutable IPFS code
Security docs claim the TLS private key is generated inside the TEE and never leaves it, so a valid verified TLS connection terminates inside the enclave rather than a proxy or intermediary
Public GitHub materials describe Lit as providing decentralized signing and wallet management, decentralized encryption/decryption, and private compute sealed via TEEs
Whitepaper: No single canonical whitepaper or litepaper was found in this pass. The strongest primary materials were Lit’s homepage, current developer docs, architecture/auth/verification docs, Lit Actions docs, and public GitHub repositories; see ../whitepapers/lit-protocol-primary-sources-2026-04-25.md.