I’ve come to the conclusion zk interaction with frames is going to be crucial. Particularly when payments are added to frames.

If the fid is known before a price is quoted, then it’s actually quite easy to charge more based on activity.

Many ways, but I can check onchain spending habits and adjust accordingly.

Foster open dialogues on Farcaster | Zk prove your fid & cast privately | Cast: https://33bits.xyz

Working on building zkTLS infra/products. A ruthless empiricist and meme connoisseur.

http://opacity.network

yes! i think, it is also a good opportunity for privacy focused mini-apps. for example @33bits within a frame would be really cool

This sort of implementation makes a trust assumption on the party indexing the signers. It works in the case each app makes its own tree.

You can also use state proofs. Noir has an implementation of Ethereum state proof verification.

As a start I’m not against each app indexes its own merkle tree.

You're right, current implementation brings additional trust assumptions. The first version on 33bits was made with storage proofs! But it never saw the light of day since the current Noir implementation results in too many gates, which makes in-browser proof generation impossible (hits the RAM limit).

Full-time builder. @pimlico | @33bits | @66bits | farcaster-solidity | x.com/potekhin_sergey. Zero-knowledge and asynchronous transactions evangelist.

tried storage proofs before 

But will let @fastfourier.eth speak about this