LUKSO Blockchain Guide: Universal Profiles, LYX and Staking (2026)

LUKSO is a proof-of-stake layer 1 blockchain that is compatible with the Ethereum Virtual Machine (EVM). Its mainnet launched in May 2023. It was co-founded by Fabian Vogelsteller, the developer behind the ERC-20 token standard and the ERC-725 identity standard, and Marjorie Hernandez. Its native coin is LYX.

The pitch is not raw throughput or the cheapest fees. LUKSO positions itself as a chain for digital identity, creators, fashion, gaming and social applications, and it builds that focus into the protocol layer through its own standards, called LUKSO Standard Proposals (LSPs). Instead of a plain key-controlled address, the intended account on LUKSO is a smart-contract account called a Universal Profile, which can hold metadata, assets, permissions and relationships.

Who it suits

• Developers who want Solidity and Ethereum tooling plus built-in profile and asset-metadata standards.
• Brands and creators interested in digital collectibles that carry rich, structured metadata.
• Validators and stakers who are comfortable running an Ethereum-style node setup on a separate network.
• Users curious about smart-contract accounts with permission controls and recovery options.

What it is not

LUKSO is a separate network, not an Ethereum rollup. It has its own validator set, its own security budget and its own liquidity. Assets that sit on Ethereum do not appear on LUKSO automatically. Activity, total value locked, token listings and ecosystem projects change often, so check live dashboards and the official site rather than relying on any article for current figures.

LUKSO follows the same broad design as Ethereum after its move to proof of stake. Two pieces of software run side by side on every node: an execution client, which processes transactions and runs smart contracts in the EVM, and a consensus client, which follows the proof-of-stake protocol. Validators run a third piece, a validator client, that holds the signing keys and proposes and attests to blocks.

Because the design mirrors Ethereum's, LUKSO's node tooling draws on mainstream Ethereum clients, and the official LUKSO command-line tool helps operators install and configure them. Block times are in the same range as Ethereum's, and fees are paid in LYX.

What EVM compatibility means in practice

• Contracts written in Solidity or Vyper can generally be deployed with little or no change.
• Standard JSON-RPC calls work, so common libraries and wallets can connect once the network is added.
• Familiar developer tools, such as Hardhat, Foundry, ethers and viem, work against LUKSO endpoints.

Network details to verify

A wallet needs the correct chain ID, RPC endpoint and currency symbol before it can connect. LUKSO runs a mainnet and a public testnet with separate chain IDs. Copy these values only from the official LUKSO documentation, not from a search result, a social post or a message from a stranger. A wrong or malicious RPC endpoint can show false balances or push you toward phishing sites.

Compatibility with the EVM does not mean compatibility with Ethereum's liquidity or apps. Each application has to be deployed on LUKSO by someone, and token balances do not carry over between chains.

A Universal Profile is the central idea of the chain. On most EVM networks your account is an address controlled by one private key. If that key leaks or is lost, the account is lost with it. A Universal Profile is a smart contract that acts as your account, and it separates the account from the keys that control it.

Main features

• Controller keys with permissions. Through a Key Manager contract (LSP6), you can give different keys different rights. One key might be allowed to set profile data, another to transfer assets, and a third to interact only with a specific app.
• Profile metadata. Name, description, images and links are stored as structured data on the account, so apps can read the same profile instead of each keeping its own.
• Asset tracking. The profile can record the tokens and collectibles it receives, so apps can display a holder's assets from one place.
• Universal Receiver. The account can run logic when it receives a token or a message, for example to reject unwanted assets.
• Recovery and relaying. Standards exist for social recovery designs and for relayed, sponsored transactions, where another party pays the gas.

Trade-offs

Smart-contract accounts add flexibility but also complexity. A badly configured permission set can leave a controller key with more power than you intended. Anyone using a Universal Profile should review its controllers regularly, keep a backup of the recovery phrase for the controlling key and understand that apps built for plain addresses may not support smart-contract accounts in every case.

LSPs are LUKSO's set of standards, written as proposals and implemented in open-source smart contract libraries. They sit alongside the ERC standards used on Ethereum. You do not need to memorise them, but the table shows the ones you are most likely to meet.

Standard	Role	Closest familiar idea
LSP0	Account contract for Universal Profiles	Smart-contract wallet
LSP1	Universal Receiver, reacts to incoming assets and messages	Receive hooks
LSP2	Schema for storing structured key-value data	On-chain metadata layout
LSP3	Profile metadata	Social profile
LSP4	Digital asset metadata	Token metadata
LSP6	Key Manager with permissions	Role-based access control
LSP7	Fungible digital asset	ERC-20
LSP8	Identifiable (non-fungible) digital asset	ERC-721
LSP9	Vault for holding assets separately	Sub-account or safe
LSP25	Execute relay calls	Meta-transactions

Why LSP7 and LSP8 matter

LSP7 and LSP8 are the token standards for LUKSO-native assets. They are designed to work with Universal Profiles and the Universal Receiver, and they carry richer metadata than the older ERC standards. An LSP8 collectible can hold data about its creator, its attributes and its relationships to other assets in a structured way.

Older ERC-20 and ERC-721 tokens can still exist on LUKSO because it is EVM-compatible. However, the wallet and app experience is designed around LSP assets. If you are building, check which standard each integration expects before you choose one.

LYX is the native coin of the LUKSO chain. It pays transaction fees and serves as the staking asset that secures the network through proof of stake.

LYX versus LYXe

Before the mainnet launched, the project's token existed as LYXe, an ERC-20 token on Ethereum that came from the project's 2017 token sale. When the LUKSO chain went live, a genesis migration let holders move from LYXe to native LYX. Check the official documentation to see whether any conversion route is still open and how it works. Do not use unofficial converters or wrapped versions of unknown origin. A copy of a token on another network is not necessarily LYX, and a lookalike contract is a common scam format.

Where LYX is used

• Paying gas for transfers, contract calls and profile updates.
• Staking 32 LYX per validator to take part in consensus.
• Collateral or trading pairs in any applications that choose to support it.

Things this guide does not state

Price, market capitalisation, circulating supply, issuance schedule and any fee-burn rules are all figures that can change. Look them up on the official LUKSO tokenomics documentation and a reputable market-data site on the day you need them. Treat any number you find in an old article, video or social post as out of date until you have confirmed it.

LYX is a volatile asset like other cryptocurrencies. Nothing here is financial advice.

LUKSO uses proof of stake, and each validator requires 32 LYX. A validator is software that stores your signing keys, proposes blocks when selected and attests to the blocks of others. In return it earns staking rewards, and it can be penalised for downtime or slashed for provably dishonest behaviour such as signing conflicting messages.

What solo staking involves

1. Prepare hardware and a stable internet connection. A validator needs to be online almost all the time.
2. Install an execution client, a consensus client and a validator client, usually with the official LUKSO command-line tool.
3. Generate validator keys and a deposit file using the official tooling and the staking Launchpad.
4. Send the 32 LYX deposit through the official deposit flow, after verifying you are on the official interface.
5. Wait for activation, then monitor the node and keep software updated.

Safety points

• Back up your recovery phrase offline and never type it into a website.
• Never run the same validator keys on two machines. Duplicate signing can lead to slashing.
• Know which address is set to receive withdrawals before you deposit.

Other routes

If you do not hold 32 LYX or do not want to operate a node, third-party staking services and some exchanges may offer exposure. These add counterparty or smart-contract risk, and terms differ. Liquid staking tokens from Ethereum services such as Lido and Rocket Pool apply to ETH, not LYX, so they are not alternatives here. Rewards vary with the number of validators and network conditions, so check live figures before you decide.

Getting started takes a few minutes if you follow official sources. Use a fresh browser profile or a trusted device, and avoid links sent to you in messages.

1. Choose an account type. The Universal Profile browser extension is built for LUKSO's account model. A standard EVM wallet can also connect to the network, but it will not provide Universal Profile features on its own.
2. Create the profile. Follow the extension's setup, write down the recovery phrase on paper and store it offline. Set a strong password.
3. Add the network if needed. In an EVM wallet, add LUKSO using the chain ID, RPC URL and symbol from the official documentation. Confirm the same values from at least one other official page.
4. Get a small amount of LYX. Check whether your preferred exchange lists LYX and which withdrawal network it supports. Exchanges such as OKX, Gate, Bitget and Bitvavo differ by region and over time, so look at their current asset pages. Send a small test withdrawal first.
5. Use the block explorer. Look up your address or transaction on the official LUKSO explorer to confirm that funds arrived.
6. Try a low-stakes action. Edit profile metadata or receive a test asset before moving anything of value.

Common mistakes

• Sending LYX to an address on a different network.
• Mistaking a wrapped or lookalike token for LYX.
• Approving a contract you have not checked.

If you are under 18 or your local rules restrict crypto trading, do not use an exchange. Check your own jurisdiction's regulations and tax obligations.

LUKSO is accessible to Ethereum developers. Smart contracts are written in Solidity, compiled with standard toolchains and deployed to a LUKSO RPC endpoint, either to the public testnet first or directly to mainnet.

Building blocks

• LSP smart contract library. Open-source contracts that implement the LSPs, including Universal Profile accounts, Key Managers and LSP7 and LSP8 tokens.
• ERC-725 JavaScript library. Helps read and write the structured data stored on profiles and assets.
• Common web3 libraries. ethers, viem and web3.js can all connect to LUKSO like any EVM network.
• Testnet. A public test network lets you deploy and debug without spending real value. Use the official faucet instructions to get test coins.

Design decisions to make early

1. Decide whether your app supports Universal Profiles, plain addresses or both. Supporting smart-contract accounts means handling their permissions and signature checks.
2. Pick LSP7 or LSP8 for new tokens if you want them to work smoothly with profiles, or ERC-20 and ERC-721 if you need compatibility with outside tools.
3. Plan how metadata is stored. LSP4 expects structured data that often points to off-chain files, so choose reliable storage and consider permanence.
4. Consider relayed transactions if you want users to interact without holding LYX for gas.

Audits and testing

Using audited libraries does not make your own contracts safe. Write tests, get an independent review for anything that holds value and read the library's release notes before upgrading. Check the official documentation for current versions, as the standards continue to evolve.

LUKSO's ecosystem is smaller and more specialised than Ethereum mainnet or the large layer 2 networks, and the mix of projects changes. Expect identity, profile, collectible and creator-focused apps rather than the deepest lending and trading markets. Check the official ecosystem listings and independent dashboards for current projects, volumes and total value locked.

Factor	LUKSO	Ethereum mainnet	Ethereum layer 2s
Security model	Own validator set and LYX stake	Ethereum validators	Inherits from Ethereum through rollup design
Default account	Universal Profile (smart contract)	Key-controlled address	Key-controlled address, with some smart accounts
Standards focus	LSPs for profiles and assets	ERC standards	ERC standards
Liquidity	Separate, usually thinner	Deepest	Varies by network
Tooling	EVM tools plus LSP libraries	Broadest	Broad

DeFi and bridging

Do not assume that well-known Ethereum protocols are available on LUKSO. Lending markets such as Aave V3, bridges such as Across, LayerZero V2 and Chainlink CCIP, and token systems such as USDT0 each support a defined list of chains. Check the supported-chain list in a protocol's own documentation before sending funds, and never rely on an unofficial deployment that claims to be the real one.

Choosing between chains

LUKSO makes the most sense when the profile and asset-metadata model is central to what you are building or using. If you mainly want deep liquidity, large DeFi markets or maximum wallet support, Ethereum and its layer 2s are usually better served. The right choice depends on the use case and your risk tolerance.

LUKSO shares the risks of any smaller, EVM-based layer 1, plus a few of its own. A practical checklist helps.

Main risks

• Smart-contract risk. Bugs in apps, tokens or even account contracts can cause losses. Audits reduce risk but do not remove it.
• Permission mistakes. A controller key with broad rights can drain a Universal Profile. Give each key only the permissions it needs.
• Scam and spam assets. Because accounts can react to incoming assets, unsolicited tokens and collectibles appear. Do not interact with unknown tokens, and never approve a contract you do not recognise.
• Phishing and fake interfaces. Imitation wallets, fake Launchpads and false network settings are common across crypto.
• Liquidity and volatility. Thin markets can mean wide spreads and sharp price moves.
• Network and client risk. Any chain can face outages, bugs or governance disputes.

Defensive habits

1. Store recovery phrases offline and never share them with anyone, including people claiming to be support.
2. Bookmark official documentation and use it for network settings and contract addresses.
3. Test with small amounts before large transfers.
4. Review approvals and controller permissions on a regular schedule and revoke what you no longer use.
5. Keep wallet extensions and node software updated.

What to check for current status

This guide deliberately omits prices, rankings, validator counts and recent news. For those, use the official LUKSO documentation, the official block explorer, independent chain dashboards and the announcements of any exchange or app you plan to use.