
Ethereum Log Bloom Filters: Useful but Not Exact
Learn what Ethereum log bloom filters can and cannot establish, why false positives matter, and how to verify actual matching event logs.
Read the guideIndexbase journal / ideas for builders
Understand the interfaces, questions and contracts behind a blockchain integration.
Follow the article feed19 articles / page 2 of 2

Learn what Ethereum log bloom filters can and cannot establish, why false positives matter, and how to verify actual matching event logs.
Read the guide
Distinguish contract creation input, receipt contract addresses and factory deployments, so a deployment inventory does not miss internal creations.
Read the guide
Compare Ethereum state reads with transaction history, and learn why a present balance cannot reveal every transfer that produced it.
Read the guide
Understand chain ID and network ID, prevent cross-network record collisions, and choose the correct identifier for API requests and storage keys.
Read the guide
Find a block near a timestamp with an explicit boundary rule, then verify the result before using it for a historical snapshot or report.
Read the guide
Model pending Ethereum transactions without treating a mempool observation as confirmation, and handle replacement, disappearance and delayed receipts.
Read the guide
Batch Ethereum JSON-RPC reads while matching responses by ID, handling individual errors and avoiding the assumption of one shared block snapshot.
Read the guideThe editorial approach
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.