Snaps can now provide name resolution for additional protocols beyond what @metamask supports natively!

More than a handful of Snaps were added to the directory. Check them out here:

Snaps can now provide name resolution for additional protocols beyond what @metamask supports natively!

More than a handful of Snaps were added to the directory. Check them out here: https://snaps.metamask.io/name-resolution/

BSc in Computer Science & Software Engineer @metamask Snaps

Note that the latest version of the MetaMask extension is required and that we have discovered one snag that is preventing lookup of non-TLD IDs e.g. Farcaster IDs (to be fixed soon)

supporting names without TLDs seems problematic for collisions - what if i have two snaps installed, one for lens and one for farcaster and somebody else has the “greg” username on lens?

I like baking /goodbread and building apps on web3 protocols. DevRel @ ENS Labs. gregskril.com

ah i didn’t think about different schemas, that makes sense. appreciate the response

that's not what he is talking about. he's talking about other namespaces like Clusters, FIO handles, or schemes like "farcaster:name." 

But even in that scenario, each resolver is required to return a protocol name and the exact match, so you never just see multiple "greg"s with different addresses.