Profile-native apps.
Building profile-native apps on LUKSO — where user identity is the account, inventory is on-chain, and the social graph is portable — combines LSP3 (profile metadata: name, avatar, bio, links), LSP5 (received assets registry), LSP12 (issued assets registry for creators), and LSP26 (follower system). Together they turn any Universal Profile into a portable identity primitive that dapps can read without a login flow. Assets, creations, and social connections travel with the profile across every app that speaks the LSP surface.
A profile-native app reads the account, not its own database. Name, avatar, owned assets, created assets, followers — all live on the profile under LSP3, LSP5, LSP12, and LSP26 keys. Your app composes these primitives instead of mirroring them.
When this vertical fits
You’re building anything social-shaped on LUKSO: a feed reader, a creator marketplace, a collector index, a follow-based discovery surface. The product is a way to consume what the profile graph already publishes.
The minimum stack
- LSP0 as the account
- LSP3 for profile-level metadata (name, image, links)
- LSP5 + LSP12 for received + issued asset inventories
- LSP26 for the follower graph
- LSP1 on the receiver side so the profile reacts to new assets (LSP5 entries get written automatically)
Reading list.
A curated path — problem → standard → migration.
- [ 01 ] problem An EOA is one key for everything
- [ 02 ] LSP0 ERC-725 Account
- [ 03 ] LSP3 Profile Metadata
- [ 04 ] LSP5 Received Assets
- [ 05 ] LSP12 Issued Assets
- [ 06 ] LSP26 Follower System