feat: FIP-256 – support additional name resolvers #732
Conversation
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
|
@CassOnMars is attempting to deploy a commit to the farcaster Team on Vercel. A member of the Team first needs to authorize it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
From discussion in farcasterxyz/protocol#256
This PR adds two new name resolvers: Solana Name Service, and Quilibrium Name Service
Purpose
Presently, the snapchain protocol is built to be relatively chain-agnostic, except ingestion of on chain events where relevant (fids/contract wallet signatures/signers). As part of this, there is support for wallet verification for eth and solana addresses already in the protocol. However, we presently do not support name resolvers outside of the ethereum ecosystem. This PR intends to resolve this by supporting two new name resolvers: