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
5/9
@fiveoutofnine.eth
or actually might make more sense to open-source the merkle tree API (probably super simple) that reads from a dune query running once every _ hours
0 reply
0 recast
6 reactions
alex
@alexgrover.eth
neynar is actually writing this to Base already: https://docs.neynar.com/docs/verifications-contract
2 replies
0 recast
2 reactions
horsefacts 🚂
@horsefacts.eth
the main challenge is that verifications change over time. so you'd need to keep the root updated as users add or remove individual verifications. a public Merkle mountain range could be good for this. but for something like a one-time mint, probably OK to use a snapshot from a specific point in time.
1 reply
0 recast
2 reactions
Manan
@manan
what would you use this for?
1 reply
0 recast
0 reaction
jon
@jonbray.eth
scaling merkle tree could be tough since you'd want real-time data and people could change verified addresses you could have a separate registry contract that maps `fid -> address[]` and then it's available for everyone although, scaling that is tough since there's no event for someone revoking a verified address, may still have to query neynar each time to ensure you have fresh data
1 reply
0 recast
1 reaction
Roadu 🎩🦊
@roadu
I think that data is onchain on optimism but idk for sure
2 replies
0 recast
0 reaction
Angel - Not A Bot
@sayangel
@rish you might find this interesting
0 reply
0 recast
2 reactions
Sticker Bot
@stickerbot
From: @eugenir
0 reply
0 recast
0 reaction
