From 09d39ce44d793d641d41ffa16a40288efeb2008c Mon Sep 17 00:00:00 2001 From: Jordi Baylina Date: Sat, 5 May 2018 04:50:30 -0400 Subject: [PATCH] Automatically merged updates to draft EIP(s) 820 Hi, I'm a bot! This change was automatically merged because: - It only modifies existing draft EIP(s) - The PR was approved or written by at least one author of each modified EIP - The build is passing --- EIPS/eip-820.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/EIPS/eip-820.md b/EIPS/eip-820.md index c3987645..047822dc 100644 --- a/EIPS/eip-820.md +++ b/EIPS/eip-820.md @@ -241,13 +241,13 @@ Your interface name is hashed and sent to `getInterfaceImplementer()`. If you ar #### If it's an approved EIP -The interface is named like `ERC###XXXXX`. The meaning of this interface is defined in the EIP specified. And XXX should be the name of the interface camelCase. +The interface is named like `ERC###XXXXX`. The meaning of this interface is defined in the EIP specified. And XXXXX should be the name of the interface camelCase. Examples: `sha3("ERC20Token")` `sha3("ERC777Token")` -`sha3("ERC777TokensReceiver")` +`sha3("ERC777TokensRecipient")` `sha3("ERC777TokensSender")` #### [EIP-165](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-165.md) compatible interfaces