status-im
/
EIPs
mirror of https://github.com/status-im/EIPs.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #631 from Arachnid/master 

EIP 137: Add warning for implementers against treating 0 like other addresses
This commit is contained in:
Nick Johnson 2017-05-15 17:16:21 +01:00 committed by GitHub
parent e601a6d8d1 9d69f58d0f
commit 384ca913cf
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
EIPS/eip-137.md
View File

@ -179,6 +179,7 @@ The following interfaces are defined:
| `pubkey` | 0xc8690233 | #619 | | `pubkey` | 0xc8690233 | #619 |
EIPs may define new interfaces to be added to this registry. EIPs may define new interfaces to be added to this registry.
### <a name="addr"></a>Contract Address Interface ### <a name="addr"></a>Contract Address Interface
Resolvers wishing to support contract address resources must provide the following function: Resolvers wishing to support contract address resources must provide the following function:
@ -189,6 +190,8 @@ function addr(bytes32 node) constant returns (address);
If the resolver supports `addr` lookups but the requested node does not have a record, the resolver MUST return the zero address. If the resolver supports `addr` lookups but the requested node does not have a record, the resolver MUST return the zero address.
Clients resolving the `addr` record MUST check for a zero return value, and treat this in the same manner as a name that does not have a resolver specified - that is, refuse to send funds to or interact with the address. Failure to do this can result in users accidentally sending funds to the 0 address.
Changes to an address MUST trigger the following event: Changes to an address MUST trigger the following event:
``` ```