GraphQL Cursor Pagination for Blockchain Records
Design GraphQL connections with stable cursors, deterministic event ordering and explicit range context so clients can resume a blockchain scan.
Read the guideIndexbase journal / ideas for builders
Blockchain data.
Worth understanding.
Practical guides to blockchain APIs, wallet data and the evidence behind a useful answer. Clear concepts, worked examples and better questions for your next integration.
Follow the article feed200 articles / page 11 of 13
Explore all guides
In-depth introductions and focused field guides, organised around practical questions.
Parquet vs JSON for Blockchain Data Exports
Choose columnar or record-oriented exports based on query patterns, schema needs and exact quantity handling rather than file extension alone.
Read the guidePartitioning Blockchain Tables by Network and Range
Choose table partitions around query and retention boundaries, while keeping stable event keys and avoiding assumptions that partitions enforce completeness.
Read the guideDurable Checkpoints for Incremental Blockchain Scans
Checkpoint accepted ranges only after durable processing, and use restart tests to prevent skipped pages or duplicate effects in incremental scans.
Read the guideBackpressure in Real-Time Blockchain Data Consumers
Bound queues and consumer concurrency when event arrival exceeds processing capacity, while preserving durable progress and explicit overload behaviour.
Read the guideDead-Letter Queues for Undecodable Blockchain Events
Quarantine failed records with safe diagnostic context, preserve original evidence and replay deliberately after correcting a decoder or schema problem.
Read the guideChunking Blockchain Range Queries Safely
Split large block ranges into bounded chunks, preserve inclusive boundary rules and adapt to response-size limits without skipping or overlapping records incorrectly.
Read the guide
Archive vs Pruned Node Data for Historical Reads
Distinguish retained blocks from retained historical state, and test the exact balance or contract query needed before assuming an endpoint supports it.
Read the guideReading SQL Query Plans for Blockchain Analytics
Measure scans, joins and row estimates before optimising blockchain queries, and preserve the result contract while improving execution performance.
Read the guideDatabase Types for Exact Blockchain Quantities
Store large blockchain integers and decimal values without silent overflow or floating-point loss, and define typed boundaries for APIs and exports.
Read the guideMaterialised Views for Blockchain Dashboards
Use precomputed blockchain summaries with explicit refresh and correction policies, while preserving links back to accepted event evidence.
Read the guideETL vs ELT for Blockchain Analytics Workflows
Choose transformation placement around evidence retention, schema evolution and consumer needs, rather than treating ETL or ELT as a universal architecture.
Read the guide
Wallet Login Nonces and Replay Protection
Protect wallet-signature login with single-use challenges, domain binding and expiry, without treating a reusable signed message as a permanent session.
Read the guideContract Wallet Signatures and ERC-1271 Verification
Verify contract-wallet signatures using the wallet’s supported interface and historical context, rather than assuming every account has a recoverable EOA signature.
Read the guideTenant Isolation in Wallet Data APIs
Enforce ownership on every wallet-data resource request, and prevent guessed IDs or shared caches from exposing another customer’s imports and reports.
Read the guideAPI Scopes vs Product Entitlements
Separate what a key is permitted to request from what an account’s plan enables, and enforce both checks consistently on each data operation.
Read the guideThe editorial approach
Useful questions.
Traceable explanations.
Each guide starts with a concrete developer question and separates technical observations from the interpretation an application adds. Worked examples use illustrative values; references point to standards and technical documentation.
Published by Indexbase. Explore related guides as your requirements develop, from a first data question to a more deliberate integration workflow.