feat(structlog): add call frame tracking to identify EVM call contexts #40
Conversation
This file contains hidden or 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
Introduce CallTracker to assign sequential frame IDs and maintain call paths during opcode traversal. This enables accurate identification of which contract call each opcode belongs to, even when the same contract is called multiple times. Extend Structlog with CallFrameID and CallFramePath fields to persist the tracking information alongside each opcode record. Update extractCallAddress to handle all CALL-type opcodes (CALL, CALLCODE, DELEGATECALL, STATICCALL) for complete call target extraction.
feat: detect CREATE/CREATE2 opcodes and fetch contract address from receipt refactor: replace extractCallAddress with extractCallAddressWithCreate to handle contract creation addresses
… trace-based computation - Remove fetchCreateAddress and hasCreateOpcode helpers - Introduce ComputeCreateAddresses to extract addresses directly from trace - Update extractCallAddressWithCreate signature to accept index and map - Rename queue name from "transaction-structlog" to "transaction_structlog" - Expand test coverage for nested and failed CREATE scenarios
The root frame now starts at depth 1 instead of 0 to match the actual EVM structlog output, where execution begins at depth 1. All tests updated to reflect the new depth semantics.
…om child gas Introduce GasSelf to represent the gas consumed by an opcode *excluding* any gas spent in child frames. For CALL/CREATE opcodes this yields the pure call overhead (warm/cold access, memory expansion, value transfer); for all other opcodes GasSelf equals GasUsed. This allows accurate aggregation of total execution gas without double counting. - Add ComputeGasSelf() helper that subtracts the sum of *direct* child GasUsed values from each CALL/CREATE opcode’s GasUsed. - Extend Structlog struct and ClickHouse schema with new GasSelf column. - Update both ProcessTransaction() and ExtractStructlogs() to populate the new field. - Provide extensive unit tests covering nested, sibling and edge cases.
…odes test(structlog): add comprehensive format_address tests for 20-byte padding refactor(structlog): introduce formatAddress to normalize stack values to 42-char addresses
…ic frames Replace heuristic precompile check with go-ethereum's canonical list to avoid mis-classifying early EOAs/contracts as precompiles. Tighten the EOA detection logic to only create synthetic frames when call depth remains unchanged (depth == nextDepth) instead of the previous nextDepth <= depth, eliminating phantom frames for failed calls and out-of-gas scenarios.
* master: fix(ethereum): improve error message for unsupported chain IDs refactor(ethereum): change ChainID from int32 to int64 across services and processors
Savid
approved these changes
Jan 22, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem:
When you trace a transaction, you get a list of every opcode executed. But you can't easily answer: "Which contract was this opcode running inside?"
For example, if
contract Acallscontract B, andBcallsC, you get a flat list like:The problem: depth alone isn't enough. If A calls B, returns, then calls C - both B and C are at depth 2, but they're different call frames.
This PR:
CallTracker)Assigns a unique sequential ID to each call frame:
call_frame_id: Unique ID within the transaction (0, 1, 2, 3...)call_frame_path: The path from root to current frame (e.g.,[0, 1, 2]meansroot→frame1→frame2)Now we can group opcodes by which contract execution they belong to, even when the same contract is called multiple times.
gas_selfFieldA new gas metric that doesn't double count child frame gas:
gas_used: Total gas consumed (includes child frames)gas_self: Just this opcode's overhead (excludes child frames)Example for a
CALL:gas_used= 23,858 (overhead 2,600 + child consumed 21,258)gas_self= 2,600 (just theCALLoverhead)SUM(gas_self)across all opcodes = total transaction gas (no double counting).CREATE/CREATE2Address ResolutionFor contract creation opcodes, fetches the newly created contract address from the transaction receipt and populates call_to_address.
When a
CALLtargets an EOA (i.e., a wallet with no code), the depth doesn't increase. The PR emits a synthetic structlog to represent this EOA frame, keeping the call frame tracking consistent.