Decoding Ethereum Transaction Data Without Contract ABIs
Summary
Ethereum transaction inputs and event logs store values in compact encoded forms. Applications commonly rely on a contract’s ABI to map that data to function names, argument types, and readable values. Maintaining ABI files becomes difficult when an application needs to work across many unrelated contracts.
The document explains an indexing approach that uses public contract ABIs, four-byte function signatures, and ERC specifications to infer and return parsed transaction data alongside raw data. Examples show how a Uniswap swap and a CryptoKitties birth event can be represented with named arguments rather than opaque hexadecimal strings. It also describes using the decoded function signature and parameters to support transaction construction or RPC calls, and lists transaction and log endpoint categories where parsing is available. These examples illustrate the format and workflow, but they are not an independent accuracy evaluation. Signature collisions, unknown contracts, incomplete ABI coverage, and provider-specific decoding behavior are not discussed, so the claimed breadth should not be treated as guaranteed for every transaction.
Key ideas
- Ethereum transaction data is encoded and often needs an ABI to interpret function calls and event arguments.
- An index of public ABIs and function signatures can be used to decode data for many contracts.
- Parsed fields can make swap and NFT event records easier for applications to consume.
- Decoded signatures and parameters may also help construct transactions or RPC calls.
- The examples demonstrate a data format, but do not independently measure decoding coverage or accuracy.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.