From 6d719f230f7dddb91175c70b1592ee81e452a82b Mon Sep 17 00:00:00 2001 From: William Entriken Date: Tue, 13 Feb 2018 03:07:48 -0500 Subject: [PATCH] Discuss optional interfaces per @dete advice References: https://github.com/ethereum/EIPs/issues/165#issuecomment-345382512 --- EIPS/eip-165.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/EIPS/eip-165.md b/EIPS/eip-165.md index 250764e..18b7c91 100644 --- a/EIPS/eip-165.md +++ b/EIPS/eip-165.md @@ -51,7 +51,9 @@ contract Selector { } ``` -Note: interfaces do not permit optional functions, therefore, the interface identity will not them. +Note: interfaces do not permit optional functions, therefore, the interface identity will not include them. + +Note: an ERC standard may define multiple interfaces to separate core functionality from optional features. For example, [one draft standard defines](https://github.com/ethereum/EIPs/pull/841) ERC721, ERC721Metadata and ERC721Enumerable interfaces. ### How a Contract will Publish the Interfaces it Implements