Lit Protocol primary-source snapshot
Fetched: 2026-04-25 UTC
1) Official homepage
Source: https://www.litprotocol.com/
Selected excerpts from the official site:
Unlock Autonomy for Wallets. User Data. Agents. Bridges. Vaults.
Lit Protocol is the decentralized network for managing keys and secrets.
Join the builders using programmable signing and encryption to power AI agents, blockchain interoperability, crypto wallets, and user-owned data.
Additional signals from the homepage:
- Homepage frames Lit around programmable signing/encryption infrastructure rather than a token-only or app-only story
- Official copy leans heavily into agentic, cross-chain, and private-data use cases
- The current marketing surface appears to emphasize developer primitives and integrations over a classic protocol whitepaper narrative
2) llms.txt documentation index
Source: https://developer.litprotocol.com/llms.txt
Selected excerpts/signals from the docs index:
Authentication Model
Security & Verification
Overview — Lit Actions are immutable JavaScript programs stored on IPFS and executed by the Lit network.
Additional signals from the docs index:
- The docs surface is organized around architecture, auth, verification, pricing, dashboard/API workflows, and Lit Actions rather than a single monolithic whitepaper
- The index shows the current primary source of truth is strongly docs-driven, with clear technical pages for security, governance boundaries, and execution flow
3) Official architecture overview
Source: https://developer.litprotocol.com/architecture/index
Selected excerpts from the docs:
Lit Chipotle is built on three composable layers that each handle a distinct concern.
TEE Enclave (Phala / dstack)
On-Chain Permissions (Base)
Lit Actions (IPFS)
Additional signals from the docs:
- The architecture page is unusually explicit about where trust boundaries sit: TEE enclave, Base smart contracts, and IPFS-hosted immutable code
- Lit’s current docs present “self-sovereign vs SaaS” as a configuration outcome rather than separate products or modes
4) Authentication model docs
Source: https://developer.litprotocol.com/architecture/authModel
Selected excerpts from the docs:
How accounts, API keys, PKPs, groups, and the TEE root key compose into a programmable KMS
There are no “modes.” Self-sovereign vs SaaS is not a toggle — it’s an emergent property of how you configure the same system.
Immutable JS code pinned to IPFS, identified by its CID.
Additional signals from the docs:
- Auth model documentation shows Lit thinking like a programmable key-management/control-plane vendor, not only a decentralized network in the abstract
- Group-scoped permissions and account-wide structural permissions are documented in enough detail to evaluate operational blast radius and trust posture
5) Lit Actions docs
Source: https://developer.litprotocol.com/lit-actions/index
Selected excerpts from the docs:
Lit Actions are immutable JavaScript programs stored on IPFS and executed by the Lit network.
They can sign data, encrypt and decrypt secrets, and make arbitrary HTTP requests — all in a verifiable, trustless way.
When a Lit Action retrieves data from an external source … and signs the result with a PKP, that signed output is called a proof.
Additional signals from the docs:
- Lit Actions are the clearest expression of what the network actually ships for builders: programmable signing, data fetching, encryption, and attestable outputs
- The docs position Lit as infrastructure for off-chain computation that can still produce cryptographically verifiable artifacts for on-chain or application use
6) Security & verification docs
Source: https://developer.litprotocol.com/architecture/verification/index
Selected excerpts from the docs:
How to verify that your connection to Lit Chipotle terminates inside a genuine TEE running unmodified code.
The TLS private key is generated inside the Trusted Execution Environment (TEE) and never leaves it.
If the TLS handshake succeeds and the certificate is valid, you are provably talking to the TEE — not to any intermediary.
Additional signals from the docs:
- Lit’s current verification story is more detailed than many crypto infra vendors, with explicit attestation and certificate-verification guidance
- This matters for cataloging because it makes Lit more than “MPC plus marketing”; the project is actively publishing its trust and verification model
7) Official GitHub organization
Source: https://github.com/LIT-Protocol
Selected excerpts/signals from the public org page:
Lit Protocol is a decentralized (MPC TSS) key management and private compute (TEE) network.
Decentralized Signing and Wallet Management
Decentralized Encryption / Decryption
Additional signals from the org page:
- Public GitHub materials reinforce the combination of key management, encryption, and private compute rather than narrowing Lit to only one primitive
- The organization links developers directly toward SDKs, docs, and code examples, which fits the project’s docs-first posture
8) js-sdk repository
Source: https://github.com/LIT-Protocol/js-sdk
Selected excerpts/signals from the repository page:
The Lit Protocol SDK provides developers with a framework for implementing Lit functionality into their own applications.
Additional signals from the repository page:
- The repo exposes a multi-package SDK surface rather than a minimal wrapper, including packages for access-control conditions, auth helpers, encryption, contracts, and multiple PKP integrations
- This is a useful signal that Lit is operating as a substantial developer platform with several integration layers
Notes
- This pass did not locate a single canonical whitepaper or litepaper that appeared to be the current main source of truth.
- The strongest primary materials were the homepage, docs index, architecture/auth/verification docs, Lit Actions docs, and public GitHub repositories.
- Current official documentation prominently uses the “Lit Chipotle” branding for the programmable KMS and execution stack, while the homepage/GitHub surfaces continue to present the broader Lit Protocol network story.