Build Smart Wallet UX on LUKSO
A smart wallet UX is a permission graph, not a connect button. LSP6 Key Manager is the standardized vocabulary for that graph — controllers, permissions, allowed calls, allowed data keys — and LSP0 is the account those controllers act on. Because every account speaks the same permission vocabulary, cross-wallet session portability is possible in principle, unlike ERC-4337's per-vendor validator SDKs that don't share a common permission shape.
The stack
| Standard | Role |
|---|---|
| LSP0 | The account contract |
| LSP6 | Per-controller permissions: target, selector, data-key scoping |
| LSP11 Basic Social Recovery | Guardian-voting recovery (contract reference) |
| LSP20 | Inline call verification, when controllers call the account directly rather than through the Key Manager wrapper |
| ERC-1271 | Contract signature validation — Sign-In-with-Ethereum, off-chain order signing |
When this vertical fits
Anything where "the wallet has full account control" is the wrong default: session keys scoped to one app, controllers scoped to a single marketplace integration, recovery controllers a user never touches day-to-day, or multi-device flows where each device gets its own permission set instead of sharing one master key.
Because LSP6 permissions are a chain-level standard rather than a per-SDK convention, a session key granted by one LSP6-aware wallet means the same thing to every other LSP6-aware wallet or tool — no per-vendor integration required to understand what a given controller can do.
Related reading: Wallet permission scoping · Social recovery without a seed phrase · The EOA key-risk problem · EOA vs Universal Profile · Smart account permissions