Two flavors of Smart Sessions: Session Keys vs SubAccounts
summary
Smart sessions delegate signing to temporary keys or lightweight accounts so apps avoid a popup per transaction, claiming session keys (wallet-managed signer + permission module), session accounts (wallet controls permissions but external key managers handle signing), and sub accounts (hierarchical wallet-owned accounts with separate balances and revocable control). Wallet Connect, ERCs like 7715/7710 and RPC wallet_getCapabilities (5792) are used; session keys are ~one year mature and widely implemented, session accounts and sub accounts are experimental but enable sandboxed app balances and fewer clicks.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:54What are Smart Sessions
- 3:01Improving wallet UX
- 5:30Origins of Session Keys
- 6:11Session Keys in detail
- 8:19Session Accounts intro
- 9:43Sub Accounts benefits
- 12:12Standards for Smart Sessions
- 15:02Comparing Session Keys, Session Accounts and Sub Accounts
- 17:11Future of Smart Sessions
- 20:59Standardization progress
- 22:45UX impact and adoption
- 23:27Q&A
related talks
31mEvolution of Wallets
01h 06mAccount Abstraction Panel
22mHow to Make Wallets Smarter
01mHow to Make Wallets Smarter
32mPortable Sessions with JSON Web Tokens
31mAccount Abstraction Panel
19mDiving into Onchain UX, MPC Account Abstraction
38mAuthentication as a Microservice: Portable Customer Identity Management
