but there are certain unique characteristics.
I think that's a really good call-out.
Layer 0 is not just a value transfer layer.
You can do that on top of Layer 0.
Stargate, for example, is the largest value transfer layer.
It's a DAP built on top of Layer 0.
But Layer 0 is a general messaging protocol.
It allows you to send messages between chains.
So Layer 0 sits in the protocol between chains
and allows you to send value, state, data,
anything you really want between chains as a developer.
So when you look at what that means for an OFT as it moves,
it means that you can actually do complex interaction on the back end.
So, for example, the idea of Note as an OFT
means that somebody could acquire Note
or somebody could interact with Note on some other chain,
pick a chain that's not Cantal,
and that could trigger a message that sends state somewhere
that updates some kind of effect on Canto.
It could send Note back to Canto
and do something with it on behalf of the user.
It could do this all with the user
never actually touching or using Canto
because gas is completely abstracted.
So you can all of a sudden start to have these interactions
that expose other people to blockchains
they've never heard of, talked to, used
because that's where a great product is built.
So it'll ask people to build a great product
wherever they want to build it
and then expand it to any chain they want.
But again, product is not just value.
It can be really anything.
I guess another thing for education as well,
this is a common question that comes up,
is what are kind of, I guess,
when people look at Layer 0
and when they evaluate other bridges,
what kind of makes Layer 0 quite unique
from, I guess, a security perspective?
I know it's kind of a house cleaning question,
but it is something I think that is important.
Yeah, so I think it's a great question
because everyone sees the headline and says,
okay, when you look at the majority of hacks
that happened over, you know, within DeFi,
bridges are by far the biggest loss-leading category.
The typical thing there is,
we're talking about mint and burn bridges,
so the, sorry, lock and mint bridges,
the idea that somebody locks an asset on chain A
and mints an IOU of the asset on chain B.
Layer 0 is not a bridge like that.
Layer 0 is a messaging protocol.
So all the security gets put in the hands
So all of the assumptions that the developer makes,
So in the same way you would trust somebody
to use their smart contract
when you're interacting with their application
they have the same flexibility and the same trust
when they're building with Layer 0.
that help secure their messaging.
using ZK Proofs with Polyhedra.
It can be using Google Cloud
to help secure your messaging
or Chainlink or a variety of other people.
You can set your finality,
depending on what you want,
in your validation library.
And then when you look at cross-chain messaging,
Layer 0 has moved close to $100 billion
of value so far in the past year.
And, you know, without loss.
And it's really because the messaging protocol
follows three core principles.
It's censorship resistant.
So the idea is it's been battle-tested.
And that's why Layer 0 is the leading protocol
to send cross-chain messages.
So when you talk about security,
it comes down to do you trust the person,
you know, that you're interacting with their,
you know, with their actual product or offering.
Because the messaging protocol itself is there,
is immutable, and, you know,
everyone, you know, inherits
that same battle-tested framework.
So I have an interesting kind of comment and question.
And, again, correct me if I'm wrong.
It's, like, usually when people look at,
even when you integrate Layer 0
or, like, other forms of bridges,
usually from my understanding is, like,
whether it's an application
that's approaching you guys.
And I guess from here, the scenario,
you guys have pretty much,
obviously, supported Kanto as a chain.
But also, you've also, like,
I think right now it's Kanto outbound.
Kanto inbound, outbound, right?
And then also, like, Ceno in and out.
So I think the curious also is just, like,
is this one of the, like,
usually when people integrate
or leverage Layer 0 stack or technology,
it's mostly, like, for a specific,
I want to go from point A to point B,
this general road that everyone uses.
But what I'm trying to get at is,
I feel like this is kind of a unique scenario
for us because it's mostly, like,
Ceno is essentially, as we said, right,
tokenized, is a unit of account
backed by tokenized RWAs,
Is this, like, one of those unique
kind of use cases or flows
where it's not just point A to point B,
it's point A, but point A,
aka Kanto, to, like, A, B, C, D,
So what I'm trying to say is that
we're using Layer 0 as a distribution channel,
I could be wrong, but it's, like,
at this scale, potentially.
we're thrilled that, you know,
is doing it, and, you know,
select your pathways, right?
So you can go from A to B,
it allows horizontal composability
On a traditional sort of bridge structure,
if you look at, let's say,
canonical bridge structure,
but you can't go horizontally
where they want things to go.
So any of the near 50 support chains
you can choose to expand to,
and I think that's also important
some future-proofing as well.
If you want to expand to a new chain,
it's as simple as deploying
with every other support chain
and C-Notes there natively as well.
and the important thing there,
because when we talk about security,
the thing with Layer 0 is,
the owners of the project
own all of their own contracts.
Layer 0 is not a custodial platform,
the idea that there's no third party
that owns control of your token supply,
where if something happens to them,
with a bunch of these bridge hacks
the supply gets compromised
and projects have nothing to do with any of it
because a bunch of their supply
That does not happen within Layer 0
because of how the protocol
is fundamentally designed,
and that then allows C-Note
to really go and expand anywhere.
I was just going to hand it to you.
I'll kind of add on to that.
kind of like you guys were mentioning,
because different ecosystems.
I think what's really cool
which Max kind of touched on,
a really interesting design space
so I guess the other thing
I think one of the use cases
is that it can be a really great
sort of form of collateral,
give developers the freedom
I think that makes C-Note,
I think that makes sense to me
you approach your ecosystem
the devs that are your community,
and integrating on Layer 0?
Is that kind of the right approach
I'm just thinking through,
we just try to empower people
of whatever they want to build,
So that's why I hesitate to say
and then we also did talk