MetaMask Snaps Directory Information - Update
This form collects the Snap details from the builders for updating the directory listing. You can visit Snaps Directory to see how this information is used. For details on the FAQs/Knowledge Base information requested, please see this document. Please only complete the fields where you are making an update. If you are not updating a field, leave it blank (unless it is a required field) .
Sign in to Google to save your progress. Learn more
Email *
Snap Name (This is the `proposedName` from the snap.manifest.json file. It should not contain the words "snap" or "MetaMask." This is the name displayed in the Snap Directory).  *
Snap Builder - Name (This is your Brand Name) *
Snap Builder - URL (This is the main Website of your Company)
Snap Website - URL (This is the Companion dapp or Landing page for your Snap. Users will go here to interact with your Snap and learn more about it.)
Please provide the description of the update describing the reason and details of the new version, including what has changed in the code.   *
Please provide a Github comparison link of your current allowListed version and the new version. eg: https://github.com/<name>/<repo>/compare/repo-v1.0.1...repo-v1.0.2

Please make sure that functional changes are separate from chore updates (like linting, dependency updates, and documentation) and provide a clean diff so we can review the relevant code changes. Doing so will help us allowlist your update faster! *
Snap Short Description (Brief description of the Snap, 1 or 2 sentences long.)
Snap Long Description (A Longer description of the Snap features and how to use them. You can use '\n' line breaks here.)
Please provide the URL to your public GitHub repo for the Snap code.
Please provide the URL to your npm package. 
Please provide the updated Snap Version number that is to be allowlisted. (It should be the same as published in the Snap's `package.json` and `snap.manifest.json` files.). *
Please mention the version number(s) that is to be unlisted, separated by comma. (This version will be removed from the allowlist and replaced by the new version. If you do not want to unlist current/older versions please enter N/A here)
 *
When building your Snap, did you verify that there were no errors in the CLI? The Snaps CLI runs a manifest validator to check for errors. If your Snap manifest has errors, it will likely not work in MetaMask. *
Required
Who is your Snap auditor? (Please select any auditor from this list, or if an audit is not required, enter N/A)
Snap audit report (A URL to where the audit report has been published. The audit report will eventually be made public. If an audit is not required, enter N/A.)
Provide a General support contact. (This can be an Email AND/OR Discord Channel AND/OR link to support ticketing page. For details, see the above document. In case of Discord, it should be a permanent link.)
Provide an escalation contact email. (This is different from the General support contact above.)
Provide a link to General FAQ document. (This should be a Snap-specific FAQ document and not generic FAQ.)
Provide a link to Knowledge Base document. (This should be a Snap-specific Knowledge Base document and not generic.)
Provide a link to the snap demo video (<2 minutes).
Which country is your team/project based in?
Submit
Clear form
Never submit passwords through Google Forms.
reCAPTCHA
PrivacyTerms
This form was created inside of Consensys.

Does this form look suspicious? Report

Google Forms