Here you can find notes, tutorials, and devops snippets relevant to 1NS, which is initially based on ENS. The resources are targeted for the Harmony Team and ecosystem developers, devided into the following sections

• Consolidate Codebase and Production Support
• At some point we should review the latest version of @ensdomains/ens-contracts, and update our dependency to a forked repository
  • Our implementation ens-deployer is written based on v0.0.15, which appears to exist only as an npm dependency, but not explicitly tagged on Github.
  • As of March 1, 2023, the latest version of @ensdomains/ens-contracts is ^0.0.20 commit
  • Update blockchain DNS (CoreDNS 1NS) implementations accordingly, if necessary
• Sending emails via EAS over SMTP https://github.com/harmony-one/eas
  • EAS smart contracts may require some improvements, see EAS.sol
• Self Hosted Mail Server
• Test coverage for DC.sol and Tweet.sol.
  • Develop registration tests for tweet.sol similar to DNS-001
  • Develop url update tests for tweet.sol (only have sample initialization now)
  • Note: here are the steps to follow for testing:
    1. Setup ens-deployer : service-testing
    2. Review register function in ensSampleDCDNS.ts
    3. Review functions in DC.sol
    4. Review functions in Tweet.sol
    5. Check config.ts and .env have the correct addresses for local ganache instance
    6. Test against local ganache yarn test —network local
• We may want to add DNS update functionalities in go-1ns module (as part of a CoreDNS 1NS plugin) https://github.com/harmony-one/go-1ns, if we want a centralized authority to be able to update DNS records for users' domains (such as to satisfy DNS challenges in generating SSL certificates). Additionally, we need to improve test coverage for this module