Skip to content
Get started

Crypto infrastructure

A programmable wallet
for your crypto system.

Power hot wallets, vaults, and agent wallets with code that runs in confidential hardware. Each code version is immutable. Your on-chain permissions determine which versions can use the wallet.

Get started with crypto

The authority stays with you

Update the rules.
Keep the wallet.

Authorize the exact code.

Each Lit Action is identified by its code hash. Changing the code creates a new version with a different hash.

Lit Actions

Update permissions on-chain.

Authorize a new Action and revoke the old one through your account’s on-chain permissions. The wallet keeps its address.

Chain Secured

Sign inside confidential hardware.

Request a permitted action without storing the signing key on your application server.

Security & verification

From input to signature

Read the data. Check your rules. Act.

  1. 01

    Connect.

    Read data from APIs, private accounts, and blockchains.

    Using private credentials
  2. 02

    Decide.

    Your code checks the conditions: amount, recipient, timing, or other rules.

    Authorizing actions
  3. 03

    Sign.

    The authorized action signs when its conditions pass.

    Run your first action

Wallet infrastructure

Built for your crypto system.

Hot wallets

Automate payments and transactions. Let code check recipients, amounts, and live data before the wallet signs.

Vaults

Define withdrawal conditions and approval checks in code. Approve changes to those rules on-chain.

Agent wallets

Let agents transact within limits you define in code. Update or revoke their wallet access through on-chain permissions.

Explore the applications

Common questions.

How can immutable code support an updatable wallet?
Each Action’s code is fixed. An update creates a new Action with a different hash. Your account authorizes that version to use the existing wallet and can revoke earlier versions. The wallet’s address stays the same. How Actions and wallet keys work.
Do signatures require an on-chain transaction?
You change permissions through an on-chain transaction. Lit Actions read those permissions when they run, so each signature does not require a separate permission transaction. Chain Secured architecture.
How are runtime updates approved?
Protocol releases follow an on-chain approval process, separate from account permissions. The runtime must satisfy the contract’s approval rules to receive its keys. Inspect runtime governance.

Compare wallet infrastructure

Build with Lit

Build on a foundation you can verify.

Get started with cryptoContact for Lit AI