From 74e2c2e3d70d16ed2a1daf0c1b95d706d931b1e2 Mon Sep 17 00:00:00 2001 From: Nick Johnson Date: Mon, 6 Feb 2017 15:56:01 +0000 Subject: [PATCH] Rename abi to abiSpec to avoid name clashes --- EIPS/eip-ens-abi-lookup.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/EIPS/eip-ens-abi-lookup.md b/EIPS/eip-ens-abi-lookup.md index b3062d63c17d19..e5554a11d7130a 100644 --- a/EIPS/eip-ens-abi-lookup.md +++ b/EIPS/eip-ens-abi-lookup.md @@ -46,9 +46,9 @@ Encoding type 8 indicates that the ABI can be found elsewhere, at the specified ### Resolver profile A new resolver interface is defined, consisting of the following method: - function abi(bytes32 node, uint256 contentType) constant returns (uint256, bytes); + function abiSpec(bytes32 node, uint256 contentType) constant returns (uint256, bytes); -The interface ID of this interface is 0x83ee6bd2. +The interface ID of this interface is 0xe2acca58. contentType is a bitfield, and is the bitwise OR of all the encoding types the caller will accept. Resolvers that implement this interface must return an ABI encoded using one of the requested formats, or `(0, "")` if they do not have an ABI for this function, or do not support any of the requested formats.