Package Exports
- @rsksmart/rns-reverse/NameResolverData.json
- @rsksmart/rns-reverse/ReverseRegistrarData.json
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@rsksmart/rns-reverse) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
RNS Reverse Resolution implementation
- Name resolver: 0x4b1a11bf6723e60b9d2e02aa3ece34e24bde77d9
- Reverse registrar: 0xd25c3f94a743b93ecffecbe691beea51c3c2d9d1
Read the docs here
Summary
RIF implementation of EIP-181 in RSK network.
Abstract
EIP-181 specifies a TLD, registrar, and resolver interface for reverse resolution of Ethereum addresses using ENS. RIF applies to this specification and proposes a different implementation, based on the technical differences on the protocol.
EIP181 compatibillity
RNS Reverse registrar and resolver are fully compatible with the EIP-181 specification.
Default resolver
In RNS, default resolver is the node's resolver. When setSubnodeOwner is triggered the subnode created inherits the node's resolver.
claimWithResolver result
If the resolver address specified is 0x00, leaves default resolver.