ABI Encoder/Decoder Tools
Converting between human-readable contract calls and the binary format the EVM expects.
No connection. Decentralized.Host has no smart-contract interaction. Its wire format is canonical JSON (integers only, duplicate keys and invalid UTF-8 rejected).
What ABI encoding actually is
The EVM only understands raw bytes -- calling a function like transfer(address,uint256) on-chain requires encoding the function selector (a 4-byte hash of the function signature) plus the arguments into a specific binary layout the ABI (Application Binary Interface) specification defines. Tools like ethers.js/viem's encodeFunctionData, or standalone decoders, translate between this binary format and human-readable calls -- essential for debugging a raw transaction's calldata, or for any tool that needs to construct a contract call without a full SDK.
Converting between human-readable contract calls and the binary format the EVM expects. No connection. Decentralized.Host has no smart-contract interaction. Its wire format is canonical JSON (integers only, duplicate keys and invalid UTF-8 rejected).