5/9 pfp
5/9
@fiveoutofnine.eth
thinking about how to authenticate `msg.sender` on-chain as someone that controls a given `_fid`: 1. query dune for all (fid, verified address) pairs (updated via neynar) 2. generate merkle tree over all w/ keccak256(fid, address) 3. host API and/or publish this somewhere for free am I missing something
8 replies
3 recasts
19 reactions

Manan pfp
Manan
@manan
what would you use this for?
1 reply
0 recast
0 reaction

5/9 pfp
5/9
@fiveoutofnine.eth
verify `msg.sender` controls a fid more specifically, I think doing an NFT mint where fid and token ID are mapped would be cool cause anyone can just mint it in the feed, and it's somewhat personalized. like if there's 100s of these
1 reply
0 recast
1 reaction

Manan pfp
Manan
@manan
makes sense. we did consider doing this (@stephancill h/t) but the use case was limited to new contracts with custom mint or claim ABIs that passed in fids + merkle proofs. another assumption we made here was that if you're trusting neynar to generate proofs & host the API, might as well do the address <> fid verification offchain using our API, generate signed message on your end, pass it into your contract function and verify it. happy to reconsider based on any new povs we might've missed
1 reply
0 recast
3 reactions

5/9 pfp
5/9
@fiveoutofnine.eth
hmm yeah this makes sense, I guess the merkle tree solution would require a trusted server to serve the proofs too
0 reply
0 recast
0 reaction