wow got answered in 1min already

2nd question: is there an easy and efficient (cheap) way to get either (i) all fids' connected addresses easily or (ii) changes in connected addresses?

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

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

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