{"id":"on-chain-data","hidden":false,"ipfs":"QmZekbPAVrLcDXCdtUEa6U4jrcen25kxkaTWW2GH37WERB","language":"en","transactionHash":"0x58d59ee6fe558f3993d59e0570fb9dd373c81ab9bd55e7e02c922154e5f455c8","created":"2026-09-11T14:46:09.656Z","updated":"2026-09-11T14:46:09.656Z","title":"On-Chain Data","summary":"On-chain data is information recorded directly on a blockchain — transactions, blocks, smart contract interactions, token transfers, and wallet balances — that the network validates and stores as a public, immutable ledger distinct from off-chain data.","content":"**On-chain data** is the information recorded directly on a [blockchain](https://iq.wiki/wiki/blockchain), including every transaction, [block](https://iq.wiki/wiki/block), [smart contract](https://iq.wiki/wiki/smart-contract) interaction, token transfer, and wallet balance that the network validates and stores permanently. \n\nIt is public and immutable, meaning anyone can read it and no single party can quietly alter it after finalization. Because on-chain data lives on the [blockchain](https://iq.wiki/wiki/blockchain) itself, it can be verified by anyone running a [node](https://iq.wiki/wiki/node), which distinguishes it from data stored in a private company database that only the holding party can confirm.[[1]](#cite-id-c21i3hlxnz)​\n\nOn-chain data is pseudonymous rather than anonymous: addresses are strings of characters whose full history is public, but the ledger does not automatically reveal who a wallet belongs to or the intent behind a transaction.[[2]](#cite-id-6830b66c05)[[3]](#cite-id-960126a281) \n\nA transaction may show that address A sent tokens to address B, but the raw record does not indicate whether address A is an exchange hot wallet or whether the transfer represents a payroll payment. This gap between what happened and what it means is central to why raw on-chain records, though complete and verifiable, are difficult to use without additional processing.[[1]](#cite-id-c21i3hlxnz)[[2]](#cite-id-6830b66c05)​ These verifiable records form the substrate for newer applications such as tokenized real-world assets, institutional [stablecoin](https://iq.wiki/wiki/stablecoin) settlement dashboards, [AI agents](https://iq.wiki/wiki/ai-agents) that consume [blockchain](https://iq.wiki/wiki/blockchain) context, and on-chain governance and security analytics, all of which ultimately rely on the same underlying ledger entries.\n\n## What It Covers\nOn-chain data comprises several distinct categories of record, each capturing a different aspect of network activity. [Blocks](https://iq.wiki/wiki/block) are containers, each stamped with a time and linked to the one before it, forming the chain that gives the technology its name. Transactions are records of value moving from one address to another. \n\n​[Smart contract](https://iq.wiki/wiki/smart-contract) events, also called logs, capture what happened inside a program, such as a token swap or a [collateral](https://iq.wiki/wiki/collateral) deposit. Balances reflect what each address holds at a given moment. Together these records document transactions, token transfers, contract logs, and balances across the network.[[1]](#cite-id-c21i3hlxnz)​ Protocol-level metrics such as [total value locked (TVL)](https://iq.wiki/wiki/tvl), available liquidity, or [validator](https://iq.wiki/wiki/validator) participation are derived by aggregating these primary records, but they remain secondary views built from the underlying ledger state rather than new categories of data.\n\nOn-chain data is contrasted with off-chain data, which lives in private systems and can only be verified by the party holding it. Off-chain examples include prices from centralized exchanges, identity records such as know-your-customer (KYC) information, and anything computed away from the [blockchain](https://iq.wiki/wiki/blockchain). \n\nThe defining distinction is verifiability: on-chain data resides on the ledger and can be checked by any [node](https://iq.wiki/wiki/node), while off-chain data resides in private databases outside the reach of independent verification.[[1]](#cite-id-c21i3hlxnz)​\n\n## How It Is Produced and Processed\nOn-chain data follows a defined lifecycle from the moment a transaction is created to the point where it becomes readable analytics. \n\nA transaction is first submitted by a user or an application. [Validators](https://iq.wiki/wiki/validator) or miners then verify, order, and include the transaction in a [block](https://iq.wiki/wiki/block) according to the network's consensus rules. Once a [block](https://iq.wiki/wiki/block) is added and confirmed, its contents become part of the permanent ledger, and every full [node](https://iq.wiki/wiki/node) on the network stores a copy of that record.[[1]](#cite-id-c21i3hlxnz)​\n\nThe stored record is encoded in low-level formats and is not immediately human-readable. Making it usable requires decoding [smart contract](https://iq.wiki/wiki/smart-contract) calls, translating hexadecimal values, and mapping token addresses to recognizable names. On higher-volume layer-one chains and rollups, specialized indexing networks and data providers continuously ingest new [blocks](https://iq.wiki/wiki/block) and events so that these raw records can be queried in near real time without every organization running its own full indexing stack. \n\nBeyond a single chain, records drawn from different [blockchains](https://iq.wiki/wiki/blockchain) must be standardized and enriched by normalizing schemas, labeling known addresses, and organizing activity into categories such as transfers, swaps, or loans. This processing pipeline is what turns a permanent but opaque ledger into information that firms and researchers can act on.[[5]](#cite-id-3ee66491a9)[[6]](#cite-id-afb5008260)[[1]](#cite-id-c21i3hlxnz)​\n\n## Technical Challenges\nSeveral properties of [blockchains](https://iq.wiki/wiki/blockchain) make their data hard to work with in practice. Different [blockchains](https://iq.wiki/wiki/blockchain) structure data differently, so formats must be standardized before activity can be compared across chains. \n\nAs activity moves across many layer-one chains, layer-two networks, and rollups, data is fragmented into different formats and execution environments. Indexers must reconcile differing event schemas, address formats, and bridge semantics to present a coherent cross-chain view. Emerging data-availability layers and techniques such as [Ethereum](https://iq.wiki/wiki/ethereum)'s EIP‑4844 data blobs change where transaction data is stored and for how long, which in turn affects how historical records are accessed, reconstructed, and archived.[[5]](#cite-id-3ee66491a9)[[6]](#cite-id-afb5008260) \n\n​[Smart contracts](https://iq.wiki/wiki/smart-contract) hide meaning because their outputs are encoded; decoding a swap on a [decentralized exchange (DEX)](https://iq.wiki/wiki/decentralized-exchange) or a lending [liquidation](https://iq.wiki/wiki/liquidation) requires knowing the specific structure of the contract involved. Addresses are pseudonymous strings rather than names, so determining which addresses belong to which entities requires ongoing research and judgment.[[1]](#cite-id-c21i3hlxnz)[[2]](#cite-id-6830b66c05)​\n\nA further complication is that some [blockchains](https://iq.wiki/wiki/blockchain) reorganize recent [blocks](https://iq.wiki/wiki/block). Because of these reorganizations and the way finality is reached, data pipelines must account for the possibility that recent [blocks](https://iq.wiki/wiki/block) may change, avoiding the reporting of transient data as though it were final. \n\nTreating recent, unconfirmed data as settled can produce numbers that later change, which is dangerous for settlement or reporting purposes. These finality assumptions, combined with encoded contract outputs and pseudonymous addressing, are the principal reasons raw on-chain data is difficult to consume directly.[[1]](#cite-id-c21i3hlxnz)​\n\n## Uses and Applications\nAccurate on-chain data enables several capabilities that depend on a verifiable, shared record. It allows faster reconciliation, since firms settling [stablecoin](https://iq.wiki/wiki/stablecoin) payments can confirm receipt against the ledger directly rather than waiting on intermediaries. \n\nIt supports real-time risk monitoring, letting participants watch [collateral](https://iq.wiki/wiki/collateral) ratios move as they happen. It provides auditable reporting, because a fund holding tokenized assets can point to the chain as proof of its holdings. It also permits verifiable research, since academics can reproduce results when the underlying data is public.[[1]](#cite-id-c21i3hlxnz)​ In [decentralized finance (DeFi)](https://iq.wiki/wiki/defi), for example, dashboards that track liquidity, [leverage](https://iq.wiki/wiki/leverage), and [liquidation](https://iq.wiki/wiki/liquidation) cascades are built directly from contract events and pool balances. Tokenized treasuries and other real-world-asset platforms rely on the same independently verifiable records to show which wallets hold specific instruments and how those holdings change over time. Compliance and forensic teams reconstruct flows of funds, monitor sanctions exposure, and investigate hacks by following raw transfers and contract interactions, while emerging [AI agents](https://iq.wiki/wiki/ai-agents) and automated applications consume this on-chain context to trigger actions such as rebalancing, payments, or governance votes based on ledger state rather than private feeds.\n\nThe users of on-chain data span finance, technology, and public institutions. Banks and payment companies use it to track [stablecoin](https://iq.wiki/wiki/stablecoin) settlement and prove where funds went. Asset managers use it to report on tokenized holdings. Wallet and fintech products use it to enrich the user experience. Researchers use it to benchmark markets, and regulators use it to monitor systemic exposure across the financial system.[[4]](#cite-id-72faa77223) Compliance providers and law-enforcement agencies treat on-chain records as a core input to investigations, and developers building AI-augmented wallets or trading systems incorporate on-chain state as a trusted signal alongside other data sources. \n\nSome wallet and analytics products provide on-chain context across tens of millions of wallets.[[1]](#cite-id-c21i3hlxnz)​\n\n## Risks and Open Questions\nSeveral limitations qualify the value of on-chain data. \n\nThe first is interpretation risk: the ledger records what happened, not intent, and address labeling is a judgment call on which different providers can disagree. \n\nThe second is a privacy tension, because full transparency means transaction histories are permanently public, which can be uncomfortable for those expecting financial privacy. New privacy-preserving designs, including zero-knowledge proofs and selective disclosure schemes, aim to hide sensitive details while still allowing verification, but their long-term effectiveness, usability, and regulatory treatment remain open questions.[[7]](#cite-id-0e638c67b6) \n\nThe third is off-chain blind spots, since activity that settles off the chain or relies on centralized intermediaries does not appear in on-chain data even when it moves the market.[[1]](#cite-id-c21i3hlxnz)​ Experiments with zero-knowledge attestations and oracles that commit summaries of off-chain states to the ledger can narrow this gap but do not eliminate it. \n\nTwo further issues concern completeness and timing. \n\nFragmentation arises because activity is spread across many [blockchains](https://iq.wiki/wiki/blockchain) and layer-two networks, so a single-chain view can misstate the true scale of a market. Finality assumptions pose a related danger: treating recent, unconfirmed data as final can produce figures that later change, a particular hazard for settlement or reporting. \n\nOn-chain data is, in summary, the shared and verifiable record of activity on public [blockchains](https://iq.wiki/wiki/blockchain), and its value depends on whether raw records can be read accurately, standardized across chains, and delivered in actionable form. Investigators, courts, and regulators increasingly treat base-layer on-chain records as primary evidence for governance disputes and enforcement actions, but they must distinguish those raw entries from third-party labels and interpretations layered on top.[[4]](#cite-id-72faa77223) \n\nAs [stablecoins](https://iq.wiki/wiki/stablecoin), tokenized assets, and on-chain lending grow, the ability to trust that data is expected to distinguish firms that can operate in this environment from those that cannot.[[1]](#cite-id-c21i3hlxnz)​","recentActivity":null,"operator":{"id":"0x1E23b34d3106F0C1c74D17f2Cd0F65cdb039b138"},"categories":[{"id":"glossary","title":"Glossary"}],"tags":[],"images":[{"id":"QmUjyGthT5MCEhZgmdyA6VoZf4ePnPAh3RmLFShDkkhzVk","type":"image/jpeg, image/png"}],"media":[],"linkedWikis":{"founders":[],"blockchains":[],"speakers":[]},"events":[{"id":"d2cb1e7c-5de7-4d9c-a02e-f5df716e1ed1","type":"DEFAULT","date":"2026-07-01","multiDateStart":null,"multiDateEnd":null,"country":null,"continent":null,"title":"Article defining on-chain data published","description":"Alex Nin published “What Is Onchain Data? A Clear Guide to Blockchain Data,” a 7‑minute read that summarizes definitions, challenges, use cases, and examples of onchain data and contrasts it with offchain data.","link":"https://www.allium.so/blog/what-is-onchain-data-a-clear-guide-to-blockchain-data/"}],"founderWikis":[],"blockchainWikis":[],"metadata":[{"id":"references","value":"[{\"id\":\"c21i3hlxnz\",\"url\":\"https://www.allium.so/blog/what-is-onchain-data-a-clear-guide-to-blockchain-data/\",\"description\":\"Definition of onchain data as public, immutable blockchain records\",\"timestamp\":1789137158031},{\"id\":\"6830b66c05\",\"url\":\"https://ar5iv.labs.arxiv.org/html/2203.09360\",\"description\":\"Academic paper explaining Ethereum’s pseudonymous accounts and de-anonymization methods\",\"timestamp\":1789246076689},{\"id\":\"960126a281\",\"url\":\"https://ar5iv.labs.arxiv.org/html/2205.13882\",\"description\":\"Research on Bitcoin’s pseudonymity and transaction clustering heuristics\",\"timestamp\":1789246076689},{\"id\":\"72faa77223\",\"url\":\"https://www.bis.org/publications/project-atlas-mapping-world-decentralised-finance\",\"description\":\"BIS Project Atlas overview combining on-chain and off-chain data for regulators\",\"timestamp\":1789246076689},{\"id\":\"3ee66491a9\",\"url\":\"https://sqd.dev/learn/multi-chain-indexing/\",\"description\":\"Technical explainer on multi-chain on-chain data indexing and cross-chain analytics\",\"timestamp\":1789246076689},{\"id\":\"afb5008260\",\"url\":\"https://www.mdpi.com/2079-9292/15/8/1741\",\"description\":\"HyperCross framework for semantic, zero-knowledge indexing of cross-chain data\",\"timestamp\":1789246076689},{\"id\":\"0e638c67b6\",\"url\":\"https://blog.thirdweb.com/zero-knowledge-proofs-in-2026-the-developer-guide-to-zk-rollups-privacy-and-scalable-smart-contracts/\",\"description\":\"Developer guide to zero-knowledge proofs for privacy and verification on blockchains\",\"timestamp\":1789246076689}]"},{"id":"previous_cid","value":"QmZekbPAVrLcDXCdtUEa6U4jrcen25kxkaTWW2GH37WERB"},{"id":"commit-message","value":"Expand and summarize On-Chain Data wiki (+401 words)"},{"id":"previous_cid","value":"QmZekbPAVrLcDXCdtUEa6U4jrcen25kxkaTWW2GH37WERB"}],"user":{"id":"0x8af7a19a26d8fbc48defb35aefb15ec8c407f889"},"author":{"id":"0x1E23b34d3106F0C1c74D17f2Cd0F65cdb039b138"},"views":27}