Historical Extraction

Corpus construction

Historical Extraction

Server-side HistoricalExtractor. Reads CKB mainnet through the validated adapter and stores raw observed plus normalized blocks, transactions and Cells. No discovery, ranking, rarity or valuation logic runs here.

LIVE CKB MAINNET DATA
Syncing with server

Run configuration

Extraction never starts automatically; an operator must initiate it.

Chain

CKB

—

Status

READY

Current height

—

target 99

Blocks processed

0

Transactions

0

Cells created

0

Cells consumed

0

Live Cells observed

0

RPC requests

0

Request rate

—

ceiling 5/s

Avg latency

—

P95 latency

—

Errors

0

retries 0

Current batch

—

Last checkpoint

—

Estimated completion

—

Batch manifests

SHA-256 fingerprint over the manifest for later reproducibility.

RangeBlocksTxsCellsFirst hashLast hashManifest SHA-256

Reconstructed Cells

Live CKB mainnet objects addressed by transaction hash + output index.

Object idHeightCapacity (shannons)Type scriptStatus

Extraction runs server-side only, throttled to a configured requests-per-second ceiling with bounded concurrency, exponential backoff and durable checkpoints. Consumption status reflects only relationships directly observable inside the indexed range; Cells marked LIVE have no observed consuming input within that range. Simulated BTC/ETH/LTC/DOGE/XMR research data is stored and displayed separately and is never mixed into these live CKB counts.