In web2, they who control the App on the users’ phones control the distribution.

If your dapp needs a particular ML model to be run to identify face from a video, count the number of reps of pushups from a video etc. Create a trained model and upload to a public repository.

I think we routinely keep talking about bringing 1B users to web3. It’s a wrong mental model, and we end up building the exactly wrong products.

We’re lying to ourselves what web3 is about. Just because someone named it web3, we’ve forced ourselves to come up with a usecase that is incremental to web2.

Common traps that developers fall into which stops them from moving fast and breaking things. I’m going to invite a lot of shit on myself for this - but ok …

Most web3 developers are writing code that is centralized. They’re just writing web2 code in Solidity. Be careful when you’re overpaying for “web3 developers”.

I wrote earlier that NFTs are an essential piece in the identity layer on web3.

Grants are treated as charity; A moral obligation for successful projects to redistribute the wealth they’ve created. That is exactly where some protocols and DAOs go wrong.

DAOs are the biggest misnomer of web3. They don’t work, and no one seems to know how to make it work. Here, I present a view to challenge the way we look at DAOs to begin with.