Content
@
0 reply
20 recasts
20 reactions
MunicipalBondLagrange
@eulerlagrange.eth
Hey everyone, I figured out a fairly simple way to achieve ZK frame interaction. IMO, anon frame use will be very important as the protocol scales. It's also a potential way to break recast to use frame. See: https://warpcast.com/eulerlagrange.eth/0xea60f72d https://github.com/farcasterxyz/protocol/discussions/145
3 replies
6 recasts
34 reactions
Sergey Potekhin
@fastfourier.eth
Can you provide more details about how the Semaphore is used here? Also, there is only one key for each FID which may become a problem considering that we have a decentralized protocol with a variety of clients. What if we associate a new key with a signer instead of an FID?
2 replies
0 recast
0 reaction
MunicipalBondLagrange
@eulerlagrange.eth
I’ll write an answer to first question in the morning. As for the second, each fid can have multiple signers. So associating a semaphore identity to the signer would allow for a fid to have multiple semaphore identities. In an anonymous poll, a fid could vote multiple times undetected.
2 replies
0 recast
1 reaction
avi
@avichalp.eth
although replay protection is important but this restriction (one key per fid) would mean user cannot use multiple privacy clients at the same time? also app developers would have to compete for users in a zero sum way which kinda sucks
1 reply
0 recast
1 reaction
MunicipalBondLagrange
@eulerlagrange.eth
There are a few ways around this but they introduce complexity. 1. Extend semaphore identity commitment for multiple identities (multiple clients) 2. Instead of trapdoor/nullifier, you add a public key. Then each client gets a trapdoor/nullifier signed by the private key
0 reply
0 recast
1 reaction
