I need a blockchain op sec expert to explain, on a scale from "total anonymity" to "telegram", how anonymous this app truly is.

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

The app knows who cast. 

It’s got a centralized api. 

Perhaps overtime it’ll move to an onchain event that gets tweeted.

@lastdotnet | @pleasrdao | flipping bits through timΞ | 

both peter and paul

App does not know who casted, code is open source and no identifying info is sent/captured.

Still gotta a trust I’m running the same code for now. That was the reason to not launch anonymously and hope people trust me enough for that until I figure out how to verify that.

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

http://opacity.network

You could prove the deployment by creating a zkTLS commit hash proof.

cc @eulerlagrange.eth

Yeah always the challenge in terms of proving what’s being run. 

I thought I saw something about decoding signatures but didn’t dig too deep. Must be decoding the proof.