Build Profile-Native Apps on LUKSO

A profile-native app reads the account, not its own database. Name, avatar, owned assets, and created assets live directly on the Universal Profile under standardized LSP3, LSP5, and LSP12 keys; followers are indexed by LSP26, a separate chain-level registry contract keyed by address rather than data stored on the profile itself. Either way, your app composes existing primitives instead of mirroring them into a separate login system.

The stack

Standard	Role
LSP0	The account itself
LSP3	Profile-level metadata — name, avatar, bio, links
LSP5	Received-assets inventory registry
LSP12	Issued-assets registry, for creators
LSP26	The follower graph
LSP1	Receiver hook — LSP5 entries get written automatically when assets arrive

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 — no per-app login flow, no separate identity database to keep in sync.

Why this matters for distribution

Because LSP3, LSP5, LSP12, and LSP26 are chain-level standards rather than protocol-specific conventions, any new app that speaks the LSP surface reads a user's existing identity, inventory, and social graph on day one — no cold-start problem, no asking users to rebuild a profile from scratch.

Related reading: EOA vs Universal Profile · The EOA key-risk problem · Best blockchain for social apps · On-chain identity architecture