From 6307a1265178007e956aa5f9980acd554f4c9efd Mon Sep 17 00:00:00 2001 From: Yoichi Hirai Date: Wed, 12 Jul 2017 14:37:12 +0200 Subject: Borrow a sentence from @axic and edit the phrase "following its type", which sounded like the data follows the type in the call data. --- docs/abi-spec.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs') diff --git a/docs/abi-spec.rst b/docs/abi-spec.rst index 5d987e7f..d915973d 100644 --- a/docs/abi-spec.rst +++ b/docs/abi-spec.rst @@ -10,8 +10,8 @@ Basic Design ============ The Application Binary Interface 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 following its type, -according to this specification. The types are not encoded. +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 the interface functions of a contract are strongly typed, known at compilation time and static. No introspection mechanism will be provided. We assume that all contracts will have the interface definitions of any contracts they call available at compile-time. -- cgit v1.2.3