Adam Liposky

Our technology that we've built, our security system is recursive, which means you can both receive security from the Canopy blockchain and also provide security out.

So there's scalability in multiple ways.

We can go horizontal where a lot of chains are secured by one security route.

And we can go vertical where those security routes secure chains that become security routes themselves and secure other chains.

And so now you've got a situation where you can have an application specific security environment that is tailored to a particular use case.

So you act not only as like an application that captures value in your own right, but you can secure other chains as well and act like a layer zero to them, adding to your utility.

It's sort of a very under the hood thing that we're talking about here, Sam.

But I think for us, it's about producing value and capturing that value at the token level for these.

Yeah, yeah, yeah.

Our system's all about alignment, first and foremost.

We want to align the security providers directly with the application themselves.

And there's no better way to do that than have the security providers own the native tokens of the chains they secure.

And so what our system essentially boils down to is a token gated security mechanism.

We use restaking that was made popular by Eigen.

And we use that for capital efficiency.

But effectively, these security providers put at risk the value they have staked in the system against a new application.

They run that software.

And then in order or in exchange for that security, the applications pay them in their native tokens.

They can also pay them

in Canopy tokens as well, which is our long run sustainability mechanism.