Confidential, verifiable execution for crypto and AI
Joined April 2021
- Tweets3K
- Following50
- Followers83.9K
- Likes5.2K
Pinned Tweet
Your wallet’s security depends on who can change its rules. Hosted wallets like @privy_io and @turnkeyhq keep those rules inside their own system.
With Lit Protocol, the rules live in contracts on @base. Changing them takes a transaction from your wallet, and anyone can read them.
Teams like @RelayProtocol and @EmblemVault build with Lit for real control.
Customer-managed keys let you control the key's policy. The provider's service still uses the key and sees your data while it works.
Zero operator access means the provider has no technical path to either one.
Here is the difference, how Lit does it, and the questions that tell you which one a vendor offers.
spark.litprotocol.com/custom…
You can run a @HyperliquidX trading bot without a private key on its server.
A Lit Action signs the orders with a Lit wallet whose key stays in an enclave. Your main account approves that wallet as an API wallet, and the action checks every order against limits in its code.
Here is the action, how to approve the wallet on Hyperliquid, and how the bot sends orders.
spark.litprotocol.com/hyperl…
We measured 600 @HyperliquidX signing requests on Lit's staging environment from our office, on an ordinary connection, end to end.
The median was 135 to 140 ms for one signature. All 600 succeeded and verified with Hyperliquid's official Python SDK.
The full numbers for orders, TP/SL, transfers, and withdrawals, and exactly how we measured them:
spark.litprotocol.com/tee-si…
If a regulator asks which code handled a customer's data, you should be able to prove it.
On Lit, each action signs its results with a key that comes from a hash of its own code. A signed result names the code that produced it.
We wrote up a screening check that signs its receipts, and how a regulator verifies one without trusting you.
spark.litprotocol.com/show-r…
No single employee should be able to move a fintech's funds.
On Lit, the signing key stays in an enclave, every payment runs through code next to it, and in ChainSecured mode the contract only accepts rule changes from your own Safe.
Here is a payment rule that needs two approvers for large payments, and the setup that keeps any one person from changing it.
spark.litprotocol.com/no-sin…
Builders can’t be stopped!
Where does your app keep its private keys? If the honest answer makes you a little nervous, I'd love to hear from you.
I've been building on @LitProtocol for a month now and have shipped two projects already. If a day goes by without me building something, I feel like I skipped a meal 😅 For my next build, I want to solve a real problem, so I'd love to hear yours first.
Has something like this happened to you?
• A private key sitting in a .env file, or in a commit you had to scrub
• An AI agent or bot that needed API keys or a wallet, with nothing really stopping it from misusing them 🤖
• A payout or trading script where one bug could sign the wrong transaction
• A client asking who on your team can access their keys or data
Or something else entirely? Tell me what happened and what you did about it. Replies and DMs open📥
Encrypted memory protects an AI agent's data from the host. The agent's own outbound calls are a separate risk.
With Lit, the agent runs in a confidential VM, a proxy inside it allows only the hostnames you listed, and changing that list needs your approval on-chain.
Here is how to run an agent on customer data so the hosting provider can't read it, and what your customers can check.
spark.litprotocol.com/ai-age…
An AI agent that holds a production key can leak it into logs, transcripts, and prompts.
With Agent Keychain, the agent asks for one operation, like reading a Stripe balance. The agent never gets the key. It is decrypted only inside a Lit enclave to make that one call.
How it works, how to set it up for Claude Code, and what it does not protect against:
spark.litprotocol.com/ai-age…
Ethereum and Solana use different kinds of keys, so a wallet for both usually starts from one seed phrase.
On Lit, one action's key covers both. It works as an Ethereum key as it is, and the same 32 bytes work as a Solana seed.
Here is one action that signs on both chains, with a limit for each and the client code for Solana.
spark.litprotocol.com/wallet…
If your AI agent holds a private key, a prompt injection can spend from it.
A safer setup gives the agent a tool that asks for a payment. The key and the rules for each payment stay in an enclave where the agent cannot reach them.
We wrote up how to build that on Lit, with the rule, the tool definition, and the setup calls.
spark.litprotocol.com/give-y…
Auditors will ask you to prove that no employee can reach your customers' keys.
You can answer with a setup where no employee has a technical path to the key, plus checks the auditor can run without trusting you.
Here is how that works on Lit: keys derived in an attested enclave, rules owned by your own Safe on Base, the commands an auditor runs, and the limits to disclose.
spark.litprotocol.com/prove-…