RNS integration in Unstoppable Domains resolver

[bguiz]

RNS integration in Unstoppable Domains resolver

Prize Bounty

0.00960 RBTC

(approximately 600 USD at time of posting)

Challenge Description

Unstoppable Domains resolver is a tool that is used to resolve domains in different blockchains. An integration with this tool would imply a PR. Some required changes are already identified:

• Is supported domain method https://github.com/unstoppabledomains/resolution/blob/master/src/Ens.ts#L30
• Network-specific instance creation https://github.com/unstoppabledomains/resolution/blob/master/src/Resolution.ts#L81 It seems that those are the only two changes required, but there is also an implicit need to audit that the whole ENS implementation is still fully compatible with RNS.

  Submission Requirements

The submission is expected to:

• A Github pull request on the Unstoppable Domains Resolution repository
• Not require any modifications to the RNS Manager or other RNS repositories
• Perform the tasks detailed in "Challenge Description"
• Use the same software licence as the Unstoppable Domains Resolution repository (MIT)

Note that if you assess that modifications to the RNS Manager or other RNS repositories are needed, please get in touch with us to discuss beforehand.

Judging Criteria

• Only one submission allowed per participant. Where a participant wishes to resubmit, update the original submission instead of submitting a separate entry.
• If the submission involves a graphical user interface of any variety, please include a video recording of it in action.
• If the submission involves a command line interface of any variety, please include a text file of it in action (including outputs).
• Test coverage for any implementation is viewed favourably: More test coverage is better.
• In cases where the bounty requires a Github PR on an existing repo, and that repo has continuous integration (CI) set up, the PR should not fail on the CI steps.
• Documentation is viewed favourably: Include specific instructions on how to set up and use your submission. Optionally, include any explanations of architectural/ design choices that went into the submission.
• The easier it is for the reviewer to run and understand the submission, the better, so be sure to consider this in your submissions!

Winner Announcement Date

• This bounty is part of a hackathon, and there are three significant dates:
  • Start date: 15/04/2021
  • End date: 14/05/2021
  • Results date: 15/06/2021
• Submissions are welcome between the start date and the end date.
• Reviews will be conducted between the end date and the results date.
• All submissions must be submitted prior to the end date in order to be eligible for a bounty award.
• Submissions submitted or resubmitted after the end date may not be awarded any bounty.
• All submissions must be reviewed and accepted (successfully pass the review) prior to the results date in order to be eligible for a bounty award.
• The bounty will be awarded on the Gitcoin platform to the best submission among all eligible submissions for this bounty.

More information

• For questions related to this bounty, and other bounties in this hackathon, please join the RSK Slack, and check out the #gitcoin2021 channel.
• To learn more about RSK and RIF technologies, check out our Developer Portal.

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

This issue now has a funding of 0.0096 RBTC (596.12 USD @ $62096.0/RBTC) attached to it.

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
  • Want to chip in? Add your own contribution here.
  • Questions? Checkout Gitcoin Help or the Gitcoin's Discord
  • $2,124,311.31 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

Work for 0.0096 RBTC (545.10 USD @ $57145.0/RBTC) has been submitted by:

---

• Learn more on the Gitcoin Issue Details page
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin's Discord
• $2,152,003.16 more funded OSS Work available on the Gitcoin Issue Explorer

[ilanolkies]

Hi @vinhbhn thanks for the submission!!

I have some feedback for your PR:

1. If the branch has conflicts, it is most probable it does not get fixed by the owners of the repo. To get it merged you will need to rebase master.
2. I would avoid copy-pasting ENS implementation, since the resolution protocol is practically the same. Try modifying the existing ENS code to
   1. Make it accept a different RPC URL and Registry address
   2. Returns the correct RSK checksum
   3. Uses .rsk as the only available top level domain