Indexed EDUBlockchain Data

EDU Chain is an Arbitrum Orbit chain built by Open Campus for education applications, and it opened to all users in January 2025. It runs as a Layer 3: transactions are batched to Arbitrum One, which in turn settles to Ethereum, so the chain sits two hops from L1 finality rather than one. Data availability follows the AnyTrust design, where a committee attests that the transaction data is available and the attestation travels upward in place of the data. Gas is paid in EDU, the Open Campus token, rather than in ETH, and the network answers to chain ID 41923. Execution is the EVM, with twenty-byte addresses and the usual token standards, so contracts written for Ethereum deploy without change. The applications on it are education-facing, which makes its contract mix credentials and payments rather than liquidity pools.

SonarX indexes EDU Chain blocks and headers, transactions and receipts, decoded event logs, execution traces including internal value transfers, and token transfers and balances. Batching and deposit records stay identifiable rather than folded into user activity.

Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request. Point-in-time balance tables are available for EDU Chain, and the rest can be enabled on request. Kafka streaming can be enabled for EDU Chain on request.

Three chains stand between a transaction here and Ethereum, and the data has to say so. A record is produced on EDU Chain, batched to Arbitrum One, and settled only once Arbitrum’s own posting to Ethereum clears, which gives every record three relevant timestamps instead of one. AnyTrust is the second point: transaction data stays with a committee, so this history cannot be rebuilt from L1 data and has to be indexed from the chain itself. Gas in EDU is the third, because a fee series here is denominated in a bridged token, so cost comparisons need a conversion.

Token accounting on EDU is the first workload: the asset pays for gas here, is issued and traded elsewhere, and moves between the two, so supply and distribution hold together only when both sides are read against each other. Credential and record analysis is the second, and it is particular to this chain, because issuing a certificate is a contract event and its history is the sequence of issuances, transfers and revocations rather than a balance. Application analytics is the third, counting actions per contract and per account from decoded logs. Distribution work of this kind runs through tokens and payments, and teams surveying Orbit chains usually pull Xai 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. EDU Chain history is available now, with batching records kept beside the transactions they carry. 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.