The Users are Here with Privy
summary
Privy explains how it provisions self‑custodial keys behind email, social, or MetaMask flows so apps can onboard users without exposing keys, and how those keys and onchain assets are made interoperable across apps (POAP, Blackbird, Zora, Courtyard). The product goes live as a self‑serve platform, a sample app ships from signup to production in 40 hours, with mobile SDKs (React Native, Swift, Kotlin) and a public release of embedded wallets; next steps center on gas sponsorship, global wallets, and cross‑app asset portability.
AI-written summary · about
chapters (21)
- 0:00Intro to Privy and user-friendly wallets
- 0:53How Privy started at Protocol Labs
- 2:34From consensus to user-facing crypto apps
- 3:36The first version of Privy and offchain data
- 4:36How onboarding shaped the current product
- 5:05What are embedded wallets?
- 6:36Balancing UX, decentralization, and custody
- 7:43Self-custody vs decentralization tradeoffs
- 9:11Developer UX and embedded wallet limitations
- 10:06What is consumer crypto?
- 11:03Privy’s developer focus across user types
- 12:25Examples: Blackbird, Hyperliquid, Zora, Courtyard
- 14:21Measuring app success and transaction funnel
- 15:21Introducing global embedded wallets
- 16:21Self-custody and interoperability in practice
- 17:55Onchain vs offchain asset context
- 18:52Starting with onchain; future of data portability
- 19:21Mobile SDKs and PWAs in crypto UX
- 20:26Why mobile crypto matters for growth
- 21:33What’s next: global wallets, gas sponsorship, on-ramps
- 22:55Closing remarks and future of wallets with Privy
related talks
13mAll Your Users, Onchain
24mBuilding Seamless Onchain Apps
25mApps Built on Polkadot
02mServer Wallets With Privy
08mMaking Blockchain Applications Available to Mainstream Users
28mExtending Web3 Provider for Better UX
18mBringing Privacy-Preserving Cryptography to Mobile Apps
22mPowering Stripe's Stablecoin Stack