Lit Protocol 🔑

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.

Hashing an email address does not keep it private on a blockchain. Anyone can hash a list of likely addresses and compare.

A keyed hash fixes that. On Lit, the key is derived from a Lit wallet inside a secure enclave, so a guess can only be tested through your own action.

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.