privy

1/ A deeper dive into @privy's on-device signing. 

We’ve crossed 50M+ wallets using it today — enabling <5ms signing speeds for 40,000+ apps. 

Here’s how Privy delivers both on-device and TEE-based wallet infra, battle-tested at global scale.

The easiest way to bring all your users onchain, regardless of whether they already have wallets | Customer love at privy.io/love

marketing @privy | 2x founder | ✍️ author digitalmavericks.xyz paragraph.com/@debbie | 👩🏻‍💻 occasional vibe coder + renaissance woman | 🇸🇬 in 🇺🇸

4/ With TEE signing:

◆ Keys are reconstituted only inside secure enclaves (AWS Nitro).
◆ Requests pass through policies before signing.
◆ Apps can act even when users are offline.

Best for: banking, or apps with backend-driven flows, and onchain automation.

3/ With on-device signing:

◆ Signatures feel near-instant (<5ms).
◆ Keys split into encrypted shares + reassembled only in memory inside a secure iframe.
◆ Apps never touch user keys.

Best for: consumer wallets, trading apps, and real-time flows.

2/ Privy powers wallets that use on-device signing and TEE-based signing using AWS Nitro Enclaves.

Each model comes with different tradeoffs:
→ Speed & ownership
→ Control & policy