-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add support for eth_getBlockReceipts RPC method (#102)
### TL;DR Added support for using `eth_getBlockReceipts` instead of `eth_getLogs` and enhanced transaction data storage. ### What changed? - Introduced `eth_getBlockReceipts` RPC method support - Added new configuration options for block receipts - Enhanced transaction structure with additional fields from receipts - Updated ClickHouse schema to accommodate new transaction fields - Improved serialization logic to handle block receipts data ### How to test? 1. Update the configuration file to enable block receipts: ```yaml rpc: blockReceipts: enabled: true blocksPerRequest: 500 batchDelay: 100 ``` 2. Run the indexer with the updated configuration 3. Verify that transactions in the ClickHouse database contain the new fields (e.g., `contract_address`, `gas_used`, `status`) 4. Check the logs to ensure that `eth_getBlockReceipts` method is being used when enabled ### Why make this change? This change improves the efficiency and completeness of data collection: 1. Using `eth_getBlockReceipts` can be more efficient than fetching logs and receipts separately 2. Additional transaction data from receipts provides more comprehensive information for analysis and querying 3. The enhanced schema allows for more detailed transaction insights without the need for additional RPC calls
- Loading branch information
Showing
12 changed files
with
337 additions
and
69 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.