New Hns.id (#941)

Closes: #942

src/registry.json

@@ -1155,6 +1155,29 @@
         }
       }
     },
+    "npm:hns-id": {
+      "id": "npm:hns-id",
+      "metadata": {
+        "name": "HNS ID Name Resolution",
+        "author": {
+          "name": "namebase",
+          "website": "https://www.namebase.io/"
+        },
+        "website": "https://hns.id/",
+        "summary": "Resolve hns.id domains natively on multiple EVM blockchains.",
+        "description": "The MetaMask Snap for HNS.ID enhances the MetaMask wallet by enabling domain resolution for HNS.ID domains and improving ENS resolution on EVM-compatible chains. This Snap provides users with broader support for hns.id domains and expanded functionality for interactions across different networks.\n\n\nKey Features:\n\n- Multi-Chain Support: Resolves HNS.ID domains across various EVM chains, ensuring seamless domain interactions within MetaMask.\n\n- ENS Enhancement: Preserves and improves ENS resolution functionality by enabling CCIP-linked ENS domain resolution on networks beyond Ethereum mainnet.\n\n- Effortless Integration: Installs directly within MetaMask, adding domain resolution capabilities without interfering with existing ENS lookups.\n\n- Secure Permissions: Requires internet access for domain resolution and permissions for domain/address look-ups.\n\n\nVisit: https://hns.id for more information about the platform and how to get started.\n\n\nThis Snap helps bridge the gap for users needing enhanced domain resolution capabilities, offering a streamlined experience without disrupting standard MetaMask operations.",
+        "support": {
+          "contact": "mailto:[email protected]",
+          "faq": "https://docs.hns.id/resolving-domains/metamask-snap"
+        },
+        "sourceCode": "https://github.com/namebasehq/hns-id-mm-snap"
+      },
+      "versions": {
+        "0.1.16": {
+          "checksum": "mXQW3g18buic9nB20A9PYjYH94XkKQpYwckVXvKEKEg="
+        }
+      }
+    },
     "npm:btcsnap": {
       "id": "npm:btcsnap",
       "metadata": {