Network Parameters
| Setting | Value |
|---|---|
| Network Name | LUKSO |
| Genesis Fork Version | 0x42000001 |
| Chain ID / Network ID | 42 |
| Currency Symbol | LYX |
| Execution Block Explorer | https://explorer.lukso.network |
| Execution Status Page | https://stats.execution.mainnet.lukso.network |
| Consensus Block Explorer | https://explorer.consensus.mainnet.lukso.network |
| Consensus Status Page | https://stats.consensus.mainnet.lukso.network |
| Launchpad | https://deposit.mainnet.lukso.network |
| Checkpoints | https://checkpoints.mainnet.lukso.network |
| Blockscout API | https://explorer.execution.mainnet.lukso.network/api |
The mainnet network configs are defined or the lukso-network/network-configs repo.
Add LUKSO to Wallets​
You can add the LUKSO to any of your existing wallets like MetaMask, Rabby, Rainbow, Coinbase Wallet, Trust Wallet, and others using the following parameters or button:
| Setting | Value |
|---|---|
| Network Name | LUKSO |
| RPC URL | https://42.rpc.thirdweb.com |
| Chain ID / Network ID | 42 |
| Currency Symbol | LYX |
| Block explorer URL | https://explorer.lukso.network/ |
You can use your hardware wallet with MetaMask. You will simply need to:
- Connect your hardware wallet to MetaMask
- Add LUKSO as a custom network (cf. settings above)
- For Ledger users: Download the Ethereum app on your Ledger
- Switch the network to "LUKSO"
3rd party RPC providers​
We recommend developers to use these RPC providers over our public RPC URL as they provide better performance and stability.
The following third parties provide RPC endpoints to connect to LUKSO Mainnet.
| Provider | RPC URL |
|---|---|
| Thirdweb | https://42.rpc.thirdweb.com |
| SigmaCore | https://rpc.lukso.sigmacore.io (increased-limit packages available) |
| NowNodes | https://lukso.nownodes.io (requires API key) |
| Envio | https://lukso.rpc.hypersync.xyz (optimized read-only) |
Network Architecture​
The LUKSO's Blockchain runs an unmodified version of the Ethereum protocol. The network architecture consists of 2 to 4 clients:
- The consensus client running Casper the Friendly Finality Gadget (Casper FFG) plus LMD-GHOST fork choice algorithm (More on the Gasper Consensus)
- The execution client, running the Ethereum Virtual Machine
IPFS Storage​
We highly recommend that developers fetch and store profile or asset data using their own IPFS gateway solutions like Pinata or Infura for production needs, ensuring distribution and availability across the IPFS network. We do not provide an official gateway for uploading asset data. For development purposes, you may use the following RPC to fetch data:
- IPFS Download (for development only):
https://api.universalprofile.cloud/ipfs
This gateway is intended for development purposes. We do not guarantee any SLA, and rate limits may apply.