As of the time of writing, the following trace request fails against Alchemy endpoints:
$ heimdall inspect -r https://eth-mainnet.g.alchemy.com/v2/[REDACTED] 0x3769def16506268d93c59371b7a2df13d87014027b8f3653f48c74798ec5d6f8
2024-06-13T00:45:38.783933Z ERROR failed to replay and trace transaction '0x3769def16506268d93c59371b7a2df13d87014027b8f3653f48c74798ec5d6f8' . does your RPC provider support it?
2024-06-13T00:45:38.783969Z ERROR error: '(code: -32602, message: invalid 2nd argument: tracers had invalid element: "vmTrace" - only "stateDiff" and "trace" tracers are supported., data: None)' .
2024-06-13T00:45:40.063780Z ERROR failed to replay and trace transaction '0x3769def16506268d93c59371b7a2df13d87014027b8f3653f48c74798ec5d6f8' . does your RPC provider support it?
2024-06-13T00:45:40.063818Z ERROR error: '(code: -32602, message: invalid 2nd argument: tracers had invalid element: "vmTrace" - only "stateDiff" and "trace" tracers are supported., data: None)' .
2024-06-13T00:45:41.600079Z ERROR failed to replay and trace transaction '0x3769def16506268d93c59371b7a2df13d87014027b8f3653f48c74798ec5d6f8' . does your RPC provider support it?
2024-06-13T00:45:41.600105Z ERROR error: '(code: -32602, message: invalid 2nd argument: tracers had invalid element: "vmTrace" - only "stateDiff" and "trace" tracers are supported., data: None)' .
2024-06-13T00:45:43.334870Z ERROR failed to replay and trace transaction '0x3769def16506268d93c59371b7a2df13d87014027b8f3653f48c74798ec5d6f8' . does your RPC provider support it?
2024-06-13T00:45:43.334894Z ERROR error: '(code: -32602, message: invalid 2nd argument: tracers had invalid element: "vmTrace" - only "stateDiff" and "trace" tracers are supported., data: None)' .
2024-06-13T00:45:47.803330Z ERROR failed to replay and trace transaction '0x3769def16506268d93c59371b7a2df13d87014027b8f3653f48c74798ec5d6f8' . does your RPC provider support it?
2024-06-13T00:45:47.803371Z ERROR error: '(code: -32602, message: invalid 2nd argument: tracers had invalid element: "vmTrace" - only "stateDiff" and "trace" tracers are supported., data: None)' .
Error: Generic("failed to inspect transaction: Internal error: fetching block trace failed: Error: failed to get trace for transaction: \"0x3769def16506268d93c59371b7a2df13d87014027b8f3653f48c74798ec5d6f8\"")
This is certainly not a Heimdall bug as this works against my local Reth node (with --http.api trace, obviously).
This raises the question of how individual tracers should be handled in the support matrix.
As of the time of writing, the following trace request fails against Alchemy endpoints:
This is certainly not a Heimdall bug as this works against my local Reth node (with
--http.api trace, obviously).This raises the question of how individual tracers should be handled in the support matrix.