-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
feat: add rns registry contract address #3730
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add rns registry contract address #3730
Conversation
Someone is attempting to deploy a commit to the Wevm Team on Vercel.
A member of the Team first needs to authorize it.
🦋 Changeset detectedLatest commit: d071742 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
2b07bcf to
9efc073
Compare
Thanks for the PR. Is this address listed on the official docs anywhere?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to also add ensTld to this chain.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added
Thanks for the PR. Is this address listed on the official docs anywhere?
Yes, you can check in the official rns-registry package: https://www.npmjs.com/package/@rsksmart/rns-registry
Deployments:
RSK Mainnet: [0xcb868aeabd31e2b66f74e9a55cf064abb31a4ad5](https://explorer.rsk.co/address/0xcb868aeabd31e2b66f74e9a55cf064abb31a4ad5)
RSK Testnet: [0x7d284aaac6e925aad802a53c0c69efe3764597b8](https://explorer.testnet.rsk.co/address/0x7d284aaac6e925aad802a53c0c69efe3764597b8)
9efc073 to
d071742
Compare
@jxom! Did you have the chance to review the PR?
Not yet.
Why is the repository archived? https://github.com/rnsdomains/rns-registry
Why is the repository archived? https://github.com/rnsdomains/rns-registry
The repository is archived because it is now in read-only mode—the protocol itself is fully deployed and actively used on the Rootstock blockchain. RNS protocol continues to be a foundational component of the Rootstock ecosystem.
📌 Where is RNS actively used?
Here are several examples that demonstrate the ongoing relevance and integration of the RNS protocol:
-
📘 Devportal Documentation
Extensive technical documentation on RNS is available here:
https://dev.rootstock.io/concepts/rif-suite/rns/ -
📦 RNS SDK
Thersksmart/rns-sdkis widely used by dApps for domain resolution, registration, and management. -
🔍 Blockchain Explorers
- Rootstock Explorer: https://explorer.rootstock.io/
- Blockscout: View active
.rskname domains
https://rootstock.blockscout.com/name-domains?only_active=true
-
📊 RNS Subgraph on The Graph
RNS data is also indexed for querying via The Graph protocol:
https://thegraph.com/explorer/subgraphs/DhBgWdhFsujyqFmYqaTwUyyYm5QWBEhqVnBHek9JYPkn?view=About&chain=arbitrum-one -
💼 Wallet Integrations
RNS is supported by a number of wallets that enable human-readable addresses:
Hi @jxom! Did you have the chance to review? Do you need more information?
129b947 to
9ad3509
Compare
d78cf00 to
b31cf2a
Compare
PR Description
This PR adds the RNS Registry contract address for Rootstock Mainnet.
By including this address, Rootstock becomes compatible with ENS-related operations offered by the wagmi library. Since RNS is protocol-compatible with ENS, developers will now be able to use standard ENS methods (e.g.,
getEnsAddress,resolveName, etc.) when interacting with.rskdomains on Rootstock.This is an important step toward improving interoperability and enhancing the developer experience across the Rootstock ecosystem.