Adam Liposky

I don't know if it's particularly unique, but our strategy relies on, I think us going after kind of the solo developers, the indie hackers of the world.

Like we, we want to lean into this like replet for web three narrative, this replet for web three strategy where people can come in and build a chain very quickly, launch it in under 10 minutes and then iterate very quickly after that.

The way we're doing so is with the,

this launchpad, which provides them access to our community so they can get instant feedback.

So you launch a product, they look at your repo, they look at your code, and they say, okay, this is an idea I can buy into or not.

And the way the launchpad works is we put you out on a bonding curve.

If enough community interest comes along and validates the idea, the chain gets launched.

And so we think this is a powerful idea as like an alternative to a paywall.

So we could have put this product out there and we eventually probably will, where the person that has the money can go along and just buy an L1 and have us host it and eventually validators will come in.

And that's a fine idea.

But we want to rely instead upon the wisdom of our community because the token holders of Canopy should and will be the end decision makers, the end owners of our application, of our security layer.

And they are the people that should determine what applications become L1s and eventually which applications receive part of the canopy block reward.

And so when I think about kind of what's our wedge, where are we going?

It's like, let's make this as democratized as possible, not only from a development perspective, but also from like a what's successful perspective perspective.

Because the feedback these developers will get on the launchpad is probably some of the most valuable feedback they'll get through their entire process.

It'll seed their community.

It'll seed their growth.

And so, you know, I think if I have a wedge, that's probably the one.

Eventually, we'll take those case studies and we'll go after more and more experienced projects, more and more experienced leaders, more and more venture-backed teams.

But if we can build for the solo dev and the indie hacker, the person that doesn't call themselves a developer, anyone can use our tech under the hood.