Repository navigation
Add Namebase - #1541
Merged
Merged
Add Namebase#1541
Conversation
This closes #1540
FrederikBolding
approved these changes
Sep 21, 2026
Mrtenz
approved these changes
Sep 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This closes #1540
Note
Low Risk
Registry-only change adding catalog metadata and a pinned package checksum; no runtime or auth logic in this repo.
Overview
Adds Namebase (
npm:@namebase.io/metamaskv0.1.1) to the snaps registry so it can be discovered and installed from MetaMask.The listing describes a name resolution snap that resolves Handshake/Namebase domains in the send field via on-chain registry reads (not ENS), with metadata, support links, source repo, screenshot paths, and a version checksum.
Reviewed by Cursor Bugbot for commit f363a0a. Bugbot is set up for automated code reviews on this repo. Configure here.