✳flâneur — a map of the web's best reading

Contract ABI Specification — Solidity 0.8.21 documentation

docs.soliditylang.org · 5,279 words · saved by 1 readers

The Contract Application Binary Interface (ABI) is the standard way to interact with contracts in the Ethereum ecosystem, both from outside the blockchain and for contract-to-contract interaction. Data is encoded according to its type, as described in this specification. The encoding is not self describing and thus requires a schema in order to decode. We assume that the interface functions of a contract are strongly typed, known at compilation time and static. We assume that all contracts will have the interface definitions of any contracts they call available at compile-time. This specification does not address contracts whose interface is dynamic or otherwise known only at run-time. The first four bytes of the call data for a function call specifies the function to be called. It is the first (left, high-order in big-endian) four bytes of the Keccak-256 hash of the signature of the function. The signature is defined as the canonical expression of the basic prototype without data loca

Contract ABI Specification - Solidity 0.8.21 documentation --> Contract ABI Specification Edit on GitHub Contract ABI Specification  Basic Design  The Contract Application Binary Interface (ABI) is the standard way to interact with contracts in the Ethereum ecosystem, both from outside the blockchain and for contract-to-contract interaction. Data is encoded according to its type, as described in this specification. The encoding is not self describing and thus requires a schema in order to decode. We assume that the interface functions of a contract are strongly typed, known at compilation ti

Explore this link on the map →

related reading