From 4f84112650cab6701bcfa7e6c86e43069615819c Mon Sep 17 00:00:00 2001 From: Lokesh Kumar Date: Wed, 1 Feb 2023 03:12:03 +0530 Subject: [PATCH] updated abi-spec.rst --- docs/abi-spec.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/abi-spec.rst b/docs/abi-spec.rst index 7906d75ff..35123a30a 100644 --- a/docs/abi-spec.rst +++ b/docs/abi-spec.rst @@ -311,7 +311,7 @@ Use of Dynamic Types A call to a function with the signature ``f(uint256,uint32[],bytes10,bytes)`` with values ``(0x123, [0x456, 0x789], "1234567890", "Hello, world!")`` is encoded in the following way: -We take the first four bytes of ``sha3("f(uint256,uint32[],bytes10,bytes)")``, i.e. ``0x8be65246``. +We take the first four bytes of ``keccak("f(uint256,uint32[],bytes10,bytes)")``, i.e. ``0x8be65246``. Then we encode the head parts of all four arguments. For the static types ``uint256`` and ``bytes10``, these are directly the values we want to pass, whereas for the dynamic types ``uint32[]`` and ``bytes``, we use the offset in bytes to the start of their data area, measured from the start of the value