Along the RNS registry and initial registrar there is a public resolver deployed as well (see the RSKResolver contract). This contract is available for anybody to use it, but the only restriction is that only owners of a domain can modify its record in this resolver. This resolver implements all the methods described in the Resolver specification
Additionally, it is used as the default resolver configured for new nodes created in the registry.
There is an upgraded version of this resolver. See Multi-crypto resolver page.
To migrate your resolver, execute the setResolver command on the registry.
0x4efd25e3d348f8f25a14fb7655fba6f72edfe93a
See RNS Testnet section for testing environment information.
Context
AbstractRNS rns;
rns
: the Registry contractStorage
mapping(bytes32=>address) addresses;
mapping(bytes32=>bytes32) hashes;
adresses
: for each namehash
entry, stores an addresshashes
: for each namehash
entry, stores a hashReturns true if the specified node has the specified record type.
Signature
function has(bytes32 node, bytes32 kind) public view returns (bool)
Parameters
node
: the RNS node to query.kind
: the record type name, as specified in EIP137.Returns
bool
: true if this resolver has a record of the provided type on the provided node.
Returns the content hash associated with an RNS node. Note that this resource type is not standardized, and will likely change in future to a resource type based on multihash.
Signature
function content(bytes32 node) public view returns (bytes32)
Parameters
node
: the RNS node to query.
Returns
bytes32
: the associated content hash.Sets the content hash associated with an RNS node. May only be called by the owner of that node in the RNS registry. Note that this resource type is not standardized, and will likely change in future to a resource type based on multihash.
Signature
function setContent(bytes32 node, bytes32 hash) public only_owner(node)
Parameters
node
: the node to update.hash
: the content hash to setGo to top