Open source the dApp layer

Why dApps are closed source, and how opening them up will drive 10x web3 adoption

15 years into this great blockchain experiment, and most enterprise builders in Web3 are still using Web2 business models. This makes total sense. Building software is hard. Finding VC to scale said software is harder. Especially when you need to show recurring revenue growth month-over-month.

So what happens. We all sell access to our blackbox APIs and UIs. Pay $49/mo, $.0002 per compute, whatever the going take rate is, and hope that our sales funnels convert to paid at a high enough percentage to find follow on capital.

But what does this leave us with.

A bunch of disjointed, fragmented, proprietary codebases no actual large enterprise will ever touch!

Every single enterprise dApp builder in Web3 is too small to be trusted with an API blackbox. The risk to enterprise is too large. What if this little SaaS company fails, what if their APIs go down.. cough cough Recur.

No shade only love intended for our closed source homies grinding it out the only way they know how.

--

With that out of the way, let’s dive into how dApps are currently made, and why open sourcing the dApp layer will 10x the growth of Web3.

What is a “dApp”

Does slapping a “d” for “decentralized” in front of application really mean anything? What properties separate a Web3 dApp from a regular Web2 app?

The answer is “blockchain”! A web3 dApp interfaces with a public immutable database somehow, while a Web2 app does not.

• This can be as light footprint as a bit of data storage onchain

• All the way to dapplications that run entirely onchain