Exciting career update 🤗
To all my friends at L2BEAT: it was a pleasure working among some of the brightest minds in the space.
But from today on, i'll be all in on @ethbeat_org, seizing a once-in-a-lifetime opportunity.
My reason? They pay way more money.
L2BEAT is now ETHBEAT.
5+ years of keeping L2s accountable, now extended to privacy, interop, staking and beyond. One goal: transparency on the guarantees users get on Ethereum.
Thank you to the community that got us here. The next chapter starts today! https://t.co/6ked4PxhPy
@arik_g@ethereum well said, or as i always say privacy is more private than privation, thanks to the https of confidentiality, merry post-quantum ai compliance.
@Ether_Gavin@unhappyben lmeow yes but so far it's not working, we could have these optin list providers rn for tcash for example but for some reason it seems very hard to do (@0xprivacypools built something cool for tcash afaik but only with their single closed list source of mysterious origins)
for compliance, imo sweet spot on the surveillance maxi vs cypherpunk/CROPS spectrum is opt-in, rich tooling to selectively disclose what you want/need to.
an app, ramp, exchange, service requests what they want you to prove, and you prove and use it or go elsewhere.
i know that infra for this is lacking. first step would be open onchain black/whitelists of public addresses, maintained a bit like adblock lists (+diversity, palantir can also make one if they like).
so yeaa we need better oracles, again :>
@kassandraETH@z0r0zzz yes they are! but pls focus shift to quality over quantity. for example a frontend / wallet that is more private and secure than the others. good trusted setups. only one tacit pool made the bar into ethbeat privacy section and the rating is not impressive https://t.co/IXRkkhw8iF
@zama isn’t private, it’s a product where sender and recipients are public, where onchain analysts can easily decrypt balances, and has privileged insiders who can see everything
why is it being shilled by @ethereum
some @0xprivacypools v2 historical data to back our claim:
> you are doxxing your deposit to each 'private' transfer recipient
- 516 of 528 compliance list (ASP) updates added exactly 10 labels
- 87% of labels in the current (largest) list are decoys
- ~1 deposit per set update
@Zodomo@0xmikemcc@0xprivacypools i hope my thread is not that unclear: this label will ONLY be known by the recipients you are sending private transfers to
@Zodomo@0xmikemcc@0xprivacypools i hope my thread is not that unclear: this label will ONLY be known by the recipients you are sending private transfers to
@dev_tawago@0xprivacypools@zERC20io circuit, wallet, enclave image and Lean proof code are not public it seems and usage is tiny, so no privacy to be had there
@ameensol agree the extremism is not useful but it would be nice if you were actually discussing ppv2's leaky tech for once (e.g. labels or the sloppy frontend) instead of trolling with the trolls https://t.co/CDxvk5CWtA