Update documentation on name resolution matchers

MetaMask · Sep 9, 2024 · 67d5a05 · 67d5a05
1 parent 8b45b73
commit 67d5a05
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 3 deletions.
diff --git a/snaps/features/custom-name-resolution.md b/snaps/features/custom-name-resolution.md
@@ -23,6 +23,18 @@ For example, to resolve Ethereum Mainnet domains, add the following to your Snap
 }
 ```
 
+If you're only targetting specific TLDs or schemes, you can use the `matchers` property to reduce
+overhead by specifying the TLDs and schemes you support. For example:
+
+```json title="snap.manifest.json"
+"initialPermissions": {
+  "endowment:name-lookup": {
+    "chains": ["eip155:1"],
+    "matchers": { "tlds": ["crypto"] }
+  }
+}
+```
+
 ### 2. Implement custom name resolution
 
 Expose an [`onNameLookup`](../reference/entry-points.md#onnamelookup) entry point, which receives a

diff --git a/snaps/reference/permissions.md b/snaps/reference/permissions.md
@@ -153,9 +153,6 @@ Specify this permission in the manifest file as follows:
 
 ### `endowment:name-lookup`
 
-:::flaskOnly
-:::
-
 To provide [custom name resolution](../features/custom-name-resolution.md), a Snap must request the
 `endowment:name-lookup` permission.
 This permission grants the Snap read-only access to user input or an address by exporting the