pin signed SIWE message in coinbase claim route#28
Open
patnir wants to merge 1 commit into
Open
Conversation
- verify the signature matches the wallet named in the message (handles smart wallets via viem) - pin the action to the one this airdrop gates on, so users cant swap it to mint a second token - shows what a third-party integrator should do instead of trusting the token blindly
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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
Demonstrates the third-party integrator pin on the offchain /coinbase claim flow. Before trusting the Base Verify token, the app now confirms the user signed exactly what we asked for: the right action and a signature that really comes from the wallet in the message. Trait pinning already existed; this adds action pinning and signature-to-wallet binding.
Test plan
type=routine
risk=low
impact=sev5