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.

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

http://opacity.network

Nice thing is you don’t have to do zk after price is quoted depending on use case.

LLMs make it easy to maliciously price. Check if someone says “I have a lot of warps”.

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

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.

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

i’m surprised price discrimination isn’t done more on public chains tbh

Founder, zCloak Network. 
https://zcloak.network
https://cloakinglayer.com

The hard part is proving the signer is a valid eddsa. The state is stored in a contract on OP.

Generate a ZKP locally in a frame, get it verified and use the result to drive some business logic. Should be a lot of fun.