Lit Protocol 🔑

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.

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.

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.

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.