Neofinance & Omnichain RWAs w. Layer Zero x Canto

Recorded: Oct. 25, 2023 Duration: 0:41:54
Space Recording

Full Transcription

We'll be right back.
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 interaction.
It can be really anything.
That makes sense.
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,
it's just like,
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
of the end developer.
So all of the assumptions that the developer makes,
they choose.
So in the same way you would trust somebody
to use their smart contract
when you're interacting with their application
or product on chain,
they have the same flexibility and the same trust
when they're building with Layer 0.
They select the entities
that help secure their messaging.
That can be, you know,
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 is permissionless.
Anyone can build on it.
It's censorship resistant.
And it's immutable.
So the idea is it's been battle-tested.
It's in production.
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.
That makes sense.
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.
And then also, like,
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,
and that becomes, like,
this general road that everyone uses.
But what I'm trying to get at is,
is this, like,
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,
in this case, T-bills.
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,
or whatever endpoints
kind of Layer 0 support.
So what I'm trying to say is that
we're using Layer 0 as a distribution channel,
which I feel like made,
I could be wrong, but it's, like,
I've never seen that
at this scale, potentially.
Yeah, Layer 0 allows,
and, I mean,
we're thrilled that, you know,
is doing it, and, you know,
it allows you to sort of
select your pathways, right?
So you can go from A to B,
you can go from B to C,
it allows horizontal composability
across your offerings.
On a traditional sort of bridge structure,
if you look at, let's say,
an L1 to L2, you know,
canonical bridge structure,
you go one way,
but you can't go horizontally
between different L2s.
Layer 0 is a framework
that allows, you know,
builders to pick
where they want things to go.
So any of the near 50 support chains
on Layer 0,
you can choose to expand to,
and I think that's also important
because it provides
some future-proofing as well.
If you want to expand to a new chain,
it's as simple as deploying
a contract there
and hooking it up.
And all of a sudden,
that chain is integrated
with every other support chain
and C-Notes there natively as well.
and the important thing there,
and when I say natively,
it's really important
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,
It's a protocol.
It's not a platform,
it's not a service,
it's a protocol.
the idea that there's no third party
that owns control of your token supply,
there's no third party
that's holding something
where if something happens to them,
you're in trouble,
which we've seen
with a bunch of these bridge hacks
the supply gets compromised
and projects have nothing to do with any of it
just get wrecked
because a bunch of their supply
gets put out there.
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.
That makes sense.
I was just going to hand it to you.
I'll kind of add on to that.
obviously,
are really cool,
kind of like you guys were mentioning,
that's really just,
value transfer
between that,
because different ecosystems.
I think what's really cool
Layer 0 is,
generalized,
cross-chain messaging,
which Max kind of touched on,
and I think there's,
a really interesting design space
to explore
in terms of,
allowing protocols
integrate C-Note
into their,
architecture,
more seamlessly.
so I guess the other thing
we should talk about
other than just being,
a stable store of value,
what is C-Note?
I think one of the use cases
that we're envisioning
is that it can be a really great
sort of form of collateral,
whether that's for,
other lending markets
on other ecosystems
protocols,
things of that nature.
If we can,
Layer 0's distribution
give developers the freedom
to kind of,
develop their own
systems around it,
I think that makes C-Note,
a lot more powerful,
if that makes sense.
I think that makes sense to me
and I guess,
is that something,
is that how
kind of you guys,
you approach your ecosystem
the devs that are your community,
at least people working
and integrating on Layer 0?
Is that kind of the right approach
or right way to think
Mostly to Max,
I think we,
I'm just thinking through,
I think that we
are fairly agnostic
about what people
build on top of Layer 0.
we just try to empower people
to try and build
the best experience
of whatever they want to build,
So that's why I hesitate to say
we think about this
in one way or another
I see things built
on top of Layer 0
on a near daily basis
change the way
that I think about
what's possible
or potential
for the protocol
or how people
could use it.
That's why
I don't really have a,
My mind is continually
blown by other people
and what they do.
Let's put it that way.
Fair enough.
that makes sense.
I think we can maybe,
head into more,
just some more stuff
what we're working on
in terms of Canto.
we did talk about,
from a really high level
about Neo Finance,
and then we also did talk
I guess a question,
and we did talk briefly,
but I guess,
maybe if you want to
kind of talk about,
the general flows,
how could someone
get CNote today
maybe if you want to
talk about
general flow,
and then maybe,
let's start there,
and then I'll add on
after that.
I think the easiest way
for people to get CNote
is actually just to
pay for it
on Slingshot.
we deployed
a CNote USDC pool,
and right now,
quite a bit of
liquidity in it,
so if you're
acquire CNote,
that's probably
the easiest way
to get it.
another way
if you already
have Note,
you can supply
that into the
lending market,
and then you'll
receive CNote.
As I mentioned
the collateralized
receipt token
Cantilani market.
those are the two
ways that you can
currently get CNote.
And then I guess
touching on that,
if you do want
to bridge your
CNote out,
currently,
we have that
supported for
Ethereum via
the Layer 0
you can just
use the bridge
on Kanto.io
to do that.
There will be
like a CNote
and that way
you can take
CNote from
into Ethereum.
That makes sense.
approach the
latter part of
this space,
I think maybe
we could also
talk about
obviously,
especially,
that's the
way to get
could maybe
talk about
some other
potential ways
where CNote
Coordinator
like maybe
very briefly
of what we
anticipate,
what we see
happening in
maybe lending
markets or
other forms
of collateral
coming because
just touch
anticipate.
what you're
really talking
one of the
big things
that we're
envisioning
downstream
markets on
So there's
one in the
works that
of working
with other
CNote will
kind of plug
will be able
downstream
that others
can borrow
collateral.
kind of like
downstream
downstream
And that's
kind of like
what I was
alluding to
before when I
mentioned that
we think that
CNote is a
really good
sort of form
of collateral.
we're going
of see how
that plays
pretty soon
this stuff
releasing.
touching on
coordinator,
something that
sure exactly
which allows
many lending,
lending market
works similar
where it'll
allow people
their Kanto
to receive
start voting
on different
lending markets
or different
like lending
lending markets
rewards to.
that we're
incentivize
initial use
that scenario,
like not only
receiving the
interest on
CNote itself,
for actually
supplying it
into certain
lending markets.
is like the
general overview.
material about
pretty soon.
So definitely
lookout for
that makes
Thank you,
about there
of Coderino
competitions
last month.
Neo Finance
coordinator,
stuff like
they could
if you will,
about that.
approaching
the summary
integration
with Layer
I personally
want to see
and explore
the design
capabilities.
and having
accessible
everywhere
is extremely
interesting
distribution
personally,
but personally
super excited
is capable
having this
my opinion,
interesting
collateral,
accessible
developers
ecosystems
liquidity,
fascinating.
importantly,
accessible
interesting.
importantly,
mentioned,
interesting
accessible
increasing
capabilities
omni-chain
applications
interesting
themselves
interesting
experiments
showcasing
distribution
everything
struggling
there must
everyone's
every time
giving you
a disclaimer
really bad
seems like
requests till
some people
a question
question so
we'll just
there's no
people were
complain about
well thank
for having
it's always
always great
yeah thanks
I'm looking
forward to
have spaces
talk about
interesting
been explored
can't can't
wait thanks
thanks everyone

Speaker