Indexed StoryBlockchain Data

Story is a proof-of-stake Layer 1 with an EVM execution environment, live on mainnet since 2025 and built for one job: putting intellectual property onchain in a form that can be licensed and paid for. Contracts, twenty-byte addresses and event logs work as they do on Ethereum, but the primitives above them are the network’s own. A registered work, called an IP asset, is held as a token with an account contract bound to it, so the asset itself can hold funds and sign for agreements. License terms attach to that asset as machine-readable terms rather than as a document, and issuing a license produces a token the licensee holds. Derivative works are registered against the work they came from, which turns the registry into a graph. IP is the native token and pays for gas and staking.

SonarX indexes Story end to end: blocks and headers, transactions and receipts, event logs decoded against contract ABIs, execution traces including internal value transfers, and token transfers and balances. The same normalized model is used on every chain SonarX covers, so registrations and royalty movements join to holdings elsewhere without a translation layer.

Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request. The real-time balances API and the batch wallets, tokens and balances API are available for Story, and the rest can be enabled on request. Kafka streaming can be enabled for Story on request.

The hard part is that the interesting object is a relationship, not a row. Registrations, license issuances and royalty payments are emitted by a small set of protocol contracts rather than by each asset, so the log stream is narrow while the structure behind it is deep: one payment can be owed upward through several generations of derivative works. SonarX indexes registrations and the links between assets alongside transfers, so the graph can be rebuilt as it stood at any block. Asset-bound accounts add a second wrinkle, because funds can sit with an asset rather than with a person, and an address that never signed a transaction still holds a position.

Attribution is the first workload and the one specific to this chain: given a payment, which works upstream have a claim on it, and what did the license terms in force at the time say. Registry analysis is the second, measuring what is being registered, by whom, and how much of it is derivative rather than original. Holder and treasury reporting is the third, since assets, license tokens and the accounts bound to them all carry balances that a normal wallet view would miss, and restating those as at a reporting date is a point-in-time question rather than a snapshot. Token-level supply and distribution work runs through tokens and payments, and teams comparing 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. Story history and the balance APIs are 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.