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 yProtocol and @EmblemVault build with Lit for real control.
With Lit Protocol, the rules live in contracts on @base. Changing them takes a transaction from your wallet, and anyone can read yProtocol and @EmblemVault build with Lit for real control.
8
3
12
2,546
Your app can send email without ever holding the email provider's API key.
On Lit, the key is encrypted to a Lit wallet and decrypted only inside the Lit Action that sends the email. The sender and template are written into the action's code.
On Lit, the key is encrypted to a Lit wallet and decrypted only inside the Lit Action that sends the email. The sender and template are written into the action's code.
2
1
3
1,189
Here is how to seal a Resend key and send from a Lit Action, and what the setup protects.
spark.litprotocol.com/send-email-wit…
spark.litprotocol.com/send-email-wit…
0
1
2
104
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.
Zero operator access means the provider has no technical path to either one.
3
2
7
1,167
Here is the difference, how Lit does it, and the questions that tell you which one a vendor offers.
spark.litprotocol.com/customer-manag…
spark.litprotocol.com/customer-manag…
1
1
3
138
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.
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.
2
2
8
1,334
Here is the action, how to approve the wallet on Hyperliquid, and how the bot sends orders.
spark.litprotocol.com/hyperliquid-tr…
spark.litprotocol.com/hyperliquid-tr…
0
1
3
181
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 median was 135 to 140 ms for one signature. All 600 succeeded and verified with Hyperliquid's official Python SDK.
2
2
8
1,366
The full numbers for orders, TP/SL, transfers, and withdrawals, and exactly how we measured them:
spark.litprotocol.com/tee-signing-la…
spark.litprotocol.com/tee-signing-la…
0
1
3
158
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.
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.
2
2
9
1,286
We wrote up a screening check that signs its receipts, and how a regulator verifies one without trusting you.
spark.litprotocol.com/show-regulator…
spark.litprotocol.com/show-regulator…
0
1
5
120
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.
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.
2
1
10
1,511
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-single-empl…
spark.litprotocol.com/no-single-empl…
0
1
3
146
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 ild, 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📥
1
1
4
1,439
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.
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.
2
1
6
1,353
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-agent-on-cu…
spark.litprotocol.com/ai-agent-on-cu…
0
1
4
145
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.
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.
3
2
9
1,372
How it works, how to set it up for Claude Code, and what it does not protect against:
spark.litprotocol.com/ai-agent-produ…
spark.litprotocol.com/ai-agent-produ…
0
1
4
152
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.
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.
2
1
2
1,620
Here is one action that signs on both chains, with a limit for each and the client code for Solana.
spark.litprotocol.com/wallet-for-eth…
spark.litprotocol.com/wallet-for-eth…
0
1
1
168
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.
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.
2
1
6
1,433
We wrote up how to build that on Lit, with the rule, the tool definition, and the setup calls.
spark.litprotocol.com/give-your-ai-a…
spark.litprotocol.com/give-your-ai-a…
0
1
4
161