Elysium DAS status
GET /v1/elysium/das/status
Endpoint and plans: Elysium RPC endpoint.
Live (2026-11-08). Use https://triport.io with X-API-Key and scope elysium:das. No query parameters.
curl https://triport.io/v1/elysium/das/status \
-H "X-API-Key: $TRIPORT_API_KEY"Illustrative response (synthetic counters and freshness, not a production measurement):
{
"chain": "elysium",
"chain_id": 99901,
"batches": 2,
"indexed_batches": 1,
"transactions": 1,
"seq_gaps": 0,
"seconds_since_newest_batch": 60,
"coverage": {
"source": "sequencer_batches",
"complete": false,
"includes": [
"signed transactions posted in Elysium sequencer batches since genesis (batch 1)",
"per transaction: sender, recipient, contract address for a creating transaction, nonce, value, input selector"
],
"excludes": [
"l1_to_l2_messages: deposits and other messages from the parent chain are counted per batch (l1_to_l2_messages) but not indexed per address",
"internal_calls: value transfers and contract creations made inside contract execution",
"execution_status: success or revert, gas used and logs are not part of batch data",
"unconfirmed: transactions accepted by the sequencer but not yet posted in a batch"
],
"from_batch_seq": 1,
"indexed_through": {
"batch_seq": 1,
"l2_block": 9,
"posted_at": "2026-11-08T00:00:00Z",
"posted_at_unix": 1794096000
},
"pending_batches": 0
}
}| Field | Meaning |
|---|---|
| chain, chain_id | elysium, 99901. |
| batches | Known batch rows, including no_data and unfinished batches. |
| indexed_batches | Batches whose signed transactions have been indexed. |
| transactions | Signed transactions counted in the index. |
| seq_gaps | Missing sequence rows from seq 0 through the highest known seq. This is separate from pending_batches. |
| seconds_since_newest_batch | Current time minus the posting time of the newest indexed batch, in seconds; null before any indexed batch. This is batch age, not indexing latency or RPC head lag. |
| coverage | Includes complete: false, exclusions, indexed_through and pending_batches. See coverage. |
Check both seq_gaps and coverage.pending_batches before accepting continuity. indexed_through is the newest indexed batch; an earlier gap can still exist. Zero gaps and zero pending batches do not make coverage complete: deposits by address, internal calls and creations, execution results and unposted transactions remain excluded. A growing batch age can reflect posting cadence; compare with RPC for the current head.