ERC-137 Ethereum Domain Name Service - Specification
Functions this standard introduces (15)
0x3b3b57de | addr(bytes32) | |
0x19a17468 | ENS(address) | |
0x9d063ed8 | FIFSRegistrar(address,bytes32) | |
0x02571be3 | owner(bytes32) | |
0xebb045fa | PublicResolver(address) | |
0xd22057a9 | register(bytes32,address) | |
0x659755f9 | Resolver() | |
0x0178b8bf | resolver(bytes32) | |
0xd5fa2b00 | setAddr(bytes32,address) | |
0x5b0fc9c3 | setOwner(bytes32,address) | |
0x1896f70a | setResolver(bytes32,address) | |
0x06ab5923 | setSubnodeOwner(bytes32,bytes32,address) | |
0x14ab9038 | setTTL(bytes32,uint64) | |
0x01ffc9a7 | supportsInterface(bytes4) | |
0x16a25cbd | ttl(bytes32) |
Events (5)
Topic0 is the keccak256 hash of the signature, which is what a log filter matches on.
0xce0457fe73731f824cc272376169235128c118b49d344817417c6d108d155e82 | NewOwner(bytes32,bytes32,address) | |
0xd4735d920b0f87494915f556dd9b54c8f309026070caea5c737245152564d266 | Transfer(bytes32,address) | |
0x335721b01866dc23fbee8b6b2c7b1e14d6f05c28cd35a2c934239f94095602a0 | NewResolver(bytes32,address) | |
0x52d7d861f09ab3d26239d492e8968629f95e9e318cf0b73bfddc441522a15fd2 | AddrChanged(bytes32,address) | |
0x0424b6fe0d9c3bdbece0e7879dc241bb0c22e900be8b6c168b4ee08bd9bf83bc | ContentChanged(bytes32,bytes32) |
Built on by (19)
Later proposals that name this one in their requires field.
What the specification covers
Compare with
Parsed from the canonical specification