LUKSO

About LUKSO (LYX)

What Is LUKSO (LYX)?

LUKSO is a standalone layer-1 blockchain that runs the Ethereum protocol stack but replaces Ethereum's account model with smart contract accounts by default. Instead of asking users to manage a raw key pair, LUKSO gives them a Universal Profile: an on-chain account that holds metadata, can be controlled by several keys with different permissions, and reacts to incoming assets.

LYX is the network's native coin. It pays transaction fees and is staked by validators, filling the same role ETH fills on Ethereum. The chain targets creative, social and consumer applications, where onboarding friction and account recoverability matter more than raw throughput. A live JSON-RPC call to the LUKSO mainnet endpoint on September 12, 2026 returned chain ID 0x2a, that is 42, confirming the identifier used by wallets and tooling.

Official sources:

• LUKSO
• LUKSO documentation
• LSP specifications (LIPs repository)
• Execution explorer
• Consensus explorer

Who Founded LUKSO? (History)

LUKSO was founded by Fabian Vogelsteller, named in the project's own documentation as the founder and known in Ethereum for authoring the ERC-20 and ERC-725 standards and for early work on web3.js. Marjorie Hernandez is widely credited as co-founder.

The funding round in 2020 used a reversible ICO, or rICO, a model Vogelsteller proposed himself. Participants bought LYXe, an Ethereum-based representation of LYX, over an eight-month window and could withdraw at any point to reclaim their remaining funds. The sale raised roughly 10,000 ETH.

Mainnet genesis followed on May 23, 2023, and was unusual in how it happened. Rather than launching the chain itself, the team published a deposit contract and let genesis validators start it. Those validators also voted on the genesis supply while depositing, selecting 42 million LYX from the options offered, and the contract collected 10,336 deposits from 223 unique addresses. After a discovery period, a migration route opened so remaining LYXe holders could convert to native LYX.

How LUKSO Works

LUKSO runs, in the documentation's own words, an unmodified version of the Ethereum protocol: a consensus layer using Casper FFG finality with LMD-GHOST fork choice, paired with an execution layer running the EVM. Clients are the same families used on Ethereum, adapted to LUKSO's network configuration.

Validators stake LYX to propose and attest to blocks. The base deposit is 32 LYX per validator key, and following the Pectra upgrade a single key can hold between 32 and 2,048 LYX. Rewards go to a withdrawal address chosen at key generation, which cannot be changed without exiting and generating new keys. Fee tips go to a separately configurable fee recipient.

Because the protocol tracks Ethereum upstream rather than forking away from it, LUKSO inherits Ethereum's fee market and reward mechanics as they evolve; anyone modeling issuance should read the current documentation rather than assume fixed parameters. The part that is genuinely LUKSO's own sits above consensus, in the account and asset standards.

Key Ecosystem Components

The LUKSO Standard Proposals, or LSPs, are the core of the design. The main ones are:

• LSP0 ERC725Account, the smart contract account that represents a user or organization.
• LSP1 Universal Receiver, which notifies an account when it receives assets or calls.
• LSP2 ERC725Y JSON Schema, the encoding rules for on-chain key-value data.
• LSP3 Profile Metadata, the descriptor that gives a profile a name, image and links.
• LSP4 Digital Asset Metadata, the equivalent descriptor for tokens and collections.
• LSP5 Received Assets and LSP12 Issued Assets, registries of what an account holds and what it has issued.
• LSP6 Key Manager, which grants granular permissions to multiple controller addresses.
• LSP7 Digital Asset and LSP8 Identifiable Digital Asset, the fungible and non-fungible token interfaces.
• LSP9 Vault and LSP10 Received Vaults, for segregated sub-accounts.

Around those sit Universal Profiles as the user-facing account, a browser extension for signing, Universal Everything as a profile and asset browser, the execution and consensus explorers, and an actively maintained contract and tooling repository set.

LYX Token Utility

• Paying gas for transactions and contract calls on LUKSO mainnet.
• Staking as a validator deposit, from 32 LYX upward, to secure consensus and earn protocol rewards.
• Delegated or pooled staking through third parties, which carries their counterparty risk rather than the protocol's.

There is no documented hard cap on LYX. Genesis supply was 42 million, and because validators are paid in newly issued LYX the total grows over time. Any source claiming a fixed maximum for LYX is describing the genesis figure, not a protocol limit.

What Makes LUKSO Unique?

Most EVM chains compete on throughput, fees or rollup architecture. LUKSO competes on the account layer. Externally owned accounts are treated as a controller mechanism rather than the user's identity, and the account itself is a contract from the first transaction.

That produces properties which are awkward to retrofit elsewhere: an account can carry a profile and metadata on-chain, several devices or delegates can hold different permission sets through the Key Manager, a lost controller key does not necessarily mean a lost account, and an account can execute logic when it receives an asset. Ethereum reaches similar outcomes through ERC-4337 and EIP-7702, but as an optional layer on a key-based default. LUKSO made it the default and specified the result in a public, versioned LIPs repository.

How LUKSO Differs from Similar Chains

Against Ethereum, LUKSO is EVM-equivalent and protocol-aligned, so contracts and tooling port with little friction, but it has a far smaller validator set, less liquidity and a much younger application ecosystem: a cleaner account model in exchange for less economic security and depth.

Against L2 rollups such as Optimism or Arbitrum, LUKSO is a sovereign L1 with its own validators and security budget, so it neither inherits Ethereum's security nor carries a rollup's sequencer and bridge assumptions. Against creator-focused chains such as Flow or Tezos, its bet is standards rather than a bespoke virtual machine: developers write ordinary Solidity and adopt the LSP interfaces.

Use Cases of LUKSO

• Universal Profiles as portable on-chain identity for social, creative and community applications.
• Issuing digital assets with rich, standardized metadata through LSP7 and LSP8.
• Permissioned setups where a team, a vault or a recovery delegate controls one shared account with different rights.
• Applications that react programmatically to incoming transfers using the Universal Receiver.

How LUKSO Is Secured

Security comes from proof-of-stake with the same finality mechanics as Ethereum. Validators deposit LYX, attest to blocks, and lose stake through penalties or slashing for equivocation and prolonged inactivity. Reverting a finalized block requires destroying a very large amount of staked LYX.

Because the network began with genesis validators drawn from deposit participants rather than a foundation-run set, validator distribution started relatively broad. The practical caveat is scale: a smaller total stake and validator count mean a lower absolute cost of attack than on Ethereum, and client diversity is tracked publicly for that reason. At the application layer, security rests on the LSP contracts, which are open source and audited, but permission systems are intricate and a misconfigured Key Manager permission set is a realistic user-level failure mode.

Risks and Considerations

• LYX has no supply cap. Validator issuance dilutes holders who do not stake.
• The chain's security budget is much smaller than Ethereum's, which matters for high-value settlement.
• Ecosystem depth is limited: fewer applications, fewer integrations and thinner liquidity than mature L1s.
• The LSP standards are strong in design but not widely adopted outside LUKSO, so assets and profiles do not automatically travel to other EVM chains.
• Smart contract accounts move complexity from key management to permission management. That is a real improvement, and also a new class of user error.
• Any remaining LYXe migration mechanics are time-bound and should be checked against current official guidance rather than older articles.

Why LUKSO Matters

LUKSO is one of the few networks that treats onboarding and account design as the primary problem rather than a UX afterthought. Whether or not the chain itself grows large, its standards work addresses a question the whole industry has: how do you give someone an on-chain account that behaves like an account instead of a private key they must never lose. LUKSO shipped an opinionated end-to-end answer rather than an optional extension.

Where Can You Buy LYX?

LYX is available on a number of centralized exchanges and, on LUKSO itself, through native decentralized exchanges once funds reach the network. Because LYXe on Ethereum and native LYX are distinct assets, confirm which one a venue delivers, and that a withdrawal reaches LUKSO mainnet, chain ID 42, rather than an Ethereum address.

Major Centralized Exchanges (CEX)

LYX and its Ethereum-based predecessor have been listed on several mid-sized international exchanges, with availability varying by jurisdiction and changing over time. Check the venue's own asset page for current network support and withdrawal options before depositing.

Storage Options After Purchase

The native experience is a Universal Profile, created through the LUKSO browser extension, which manages permissions through the LSP6 Key Manager. For holding LYX as a plain balance, any EVM-compatible wallet works once the LUKSO network is added with chain ID 42 and an official RPC endpoint, and a Ledger or Trezor can secure the controller key behind it. Validators should note that the withdrawal address is fixed at key generation, so it should point at long-term storage from the start.

Related Coins

• Ethereum
• Polygon Ecosystem Token
• Tezos
• Flow
• Ethereum Name Service