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
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
5/9
@fiveoutofnine.eth
(spitballing again) maybe a TEE w/ an API endpoint to update it every 12 hours, but someone can pay a fee + fund it to force an update?
2 replies
0 recast
0 reaction
jon
@jonbray.eth
extra trust assumption, but that could definitely work would still need a contract that references the TEE output but that would be a good solution to handle the heavy lifting!
0 reply
0 recast
1 reaction