►
From YouTube: Community Call: Product & Protocol April 11, 2023
Description
LOA Labs and Quicksilver join the call to discuss their recent governance events. Ryan Christoffersen talks Regen Ledger 5.1 and Cory Levinson demos the new Regen Ledger/Polygon bridge for NCT.
A
A
Today
we
are
going
to
be
getting
into
some
governance,
first
kind
of
a
break
from
our
normal
timeline
just
to
come
date.
Some
schedules
so
we're
going
to
start
with
low
Labs
talking
about
some
work
that
they're
doing
on
a
codifying
region,
Network
governance
and
then
we're
going
to
talk
about
Quicksilver
and
they're,
not
currently
in
governance.
But
talking
about
kind
of
the
effects
of
that
Governor's
proposal.
We're
gonna
go
into
regen
Ledger
5.1
upgrade
Ryan's
going
to
be
on
to
talk
about
that.
A
B
Yeah,
yes,
thank
you
appreciate
the
opportunity
hi
everyone
Dave
Fortson
here
long
time,
partner
of
regen,
Network
and
regen
Network
development,
since
during
the
early
days
of
2017,
all
the
way
to
now
also
have
a
history
in
web
2
governance
as
a
former
Politico
activist,
both
inside
and
outside
of
traditional
government.
So
this
is
a
topic
that's
near
and
dear
to
my
heart.
We
also
a
long
time
validator
for
regen
Network
as
well,
so
Lola
Labs,
Loa
labs.io.
B
B
You
know,
in
this
case
app
chain
for
the
origination
of
ecological
assets.
I
think
we
just
realized
that
we're
just
early
stage
enough
to
be
able
to
move
around
and
think
critically
and
reflectively
about
how
we
can
shape
this
appropriately
within
regen
and
also
just
further
far
enough
along
where
we've
already
had
some
ability
to
look
in
the
rear
view,
mirror
like
what
you
know,
I
think
we're
20-some
proposals
in
you
know
and
I
expect.
B
The
velocity
of
proposals
coming
at
the
regen
ecosystem
is
going
to
increase
dramatically
around
you
know
anything
from
credit
classes
to
community
spends
to
signaling
proposals
about
where
the
community
wants
to
go
on
any
particular
issue.
So
to
that
end,
we've
been
following
along
obviously
closely
as
a
validator,
but
also
as
a
just
a
Community
member
who
wants
to
really
take
a
look
under
the
hood
at.
How
can
we
improve
governance,
decentralized
governance
for
regen
Network?
B
B
What
are
the
issues
that
you've
seen
either
retroactively
or
that
you're
contemplating
moving
forward
are
required
for
us
to
be
good
stewards
of
this
ecosystem
as
a
community-
and
you
know
anything
from
you
know
and
I'll
just
you
know,
double
click
into
like
Community
spends
around.
What
does
accountability
look
and
feel
like
for
regen
Network
ecosystems?
You
know
where
you
know
again,
I
think
on
a
very
Baseline
level.
It's
Community
spend
somebody's,
got
an
idea
around
how
they
want
to
serve
the
network
or
the
movement.
B
More
broadly,
they
appeal
to
the
community
for
a
chunk
of
money
that
money
gets
handed
over
and
then
what
that?
That's,
how
that's
you
know
how
I
think
the
Baseline
operations
has
started.
I
think
we
agree
that
there
are
I
think
important
ways
that
we
need
to
add
accountability
layers
into
that
program.
B
Other
things
you
know
again
just
thinking
about,
and
then
as
far
as
proposals,
you
know
like
what
is
the
phase
proposals
to
ensure
the
highest
level
of
community
engagement
early
on
and
get
really
early
signaling
proposals
from
obviously
getting
some
something
up
on
Commonwealth
socializing,
on
Twitter
having
internal
snapshots
to
give
a
sense
of
the
community
all
the
way
to
getting
these
things
on
chain.
Are
they
parameter
upgrades?
Are
they
simple,
signaling
proposals?
What
do
we,
what
level
of
restrictions
do
we
want
to
I?
B
Don't
know
if
restrictions,
the
right
word
parameters?
Do
we
want
to
activate
to
ensure
that
proposals
have
been
socialized
and
metabolized
within
a
community
before
we
get
them
on
chain?
Do
we
want
to
have
sub-dials
at
some
point,
I
mean
there's
a
number
of
different
ways.
We
could
do
this,
so
these
are
the
kinds
of
things
that
we're
hoping
to
explore.
B
A
Sorry
I
actually
have
a
few
thoughts.
One
I'm
so
excited
that
you
guys
brought
this
up,
because
this
governance
process
is
going
to
have
to
be
codified
at
some
point
and
they
can
either
be
after.
We
realize
what
codes
need
to
be
put
into
place
to
keep
our
blockchain
and
governance
processes
safe
and
streamlined,
or
we
can
do
it
now
when
it's
all
theoretical
and
set
up
those
safety
nets
before
they
even
be
need
to
be
used
necessarily
I
mean.
A
Obviously
we
have
some
review
behind
us,
but
so
one
that
two,
you
guys
have
done
quite
a
lot
of
work
on
just
kind
of
looking
at
how
governance
is
approached
in
the
cosmos.
Ecosystem-Wide
setting
and
you
guys
have
some
work
on
GitHub
I-
believe
that
you've
done
there.
Could
you
share
that
link
to
everybody
as
well.
A
B
B
You
know
again
what
I
was
sharing.
Is
that
we're
you
know?
Certainly
you
know
with
low
Lodge,
validator
and
I
know.
Your
team
is
spending
a
fair
amount
of
time
here.
Around
kind
of
top
principles
for
decentralized
governance
and
Community
spends
I'd
be
curious
if
you
had
any
just
high
level
Reflections
on.
D
C
C
C
D
D
D
C
I
mean
that
makes
sense,
I
just
sort
of
pick
up
like
right,
where
we
left
off
weird
anti-pattern
I.
Don't
think
this
is
obvious.
Governance
proposals
should
not
define
vote
options
at
all.
This
comes
from
the
maxim
that
Larry,
that's
larry0x,
he's
always
right
he's
been
saying
this
for
a
while
he's
right,
because
otherwise
you
can
Define
them
and
do
it
wrong.
This
is
a
silly
procedural
matter
that
we
can
eliminate
by
not
defining
the
vote
options,
but
they're
very
serious
about
that.
We
saw
this
in
Hub
proposal.
C
So
in
69
we
had
that
no
with
veto
that
discussed
the
concept
of
exit
I,
don't
know
if
you
remember
that,
but
basically
it
was
like
you
vote
no
with
veto,
and
this
measure
passes
your
validator
should
leave
the
network
and
I
took
that
as
a
threat.
Now
you
know
what
I
think
it
was
a
threat.
It
was
not
cool.
That
was
the
one
to
put
Taj
mwasm
permission.
C
Kazum
was
in
on
the
Hub
and
then
other
folks
felt
that
much
much
later,
very
recently,
the
ICF
transparency
proposal
that
my
defining
no
as
like
something
other
than
nil,
was
that
basically
the
no
option
on
that
reads
like
if
a
no
passes,
The
Hub
community
releases
the
entertain
Foundation
from
any
obligation
to
do.
Transparency,
reporting
and
I'll
tell
everybody
really
directly
that
I
wrote
that
myself,
because
I
personally
was
really
tired
of
I
I.
C
D
C
Oh
I'm,
so
sorry
Raul
is
building
a
UI
for
groups
and
I'm,
seeing
more
and
more
cases
where
the
group's
module
design
is
totally
correct
in
that
it
wraps
a
multi-sig
and
so
I
would
just
say
to
regen
Kudos,
because
I
I
know
that
the
region
Community
put
a
lot
of
work
into
groups.
I
know
that
the
Hub
community
did
as
well,
but
like
very
mutual
effort
there
and
I
think
it's
being
proven
as
we
speak,
like
the
need
for
that.
C
C
Can
I
brag
a
little
well
actually
I'll
just
shoot.
Let's
horn
and
jihan's
Horn,
they
collectively
came
up
with
the
design
for
proposal
104
on
the
Hub
and
I
suppose
that
software
wise
104
could
have
been
improved
that
funds
notional
by
the
way,
and
it
could
have
been
improved
by
having
streaming
in
the
code.
C
The
really
nice
part
about
104
we
can
quit
The
Hub
can
fire
us
there's
a
software
upgrade
involved,
so
it's
not
totally
ideal
and
that's
what
I
mean
about
having
streaming
functionality,
but
I
think
that
that
Progressive
part
is
very
important
for
maintenance.
Work.
Marco
made
a
comment
recently
that
I
fully
agree
with.
He
said:
look
if
we're
changing
every
team
every
couple
of
months.
C
Nothing
is
ever
going
to
happen,
and
so
few,
let's
like
take
a
couple
of
paths
simultaneously,
there
are
likely,
let's
say
feature
spends
on
software
or
Community
event
spends
right.
These
are
basically
one
shot
and
on
those
you
basically
just
want
to
verify
the
work
and
I
would
say
that
there's
some
trust
involved
in
both
because
let's
just
take
like
a
conference,
for
example
right
at
some
point,
the
conference
needs
to
be
funded.
You
are
taking
a
little
bit
of
a
leap
of
faith
and
on
a
feature.
C
Well,
I,
wouldn't
advise
like
software
development
groups
to
build
Futures
on
credit
generally,
you
might
want
to
have
like
a
half
payment.
Then
a
half
payment
and
the
groups
module
might
come
in
very
handy.
For
that,
like
delegating
say
you
want
a
feature
built
right,
well,
delegate
the
basically
take
money
from
the
larger
community
pool,
put
it
in
a
group
and
then
Fund
in
pieces
as
it
goes,
but
then,
when
it
comes
to
maintenance,
work,
I
I'd
encourage
the
regen
community
and
any
community
in
Cosmos
to
think
on
a
years-long
time.
F
Hey
yeah,
that's
me,
yeah
I
can
quickly
go
over
this
sort
of
run
through
Quicksilver.
You
know
where
we
are
in
region.
What
sort
of
our
plants
are
going
forward
as
an
LSM
proposal
at
least
going
around
in
the
Commonwealth
I?
Think
Jacob
will
also
want
to
talk
about
that
yeah
I
guess
just
to
introduce
Quicksilver.
You
know
with
a
liquid
taking
protocol
and
Cosmos
we've
sort
of
been
in
their
liquid
Stadium
research
space
for
a
while,
the
team
we
come
from
Chorus
one
and
yeah.
F
We've
certainly
been
working
on
this
for
a
while
I
think
to
introduce
like
the
quick
silver
liquids
taking
solution.
There's
I
think
two
main
things
that
we
do
differently
than
most
liquid,
staking
Solutions
in
crypto.
First
being
that
we
have
a
completely
unrestricted
validator
set.
That
means,
while
liquid's
taking
you
can
delegate
your
assets
to
any
validator
that
you
know
natively
exists
in
the
chain,
so
there's
no
gatekeeping
by
us.
Obviously
this
promotes
decentralization
stake.
Distribution
and
validators
can
still
do
what
they
usually
do
right.
F
Let's
go
out
and
get
steak,
you
know
for
their
validator
support
their
costs.
That
sort
of
thing,
so
quick
service
promotes
that
side
of
things
and
the
other
thing
we
also
work
on
is
governance
right.
You
know
we
let
Q
region
token
holders
vote
on
governance
reports,
so
we're
working
on
that
that
will
come
live
very
soon
and
the
cool
thing
about
this
is
you
can
vote
on
these
proposals
while
you
have
your
assets
on
remote
chains.
F
F
You
is
taking
it
using
it
in
D5,
but
you're,
also
like
you're
participating
in
governance
and
exercising
like
your
validated
choice
or
your
rights
regarding
voting
power
distribution
right,
so
that
some
of
the
things
that,
with
silver
some
of
the
themes
that
putslow
works
with
yeah
I.
Think
as
it
stands
now,
you
know
we're
live
with
regen
the
Q
region,
regen
pool,
is
live
also
on
osmosis,
so
definitely
something
to
check
out
and
there's
the
proposal
for
a
liquid
staking
module
right
now.
F
Okay,
maybe
I
can
quickly
run
through
the
safe
module
and
then
I'm
happy
to
take
questions
and
like
open
up
a
discussion.
So
this
liquid
sticking
module
is
essentially
a
module
that
replaces
I,
think
it's
taking
module
and
Native
chains
and
what
it
essentially
does.
Is
it
tokenizes
your
state
position
into
like
a
non-fungible
delegation
share?
F
So
if
I
have
like
a
thousand
regions
take
with
validator,
a
I
can
essentially
claim
like
a
thousand
region
with
validator,
a
non-fungible
share
or
token
kind
of
thing
right
and
now
I
can
use
this
in
liquid
statement
protocols
to
essentially
claim
Hue
region.
So
what
you're
actually
doing
is
you
don't
have
an
unbonding
period
when
you
enter
from
staking
into
liquid
staking
right?
So
this
is
supposed
to
bring
like
a
large
amount
of
stake
into
liquids.
F
F
C
C
F
Yeah
I
think
I
honestly
think
that's
a
great
idea,
because
in
many
ways,
if
you
essentially
make
your
base
pair
a
liquid
sticking
pair,
then
the
cost
to
incentivize
this
pool
would
be
really
low
right.
So
whatever
a
chain
or
a
community
spends
on
bootstrapping
its
liquidity
or
essentially
ensuring
that
the
liquidity
of
that
token
continues
in
the
form
of
incentives,
the
amount
required
to
do
that
would
be
a
lot
lower,
because
you
know
half
of
that
pair
is
owning
sticking
towards
anyway
right.
F
So,
if
you
have
a
Q
region
at
a
pool
the
amount
of
incentives
you
require,
that
would
be
much
lower.
So
that's
definitely
like
a
great
approach
and
especially
with
the
LSM
right
you
have.
It
becomes
now
a
lot
easier
for
people
to
LP
the
Q
region
and
like
a
deeper
liquidity,
means
that
you
could
sub
potentially
start
using
huge
and
other
D5
use
cases
right.
I
think
that
would
also
be
great
for
the
ecosystem.
F
I
think
currently
say:
Network
and
dydx
are
seriously
considering
using
a
staking
staking
derivatives
as
their
base
pair
asset
I.
Think
on
a
few
dances
like
shade,
swap
forge
on
Atmos
they're,
also
using
like
staked
staking
derivatives
as
their
base
pair,
which
then
branches
off
to
everything
else,
so
I
think
in
Cosmos.
This
is
definitely
something
that
we're
seeing
and
unless,
like
the
cost
to
switch
over
is
massive
in
the
sense
that,
unless
there's
already
like
super
deep
liquidity,
I
think
it's
pretty
much.
F
A
no-brainer
like
most
of
the
new
projects
that
are
coming
in
and
new
tokens
that
are
launching
are
seriously
considering
using
a
liquid
state
token,
as
like
their
main
pair
right
and,
in
fact,
I
think
with
c
network
they're,
also
making
like
the
liquid
state
version
of
say,
their
default
staking
option
right.
So
you
begin
liquid
staking
right,
I
guess
for
them.
It
makes
sense,
because
Capital
efficiency
is
the
name
of
the
game,
but
in
general
it
is
a
trend
for
sure.
G
I
was
just
going
to
point
out
in
the
Forum
post
that
has
since
been
linked
in
the
chat.
I
had
asked
just
a
couple
questions
to
the
community
to
the
Quicksilver
team
into
engineers
at
regen.
So
if
any,
you
want
to
hop
in
the
thread
there
and
just
comment
on
some
of
that
stuff
that
might
help
get
more
information
out
in
public,
so
people
can
have
what
they
need
to
vote
vote
on
it.
A
G
A
I
Yeah
I'll
keep
it
pretty
short.
This
was
a
relatively
small
upgrade
we
upgraded
two
weeks
ago,
so
the
vote
turned
it
out
was
69.92
with
a
99.99.
Yes,
there
was
just
a
couple
of
stains
in
the
vote
and
other
than
that.
Yeah,
the
the
upgrade
went
successfully
executed
on
April
5th.
No
problems
happened
within
12
minutes,
big
shout
out
to
validators
for
being
prepared
and
available,
so
that
was
really
smooth.
I
What
it
included
essentially
was
just
updating
to
the
latest
patch
release
of
Cosmos
SDK
v046,
which
was
vo46.11
at
the
time.
12
just
came
out
last
week,
but
yeah
we'll
we'll
determine
when
we're
going
to
upgrade
it
to
that,
but
also
Jacob
and
his
team
have
actually
submitted
a
PR
to
start
the
work
on
updating
247.
So
that's
something
to
look
forward
to.
I
In
addition
to
the
update
on
the
cosmos
SDK
side,
we
also
did
some
updates
to
credit
batch
metadata.
Essentially,
this
is
part
of
a
larger
story
in
terms
of
separating
out
what
we
anchor
on
Chain
versus
what
we
don't
anchor
on
chain
in
what
we
don't
anchor
on
chain
is
more
specific
to
the
application.
I
So
if
you
are
cruising
around
app.regen.network
you'll
notice
that
there
have
been
updates
to
the
project
pages
and
a
lot
of
that
have
was
a
reflection
or
outcome
of
this
credit
batch
metadata
update
credit
batch
metadata
is
not
something
that
can
be
updated
by
a
credit
class
issuer
or
a
credit
class
admin,
because
it
could
actually
affect
the
price
of
credits.
So
that's
why
it
is
included
as
part
of
a
software
upgrade
and
done
as
a
manual
migration,
so
that
was
included
in
this
update.
I
It
should
be
a
network-wide
vote
because
updating
the
date
criteria
could
affect
the
price
of
the
underlying
token
of
the
basket
in
this
case
NCT.
So
we
implemented
a
fix
for
the
basket
creation.
We
also
fixed
user
error
to
make
sure
that
credits
could
be
pulled
out
of
the
basket
in
a
tradable
state
when
creating
the
basket.
There
was
a
flag
that
was
missed
in
terms
of
basically
disabling.
I
This
Auto
retire
functionality
and
we
included
this
new
governor
message
that
allows
for
updating
date
criteria
and
then,
finally,
we
added
a
few
event
fields
to
the
bridge
events.
This
wasn't
blocking
the
bridge
launch,
but
this
helped
us
like
optimize
and
improve
our
monitoring
of
the
bridge
service.
So
we
stuck
a
few
events
in
there
to
yeah,
improve
the
bridge.
Service
monitoring
specifically
and
the
bridge
is
now
live
and
launched
and
using
those
optimizations.
A
H
Well,
I
think
if
you
could
keep
this
on
for
a
second
and
then
when
I
walk
through
this
after
I
walk
through
this
slide,
I'll
take
over
screen
sharing,
so
the
polygon
regen
Ledger
bridge
is
live.
This
is
a
project.
That's
been
underway
by
r
d,
in
partnership
with
the
toucan
team
for
I.
Haven't
I,
don't
know
the
exact
star
tape,
but
it
must
be
over
a
year
at
this
point,
I'm
pretty
sure,
at
least
in
concept,
if
not
like,
in
actual
like
legitimate
implementation
work.
H
So
what
that
means
is
that
tco2s,
which
are
two
cans,
representation
of
Vera
credits
that
are
eligible
for
the
NCT
kind
of
pools
or
the
NCT
baskets,
as
they're
known
in
regen,
can
now
be
bridged
to
regen
Network
under
the
tco2
credit
class.
So
we
have
a
credit
class
instantiated
on
regen
Network
that
is
managed
jointly
by
the
r
d
and
toucan
team,
and
the
issuance
of
credits
under
this
credit
class
is,
is
basically
managed
automatically
through
a
fully
custodial
bridge
that
we've
developed
in
partnership
with
the
toucan
team.
H
It
listens
to
bridge
initiations
from
polygon
and
when
those
happen,
it
issues
the
corresponding
credits
on
the
regen
Network
blockchain
under
the
tco2
credit
class
and
in
the
same
way,
when
an
end
user
initiates
credits
on
regen
Network
of
this
tco2
credit
class
to
be
bridged
back
to
polygon,
then
those
will
pop
up
on
on
the
other
side,
just
as
they
originated
so
in
terms
of
functionality.
What
that
means
on
regen
Ledger
credits
can
be
retired
for
climate
accounting
credits
can
be
listed
in
the
marketplace
for
secondary
sales.
H
End
credits
can
also
be
basketed
into
NCT
on
regen
Ledger.
The
reason
I
have
this
asterisks
here
for
basket-
is
that
you
know
retirement
and
listing
credits
in
the
marketplace
is
something
that
you
can
do
if
you
hold
any
credit
on
regen
Ledger,
but
this
basketing
functionality
into
NCT
is
something
that
is
only
possible
with
these
tco2
credits,
as
as
the
acceptance
criteria
for
the
NCT
standard,
which
is
a
token
standard
managed
by
the
toucan
team,
is
nature-based
methodologies
of
credits
issued
by
Vera.
E
H
So
what
you
can
see
here
this
is
the
bridge
tokens
page
of
the
toucan
app.
If
you
click
on
your
tokens,
you'll
see
some
tokens
like
if
you're
bridging
to
another
chain
and
some
unsupported
tokens.
The
thing
is:
you
first
have
to
select
your
destination
chain,
so
first
we'll
select,
regen,
Network
and
now
the
tco2s
that
I
have
which
are
available
for
bridging
pop
up
right
here.
H
If
you're
not
seeing
any-
and
let's
say
you
have
some
NCT
in
your
balance,
you
would
first
need
to
actually
redeem
tco2s
from
that
NCT,
which
has
nothing
to
do
with
bridging.
So
you
would
just
do
that
through
the
toucan
app
and
then
you
would
have
these
tco2s
in
your
balance
on
polygon,
so
I'm
going
to
select
these
I'm
going
to
select
0.25
of
my
balance.
So
half
of
my
balance
for
the
recipient
address
I'm
going
to
go
over
to
Kepler
and
send
these
to
my
regen
wallet.
H
H
And
we'll
be
able
to
see
it
actually
show
up
on
the
regen
side
in
a
couple
minutes
after
this
is
reached.
120
blocks,
so
I
wanted
to
take
a
pause.
Then,
while
we're
waiting
for
that
and
also
talk
about
another
feature
that
we
launched
just
this
past
week
on
regen
Network
and
that's
the
addition
of
user
profiles,
so
here's
my
regen
profile,
which
I've
made
for
this,
is
actually
my
gecko,
that
I
have
back
at
home
in
Los,
Angeles
gekko's
name
is
Raphael,
and
this
is
Raphael's
user
profile.
H
You
can
share
it
so
that
you
know
your
community
or
friends
and
family
can
see
the
carbon
credits
that
you're
holding
the
carbon
credits
that
you've
retired
and
yeah.
This
is
this
is
the
first
kind
of
feature
that
we've
launched
enabled
by
this
new
off-chain
login
system
that
we
built,
which
connects
with
Kepler
so
similar
to
how
Commonwealth
allows
for
you
to
log
in
Via
Kepler.
H
If
you're,
the
administrators
of
those
entities
on
chain
you'll
also
be
able
to
control
and
manually,
manage
a
set
of
off-chain
metadata,
like
descriptions,
Gallery
images
Etc
directly
via
the
marketplace
interface,
so
I
wanted
to
talk
through
a
little
bit
of
that.
While
we
were
waiting
here,
if
we
refresh
it
looks
like
we're
still.
E
A
H
You
know
I
think
it
was
we.
We
were
looking
for
a
very
like
nice
and
appealing
name
that
was
also
gender
neutral.
As
we
don't
know,
the
gender
of
our
baby,
gecko
I
mean
I,
guess
they're
not
as
much
of
a
baby
anymore,
but
it's
quite
I,
don't
know
I,
think
I,
maybe
Alex
I
know
that
you've
got
a
whole
lot
of
reptiles.
Maybe
you
and
I
can
have
a
chat
about
gender.
Identifying
geckos
I.
H
H
H
H
H
This
is
the
transfer
right
here
success,
so
you
can
view
the
outgoing
transaction
on
the
polygon
side,
the
incoming
transaction
on
the
regen
side,
and
we
can
go
to
bridgeable
Eco
credits
and
you
can
see
my
balance
is
right
there,
so
I
had
0.25
credits
in
here
prior
and
so
what
you're?
Seeing
now
is
the
amount
incremented
from
that
so
yeah,
that's
that's
an
overview
of
the
bridge.
H
Any
questions
on
this
and
I
will
say,
of
course,
like
if
you're,
then
looking
on
your
Eco
credits
portfolio,
any
assets
that
are
under
the
tco2
credit
class
will
also
in
your
actions,
have
the
ability
to
put
them
into
the
NCT
basket.
So
you
can
do
that
and
when
you
do
that,
then
you'll
actually
see
that
balance
increment
as
a
basket
token,
and
you
would
like
no
longer
have
the
actual
granular
Eco
credit
assets
and
these
NCT
assets
are
the
ones
that
you
would
be
able
to
view.
Also
in
your
Kepler
wallet.
H
H
J
E
Absolutely
so
after
you
basket
your
NCT
tokens,
just
like
Corey
was
showing
us
how
to
do
on
Friday.
Presumably,
you
will
be
able
to
go
on
to
osmosis
and
be
able
to
implement
those
NCT
tokens
in
the,
in
the
same
way
that
you
would
import
regen
or
atoms
into
osmosis
and
be
able
to
trade
them
on
the
newly
instantiated
pool
on
osmosis
proposal.
E
Will
be
established
on
osmosis
and
r
d.
Ink
is
matching
that
liquidity
there,
so
they'll
be
pretty
deep
liquidity
and
then
osmo
NCT
pool
will
be
started
with
very
little
liquidity,
but
it'll
have
incentives
associated
with
it,
so
people
will
start
bringing
ncts
over
buying
them
off
of
the
regen
NCT
pool
and
bring
them
over
to
NCT
osmo
pool
and
staking
them
there
for,
for
incentives,
so
should
be
pretty
exciting
over
the
next
starting
on
Friday
to
see
what
happens
in
those
pools,
love
everyone
to
participate.