Indexed LUKSOBlockchain Data

LUKSO’s mainnet has produced blocks since May 2023, under the proof-of-stake design Ethereum uses: Casper FFG for finality, LMD-GHOST for fork choice, and a consensus layer running beside an execution layer. LYX is the native token and pays gas, and the network answers to chain ID 42. The difference sits above consensus. An account here is normally a contract rather than a key pair, a Universal Profile built on ERC725, with its permissions held by an attached Key Manager, so the sender of a transaction is a deployment that somebody controls. Assets follow LSP7 for fungible tokens and LSP8 for identifiable ones, and both notify the receiving profile through its Universal Receiver. LUKSO was founded by Fabian Vogelsteller, co-author of ERC-20, and its standards revise that work rather than extend it. Bytecode and gas semantics still come from Ethereum.

SonarX indexes LUKSO blocks and headers, transactions and receipts, decoded event logs, execution traces including internal value transfers, and token transfers and balances. Profile contracts and LSP assets are decoded against their own interfaces, then normalized into the model SonarX uses on every chain it covers.

Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request. Balance tables and the balance APIs can be enabled for LUKSO on request. Kafka streaming can be enabled for LUKSO on request.

Nothing here decodes on ERC-20 assumptions. An LSP7 or LSP8 transfer emits its own event, so a decoder keyed to the ERC-20 topic finds an empty chain where the assets actually moved. The account that sent it is usually a Universal Profile acting for a controller, which puts attribution behind the Key Manager’s permission list rather than behind the transaction signer. Profile metadata lives in an ERC725Y key-value store, so a name or an image is a state read at a height rather than an event to replay. Universal Receiver delegates add internal calls to most transfers, so traces carry weight that logs alone would miss.

Token-distribution analysis is the first workload, and here it means counting profiles rather than key pairs, because an asset’s holder is a contract with its own controller set. Creator-asset accounting is the second: LSP8 collections keep metadata in a key-value store, so issuance and ownership are read from state at a height rather than rebuilt from a transfer feed. Controller-permission research is the third, tracing which keys were allowed to act for a profile and when that changed, a question no ERC-20 chain poses. Token analytics covers the issuance side across chains, and teams studying creator networks usually pull Zora alongside this one.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. LUKSO history is available now, so a first delivery is provisioning rather than engineering. The published coverage matrix for every network SonarX indexes lives in the data documentation, and the rest of the catalogue is at all indexed chains.