Skip to content

Conversation

jonathansmirnoff
Copy link
Contributor

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 .rsk domains on Rootstock.

This is an important step toward improving interoperability and enhancing the developer experience across the Rootstock ecosystem.

Copy link

vercel bot commented Jun 12, 2025

Someone is attempting to deploy a commit to the Wevm Team on Vercel.

A member of the Team first needs to authorize it.

Copy link

changeset-bot bot commented Jun 12, 2025

🦋 Changeset detected

Latest commit: d071742

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
viem Patch

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

@jonathansmirnoff jonathansmirnoff force-pushed the feat/add-rootstock-rns-contract branch 2 times, most recently from 2b07bcf to 9efc073 Compare June 12, 2025 21:41
@jxom
Copy link
Member

jxom commented Jun 13, 2025

Thanks for the PR. Is this address listed on the official docs anywhere?

url: 'https://explorer.rsk.co',
},
},
contracts: {
Copy link
Member

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.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added

@jonathansmirnoff
Copy link
Contributor Author

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)

@jonathansmirnoff jonathansmirnoff force-pushed the feat/add-rootstock-rns-contract branch from 9efc073 to d071742 Compare June 13, 2025 12:31
@jonathansmirnoff
Copy link
Contributor Author

@jxom! Did you have the chance to review the PR?

@jxom
Copy link
Member

jxom commented Jun 17, 2025

Not yet.

@jxom
Copy link
Member

jxom commented Jul 18, 2025

Why is the repository archived? https://github.com/rnsdomains/rns-registry

@jonathansmirnoff
Copy link
Contributor Author

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:

@jonathansmirnoff
Copy link
Contributor Author

Hi @jxom! Did you have the chance to review? Do you need more information?

@tmm tmm force-pushed the main branch 3 times, most recently from 129b947 to 9ad3509 Compare September 19, 2025 19:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants