Universal Profile

A Universal Profile is built from a modular set of LUKSO Standard Proposals (LSPs). The core components are:

• LSP0 - ERC725 Account: The foundational smart contract acting as a programmable key-value store and proxy.
• LSP3 - Universal Profile: Defines the metadata schema for profile data (name, description, avatar).
• LSP6 - Key Manager: Separates ownership from control, allowing multiple keys with granular permissions.
• LSP1 - Universal Receiver: Enables the contract to be notified of and react to incoming asset transfers.

It functions as a user's portable, verifiable identity on-chain. Unlike externally owned accounts (EOAs), a Universal Profile stores its own metadata, enabling:

• Verifiable Claims: Attestations (e.g., KYC, credentials) can be linked to the profile.
• Social Profiles: Public display of avatars, descriptions, and links.
• Interoperability: Any dApp on LUKSO can read this standardized identity data, creating a consistent user experience across the ecosystem.

Every Universal Profile is a smart contract wallet, providing advanced security and functionality over traditional EOAs:

• Account Recovery: Through social recovery schemes or guardian contracts.
• Transaction Relaying: Gas can be sponsored by third parties (meta-transactions).
• Batch Operations: Multiple actions (e.g., swap and stake) can be executed in a single transaction.
• Permission Management: The Key Manager (LSP6) allows defining roles (Admin, Signer) with specific allowances and restrictions.

Universal Profiles are designed to be the hub for all a user's digital assets, compatible with other LSPs:

• LSP7 - Digital Asset: For fungible tokens (like ERC20).
• LSP8 - Identifiable Digital Asset: For NFTs (like ERC721/1155).
• LSP9 - Vault: Allows creating separate asset containers for organization or security.
• The Universal Receiver (LSP1) automatically notifies the profile of any incoming asset, enabling custom logic upon receipt.

Universal Profiles empower creators by unifying their identity, assets, and commerce:

• Unified Brand Identity: A single profile links to all their creations (NFTs, social tokens).
• Direct Monetization: Fans can send assets directly to the creator's profile.
• Verified Collections: Creators can link their official NFT collections to their profile, combating impersonation.
• Royalty Enforcement: Smart contract logic within the profile can manage royalty streams.

A Universal Profile replaces traditional usernames and passwords for Web3 services. It enables single sign-on (SSO) across dApps using Ethereum-based signatures, eliminating the need for new credentials. Key features include:

• Profile Data: Stores verifiable information like avatars and social links in its ERC725 data store.
• Permission Management: Users control which dApps can access specific data via its LSP6 KeyManager.
• Real Example: The Lukso ecosystem uses Universal Profiles as the foundational identity layer for all its applications.

The profile acts as a smart contract wallet, natively supporting digital assets via ERC725Y standards. This creates a unified vault for a user's entire portfolio.

• Fungible Tokens: Receive and hold ERC20 tokens.
• NFTs: Natively compatible with ERC721/ERC1155 and the LSP7/LSP8 standards.
• Visual Unity: All assets are discoverable in a single interface, unlike scattered EOAs. This is foundational for digital fashion and phygital goods on networks like Lukso.

Universal Profiles solve the private key loss problem through programmable social recovery. Instead of a single seed phrase, control can be distributed among trusted entities.

• Recovery Vaults: Users can set up a LSP1 UniversalReceiverDelegate contract as a recovery module.
• Guardian Designation: Assign recovery powers to other profiles or trusted contracts.
• Process: If a main key is lost, a predefined majority of guardians can authorize a key reset, transferring profile ownership to a new wallet.

The profile's on-chain data store enables portable reputation and verifiable credentials. Achievements and attestations are linked directly to the immutable identity.

• Soulbound Tokens (SBTs): Non-transferable tokens representing memberships, skills, or licenses can be held by the profile.
• Verifiable Credentials: Issuers can write signed claims directly to the profile's ERC725Y storage.
• Use Case: A DAO could issue governance credentials or a university could grant verifiable diplomas to a Universal Profile.

Profiles enable meta-transactions, allowing dApp operators or third parties to pay gas fees on behalf of users. This is managed via the LSP6 KeyManager.

• Relayer Systems: A service can sponsor transactions by bundling a user's signed payload.
• Improved UX: Users can interact with dApps without needing the network's native token for gas, lowering the entry barrier.
• Enterprise Application: Brands can create seamless onboarding flows by covering initial transaction costs for customers.

The technical foundation is a suite of interoperable Ethereum standards that define the profile's capabilities.

• ERC725: The core; ERC725X enables execution (calls, deployments) and ERC725Y provides a generic key-value data store.
• LSP Standards: The LSP0 (ERC725Account), LSP1 (UniversalReceiver), LSP6 (KeyManager), and LSP7/LSP8 (Digital Assets) form a complete specification stack.
• Result: This standardized architecture ensures profiles from different builders remain interoperable across the ecosystem.

A Universal Profile is a smart contract wallet, not an Externally Owned Account (EOA). This fundamental shift means:

• Security logic is programmable (e.g., multi-sig, spending limits, transaction cooldowns).
• The contract's owner (an EOA or another contract) holds the ultimate signing keys.
• Recovery mechanisms and access control are built into the contract's code, moving beyond simple private key custody.

UPs implement fine-grained permissions via ERC-734 Key Manager. This allows for:

• Multiple keys with distinct roles (e.g., ADMIN, SETDATA, SIGN).
• Delegated signing where a trusted service can sign specific transactions without holding the master key.
• Time or spending limits on permissions, enabling secure delegation of asset management.

Mitigates the risk of lost private keys through recoverable controller schemes. Common patterns include:

• Guardian networks where trusted contacts can vote to replace a lost key.
• Hardware security module (HSM) integration for enterprise-grade key storage.
• Multi-factor setups requiring confirmation from multiple devices or parties for sensitive operations.

UPs store verifiable data via ERC-725Y (Key-Value Store). Considerations include:

• Data is public by default on the blockchain; sensitive information should be stored as hashes or off-chain (e.g., using ERC-725Y with IPFS).
• Selective disclosure protocols allow users to prove claims (like KYC status) without revealing the underlying document.
• Users control what data is attached to their profile, forming a self-sovereign identity.

Built on open standards (ERC-725, ERC-734) to ensure compatibility across the ecosystem. This enables:

• Cross-dApp recognition: A single profile works with any application supporting the standards.
• Asset agnosticism: Can hold and interact with any ERC-20, ERC-721, or ERC-1155 token.
• Verifiable credential integration with frameworks like W3C Decentralized Identifiers (DIDs).

As smart contracts, UPs have different transaction characteristics than EOAs:

• Higher base gas cost for simple transfers due to contract execution overhead.
• Batch transactions (e.g., transferring multiple assets in one call) can improve efficiency and user experience.
• Gas abstraction patterns allow dApps or relayers to pay fees, improving onboarding (see ERC-4337 Account Abstraction).

A key distinction in blockchain account models.

• EOA: A traditional account controlled by a single private key (e.g., MetaMask). Limited functionality, no built-in recovery, and cannot hold complex data.
• Universal Profile: A smart contract account with upgradable logic, multi-sig capabilities via controllers, a built-in data store, and native asset management. It represents a shift from key-based to identity-based accounts.