Skip to content

Conversation

@MartinquaXD
Copy link
Contributor

@MartinquaXD MartinquaXD commented Jan 2, 2026

Description

#3982 introduced a small change that caused the settlement indexing to fail on lens.
The debug_traceTransaction calls are now failing with the error Alloy(ErrorResp(ErrorPayload { code: -32602, message: "Invalid params", data: Some(RawValue("missing field onlyTopCall at line 1 column 40")) })).
Previously we encoded a call with the arguments {"tracer": "callTracer"} (see here) but now due to how alloy's internal logic works we encode arguments like {"tracer": "callTracer", "tracerConfig": {}}. Alloy only skips encoding the tracer_config argument when it's null (see here) but GethDebugTracingOptions::call_tracer(CallConfig::default()) ends up putting an empty JSON object into tracer_config instead of null.

Changes

Update debug_traceTransaction arguments to not encode any tracerConfig.

How to test

Confirmed hypothesis with cast.
Current call:

cast rpc -r <LENS_RPC> debug_traceTransaction 0x4c1900589b428950ebd17008eecf5b6ca6e9698c5c02b450a8868fd94a30fb7c '{"tracer": "callTracer", "tracerConfig": {}}'
Error: server returned an error response: error code -32602: Invalid params, data: "missing field `onlyTopCall` at line 1 column 40"

Without additional tracerConfig:

cast rpc -r <LENS_RPC> debug_traceTransaction 0x4c1900589b428950ebd17008eecf5b6ca6e9698c5c02b450a8868fd94a30fb7c '{"tracer": "callTracer"}'
{"type":"call","from":"0x0000000000000000000000000000000000000000","to":"0x0000000000000000000000000000000000008001","gas":"0x3126b4","gasUsed":"0xf8d38"....

@MartinquaXD MartinquaXD requested a review from a team as a code owner January 2, 2026 08:20
@MartinquaXD MartinquaXD added this pull request to the merge queue Jan 2, 2026
Merged via the queue into main with commit fb41a0a Jan 2, 2026
19 checks passed
@MartinquaXD MartinquaXD deleted the fix-settlement-indexing-on-lens branch January 2, 2026 09:18
@github-actions github-actions bot locked and limited conversation to collaborators Jan 2, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants