Blockchain data that
comes to you.

BlockHook operates a dedicated Finality Monitor per network that tracks canonical chain state in real time. When a reorg is detected — even deep reorgs of 10+ blocks — the system automatically invalidates affected events, reprocesses the canonical fork, and dispatches idempotent correction payloads with a reorg_correction status flag. Your application receives exactly-once semantics: no duplicates, no gaps, no stale state. All correction events include the original event_id for deterministic reconciliation.

BlockHook implements at-least-once delivery with configurable retry policies for up to 48 hours. Failed deliveries are routed to a dead-letter queue with full payload retention. Once your endpoint recovers, events are replayed in strict chronological order. Enterprise plans include webhook HMAC signature verification, mutual TLS (mTLS) authentication, and a real-time Delivery Dashboard with per-event status tracking, latency percentiles, and one-click manual replay.

Each supported network has a dedicated decoder pipeline that handles the specifics of its execution model — EVM logs and traces, Solana instructions, UTXO inputs/outputs, TON messages, and TRON's Protobuf format. These are normalized into a unified JSON schema with consistent fields for sender, receiver, value, token metadata, and confirmation depth. This means your backend consumes a single, predictable payload structure regardless of whether the source event originated on Ethereum, Solana, Bitcoin, or any other supported chain.

BlockHook maintains direct peering with validator nodes and operates private, geo-distributed RPC clusters. For EVM-compatible networks, the p95 latency from block propagation to parsed JSON delivery is under 300ms. Solana and TON events are typically delivered within 400ms. All latency metrics are contractually defined in our Enterprise SLA, and customers have access to a real-time observability dashboard with per-event latency breakdowns, delivery success rates, and historical percentile charts.

Yes. Enterprise customers can initiate retroactive indexing for any smart contract or address from its genesis block forward. Historical events are decoded using the same normalization pipeline as live data and can be delivered via Webhook, Kafka, or exported as Parquet/JSON batches to your S3-compatible storage. This is ideal for migrating to BlockHook from a custom indexer, bootstrapping analytics pipelines, or auditing transaction history for compliance purposes.

Our Enterprise Streams infrastructure is horizontally scalable and processes over 100,000 decoded events per second per network with sub-millisecond internal routing. Each customer receives dedicated Kafka partitions with isolated throughput guarantees. During stress scenarios — such as high-volume NFT mints or DeFi liquidation cascades — the system auto-scales ingestion capacity with zero impact on delivery latency or ordering guarantees.

BlockHook supports multi-level filtering that goes far beyond simple address matching. You can define rules by contract address, specific method signature, event topic, parameter value ranges, minimum transfer thresholds, and even cross-reference conditions between sender and receiver. Filters are compiled into optimized matching engines at the ingestion layer, so irrelevant events are dropped before they reach your delivery pipeline — reducing noise and lowering bandwidth costs. Filter configurations are version-controlled and can be updated via API or the management dashboard with zero downtime.

Our onboarding team provides a dedicated migration engineer who audits your current data pipeline — whether you're coming from Alchemy, QuickNode, Moralis, or a self-hosted node setup. We run a parallel shadow deployment where BlockHook delivers events alongside your existing solution, allowing you to validate payload parity before cutover. Most integrations are production-ready within 48 hours. Enterprise clients also receive a custom Terraform/Pulumi module for infrastructure-as-code provisioning.