Invalid tx result
Code
RPC/BASE/INVALID_TX_RESULT
What it means
The tx result shape is not what the client expects, so the client cannot safely determine success/failure or parse the response payload.
When it happens
- A transaction response is missing fields required for parsing (e.g.
ResponseBase).
Typical scenarios:
- Node returns a partial response due to internal failure
- Upstream API changed or a proxy modified the payload
- Client is out of sync with the node version/format
How to handle
- Treat as an internal RPC failure.
- Log
meta.paramsandmeta.txHashto reproduce.
Suggested follow-ups:
- Capture the raw response in
meta.result(or a trimmed version) when safe. - If reproducible, compare node responses across environments.
Last updated on