protocols

Opacity

@androidsixteen.eth seems like @cdixon.eth  sees understanding the historic dynamics of Internet companies is how you can predict how things play out.

If the zkTLS thesis (admittedly not fully validated yet) plays out how I’ve been yelling about, then it represents a black swan primitive.

It introduces the possibility of forking existing web2 networks. It reduces down to a product problem:

Can you build something compelling enough to get a-lot of users to login and exfiltrate their data.

Theorem: Data availability and verifiability ensure the ability to fork networks (including existing web2 ones)

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

/opacity
/eulerlagrange

Let me play red team for a moment. 

When web2 incumbents wake up to this existential threat to their business, what’s their strategy to destroy zktls?

Building something new. 🟪 Host: /venturecapital /adventures /theitinerant

1. They can sue. As long as we uphold letting the user get their own data I’m confident a legal argument can be made it’s permissible.

We go after mobile app APIs because of a few advantages (stability is a big one vs web).

They can only make it harder to reverse engineer, not stop. Because they can’t rug their own products.

Theres only a few that are adversarial. Proof of employment from rippling id argue is harmless to them.

Extracting twitter social graph is different

1. You can change the standardized protocol to be even more MPC unfriendly.

This would require buyin from all the standards bodies, browsers etc.

Would only happen if we had a lot of success and money. We have the morally superior position as well.

If you were them, what would you do? Assume unlimited resources.