↗
Transactions & UTXOs
Inputs, outputs, amounts, fees, inclusion height, slot and confirmation state. Designed for deposit and withdrawal processing.
Historical explorer data exists; complete managed API is planned. PRODUCT ROADMAP / DATA + DEV CLOUD
Data you can trace.
Tools you can
build on.
Bloch Data + Dev Cloud is the proposed layer for canonical network records, developer integrations and financial-market reconciliation built around verifiable evidence.
The public explorer and historical index are available today. The managed data platform described here is in development and qualification.
01 / THE DATA PATH ROADMAP VIEW
ORIGINBloch L1Blocks · transactions
validators · finality
validators · finality
CANONICAL VIEWBloch DataIndex · provenance
reorg-aware records
reorg-aware records
DELIVERYDev CloudAPIs · events
SDKs · sandbox
SDKs · sandbox
NETWORK EVIDENCEVERSIONED CONTRACTSREPRODUCIBLE WORKFLOWS
01 / BLOCH DATA
Network data with a clear origin.
One consistent view of the chain, built for teams that need to explain every balance change and transaction decision.
▦
Blocks & finality
Block ancestry, validator context and evidence that distinguishes observed inclusion from a qualified finality claim.
Finality reporting requires independent qualification.◎
Addresses & activity
Address histories, balances and changes over time with a path back to the underlying network records.
Coverage and provenance targets for the complete index.⟲
Canonical history
Stable identifiers, explicit reorganization handling and recoverable indexing from a reviewed network anchor.
An EVM-side anchored indexer core exists; a durable Bloch Data service is planned.A CONTRACT WORTH BUILDING ON
From a txid to a complete record.
The target transaction interface returns the fields an integrator needs to reconcile a transfer and follow its status.
- Canonical inputs and outputs with native amounts
- Block height, slot and confirmation progress
- Explicit inclusion, finality and reorganization status
- Network identity and source provenance
TRANSACTION RECORDPROPOSED SCHEMA
txidtransaction identifier
inputs[]source outpoints + amounts
outputs[]destinations + amounts
block.height / slotinclusion position
confirmationschain depth
finality.statusqualified evidence state
canonicalreorg-aware state
Every field should have a documented meaning and source.
02 / FINANCIAL-MARKET DATA SERVICES
A ledger for evidence.
A workflow for reconciliation.
Proposed software for trading venues, exchanges, banks, custodians and asset platforms that need to connect positions and movements to their source records.
Product stage / proposedProof Ledger is a buildable, non-settlement software concept. The remaining market workflows depend on partner data, controls and qualification.
01 / PROOF LEDGERPROPOSED
Position and reserve evidence
A traceable operational subledger that links positions, balances and reserve snapshots to source events. Compare internal views, explain differences and export evidence for audit.
- Position lineage and snapshot history
- Reserve and liability evidence
- Reproducible audit exports
02 / RECONCILIATIONPROPOSED
Find the break. Follow the cause.
Match executions, allocations, cash and asset movements across partner systems and network records. Route unmatched items into review with timestamps, owners and supporting evidence.
- Source-to-source matching rules
- Exception queues and investigation trail
- Cutoff and completeness checks
03 / ASSET LIFECYCLEDESIGN
Events across an asset's life
Normalize issuance, redemption and corporate-action data for eligibility, entitlements and lifecycle reconciliation. Partner systems retain legal authority over the asset and its records.
- Event provenance and version history
- Entitlement and position comparison
- Partner-controlled approvals
04 / SETTLEMENT EVIDENCERESEARCH
See what settled, and when.
Compare linked asset and cash obligations, confirmations and finality evidence for partner DvP/PvP research. Actual settlement requires authorized operators, qualified cash legs and risk controls.
- Pre- and post-settlement checks
- Linked-obligation evidence
- Exception and recovery records
WHO THIS SERVESOne evidence model.
One evidence model.
Different operating desks.
Trading venues & exchanges
Reconcile executions, member positions, asset balances and exceptions across internal and external records.
Banks & custodians
Compare cash and asset movements, account positions and settlement status with auditable source references.
Issuers & asset services
Track lifecycle events, entitlements and receivables through partner-controlled data contracts.
Operating boundary
Bloch Data proposes data and workflow software. Partners remain responsible for their regulated books, custody, compliance and settlement. No live exchange, bank, payment-rail or DvP/PvP integration is claimed.
03 / DEV CLOUD
Build once. Integrate with confidence.
Developer tools that turn raw node access into predictable application workflows.
API / PLANNED
Versioned read APIs
Documented transaction, block and address contracts with pagination, stable identifiers and compatibility rules.
EVENTS / PLANNED
Reliable webhooks
At-least-once delivery, idempotency keys, retries and replay for deposits, confirmations and finality changes.
TOOLS / INCREMENTAL
SDKs & examples
Working client examples for exchange, wallet and application flows, with explicit network and version binding.
SANDBOX / PLANNED
Reproducible sandbox
Local node, fixtures and transaction simulation for testing integrations before mainnet submission.
04 / TRUST MODEL
Useful data needs visible boundaries.
A data service should show what the network observed, how the index derived it, and which claims still need independent proof.
01Chain identity
Bind every record to the expected network, chain and genesis.
02Canonicality
Expose reorganization and replay behavior instead of silently replacing history.
03Finality evidence
Separate confirmations from finality; never treat a single node claim as independent proof.
04Operational quality
Measure index freshness, event integrity, availability and recovery time before service commitments.
05 / DELIVERY ROADMAP
Ship the evidence before the promise.
Milestones follow the Bloch Inc G0–G1 gates and the existing indexer implementation boundary.
Public visibility
Explorer, historical records and published integration components. An anchored EVM canonical indexer core exists in code.
Not a managed Dev Cloud service.Durable data
Persist canonical and orphan transitions atomically, recover after restart and validate input adapters.
Prerequisite for dependable API reads.Developer access
Versioned APIs, documented schemas, SDK examples and idempotent event delivery.
Qualification before public service claims.Managed Dev Cloud
Sandbox, monitoring, support procedures and measured availability for pilot users.
Availability and terms depend on qualification.Market-services sequence
Proof Ledger and reconciliation data contracts first; asset lifecycle only with authorized partners; DvP/PvP evidence pilots only after finality, cash-leg and operational-risk qualification.
BUILD ON WHAT YOU CAN VERIFY
More than a data feed.
A dependable starting point.
Bloch Data + Dev Cloud is being shaped for exchanges, trading venues, banks, custodians, wallets and builders that need traceable records and repeatable reconciliation.