Skip to content

fix: correct debug method availability and remove unsupported 4byteTracer #37

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Troublor merged 2 commits into from
Apr 9, 2026
Merged

fix: correct debug method availability and remove unsupported 4byteTracer #37

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ccaecf8
fix: correct debug method availability and remove unsupported 4byteTr…
Troublor Apr 9, 2026
dbcd37d
fix: drop unverifiable rate limit claim per review
Troublor Apr 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 5 additions & 6 deletions docs/dev/send-tx/debugging.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,15 +6,15 @@ description: Debug failing transactions on MegaETH — trace with debug_traceTra

MegaETH provides two ways to debug transactions:

1. **`debug_*` RPC methods** — trace transactions via JSON-RPC (requires a managed RPC endpoint)
1. **`debug_*` RPC methods** — trace transactions via JSON-RPC
2. **`mega-evme`** — replay or simulate transactions locally with full tracing

## Debug RPC Methods

Standard Ethereum debug methods — `debug_traceTransaction`, `debug_traceCall`, and `debug_traceBlockByNumber` — are available through managed RPC providers but **not on the public MegaETH RPC endpoint**.
Use a provider such as [Alchemy](https://www.alchemy.com/) to access them.
Standard Ethereum debug methods are available on the public MegaETH RPC endpoint (`https://mainnet.megaeth.com/rpc`) and through managed RPC providers such as [Alchemy](https://www.alchemy.com/).
Debug methods share the `compute` rate limit tier (200 requests per 10 seconds).
Comment thread
claude[bot] marked this conversation as resolved.
Outdated

The following methods are available through managed providers:
The following methods are supported:

- **`debug_traceTransaction`** — trace an already-mined transaction by hash
- **`debug_traceCall`** — simulate and trace a call without broadcasting
Expand All @@ -28,7 +28,6 @@ The following methods are available through managed providers:
| callTracer | `"callTracer"` | Nested call tree with inputs, outputs, and gas usage per call |
| prestateTracer | `"prestateTracer"` | Account state before execution; set `"diffMode": true` for before/after diff |
| flatCallTracer | `"flatCallTracer"` | Parity-style flat list of all calls |
| 4byteTracer | `"4byteTracer"` | Counts function selector usage |

{% hint style="info" %}
JavaScript tracers are not supported.
Expand All @@ -41,7 +40,7 @@ For method parameters, tracer configuration options, and response formats, see t
[`mega-evme`](https://docs.megaeth.com/mega-evme) is a local CLI tool that uses the open-source [MegaEVM](https://github.com/megaeth-labs/mega-evm) implementation.
It can perfectly simulate any transaction's behavior on MegaETH, including storage gas, compute gas caps, and resource limits.

Use `mega-evme` when you want full local control over tracing, or when you don't have access to a managed RPC endpoint with debug methods.
Use `mega-evme` when you want full local control over tracing, deterministic replay, or what-if analysis with transaction overrides.

### Installation

Expand Down
Loading