umm, so, do i understand it correctly that if you want to cast through @33bits you have to *connect a signer*?

dune says there are only 199 distinct fids that have done that (no vitalik, no dwr).

i guess if you really tried, you could also connect some of the casts to the account with pretty high level of confidence based on timestamps (signer approval vs cast).

dyor

It's in our todo. Two reasons - it was implemented before SIWF became a thing. Second one - verifying SIWF signature within the ZK circuit is quite a hassle. Not sure if anyone has done it before (or verifying EIP-712 signatures in general), please elaborate! Would be especially helpful if it's written in Noir (cc @zac-aztec)

CEO @aztecnetwork. Building a privacy-first L2 on Ethereum. Cryptographer, software engineer, ex-particle physicist. Plonk co-author. Huff inventor.

https://anoncast.org | anonymous posting for $ANON holders, powered by zk proofs | CA 0x0Db510e79909666d6dEc7f5e49370838c16D950f @anontokenbase

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

working on blockchain privacy

https://joshcrites.com

To cast with @33bits you have to connect Farcaster account, not your wallet (what anoncast does). Your idea would work if Farcaster clients allowed to sign messages with FID's address. The only signature we can get is SIWF.

Couldn't you build a merkle tree of the ethereum accounts associated with the first 20k farcaster accounts? then just use any old ethereum signature to prove ownership of an account and prove that the account is in the merkle tree. This is what @anoncast does afaict

Seems he's not all that active on farcaster. Will forward to their discord