►
From YouTube: Cosmos Stargate & IBC Launch
Description
Inter-Blockchain Communication (IBC) has launched with the Cosmos Stargate upgrade on February 18th at 7AM UTC. This is exciting news for the Agoric economy, which is built on Agoric’s Layer-1 chain and connected to Cosmos zones and other networks like Ethereum via the same IBC protocol.
For developers leveraging Agoric’s fast building environment, the launch of IBC is one of many powerful tools to use in your lending dapp, automated market maker, or project of choice. Here’s to building the future of DeFI 🍻
B
B
B
Yeah,
of
course,
this
is
going
to
be
like
a
fun
session,
so
don't
use
that
guys
too
to
jump
in.
So
what
we
wanted
to
do
with
this
website
is
make
sure
that
ibc
has
its
own
brand
because
it
deserves
it.
Ibc
is
what
we
consider
the
standard
for
industrial
blockchain
communication.
It
has
been
in
the
works
again
for
two
years
and
yeah.
This
this
website
is
going
to
basically
enable
you
to
get
all
the
information
you
need
about.
B
Ibc
some
document
documentation
answer
some
faq
questions
and
more
and
of
course
this
is
just
the
version
one.
We
have
like
other
versions
in
the
works
with
more
information
and
more
content,
but
we
really
wanted
to
have
something
to
to
show
you
for
this
network
upgrade
so
on.
If
you
navigate
to
the
homepage,
you'll
get
some
useful
information
about
ibc
and
then
some
news
so
pretty
exciting
stuff
happening
in
the
cosmos
ecosystem.
You
you're
invited
to
check
it
out
as
we're
going
to
to
to
explain.
B
B
So
these
are
basically
the
canonical
reference.
If
you
want
to
delve
more
into
ibc,
then
you'll
be
able
to
see
the
status
of
different
ibc
implementations.
Obviously
we
have
like
for
the
only
the
cosmos.
Sdk
implementation
is
ready
to
be
deployed
in
production,
but
many
other
people
and
organizations
are
working
on
other
implementations
of
ibc,
for
example,
like
the
substrate
abc
for
the
polkadot
ecosystem.
We
also
have
like
a
rest
implementation
and
I'm
sure
many
more
are
coming
the
red
layers
are.
B
B
So
the
next
level
of
an
application
is
to
send
transfer,
transfer
tokens
between
one
chain
and
another,
but
like
I
can,
I
can
tell
you
that,
like
many
many
more
interesting
ibc
applications
are
being
developed
right
now
and
will
be
developed
in
the
future,
and
then
we
have
some
cosmos
sdk
guides.
So
if
you
want
to
add
ibc
to
your
sdk
blockchain
or
build
an
ibc
application
specifically
for
the
cosmos
sdk,
you
will
find
useful
links
to
do
so
here
and
then
we
have
the
faq.
B
B
B
A
I
am
all
right
now
we
are
here
and
billy
will
join
us
to
here,
eventually
as
well,
but
in
the
meantime
I
asked
in
chat
how
many
people
know
what
ibc
is
right
and
I
keep
you
know.
We've
got
the
technical
stuff.
You
know
with
all
these
teams
that
have
been
building
awesome.
Awesome
things
welcome,
billy,
hello,
how's,
it
going
everybody
good.
D
D
The
the
topic
of
this
call
is
ibc
overview
and
the
future
of
the
interchange
we've
got
chris
groves
from
entertainment,
gmbh
and
sean
breithwaite
from
informal,
and
we've
got
dean
tribble
from
mcgorrick.
Here,
you
guys
are
all
involved
with
ibc
at
various
levels.
I
think
probably
chris
you're,
the
most
associated
with
the
protocol
you've
been
working
on
the
spec
for
for
quite
some
time.
When
did
you?
D
E
That's
right,
that's
right!
I,
when
I
interviewed
for
tendermint
at
that
point,
I
was
not
in
berlin.
I
was
in
the
united
states
only
interviews
for
phone
calls
and
the
third
interview
was
with
ethan
buckman,
who
I
think
is
currently
busy
testing
the
stargate
upgrade.
So
he
may
not
be
here
at
the
moment,
but
that's
because
he's
doing
more
important
things
and
when
we
sort
of
negotiated
at
the
end
he
said
well,
it
seems
like
a
good
fit.
You
seem
interested,
you
know
what
would
you
like
to
do?
E
D
So
you
were
working
a
lot
with
with
dean
during
that
that
time,
when
you
actually
did
get
your
shift
to
working
on
the
ivc
spec,
what
was
how
did
that
relationship
begin?
Where
dean
were
you
involved
from
day?
One
is
this
something
that
people
ask
you
to
get
involved
with?
Is
it
something
that
you
were
proactively
getting
involved
with?
What
was
that?
What
was
the
beginning
of
that
relationship
with
you
in
ibc,
like.
A
So,
as
zucky
tells
me,
it
tells
us
you
know,
we
were
involved
since
before
day,
one,
which
is
to
say
you
know,
we've
been
doing
distributed,
system
stuff,
myself,
marcum
a
few
others
here
at
cork
for
a
long
time,
and
they
were
looking
for
solutions
to
some
problems
and
stumbled
upon.
Some
of
you
know
some
of
the
sites
that
talk
about
our
work
back
from
you
know
the
90s
or
the
2000s
or
whatever.
I
think
it
was
and
went.
A
You
know
problems
they've
they've
thought
about
these,
so
we
can
focus
on
getting
a
chain
out
and
then
come
back
and
solve
these
set
of
problems
and
and-
and
we
were
working
on
starting
to
work
on
the
gork
chain
where
we
were
building
our
interchange
distributed
protocol
stuff
and
we
met
at
there
was
a
powwow
at.
I
think,
the
first
of
interchange,
conversations
in
berlin.
E
A
E
E
E
A
Ibc
had
already
you
know,
they
thought,
through
a
bunch
of
these
best
practices,
of
how
to
have
one
chain
figure
out
whether
it
could
believe
another
and
how
to
set
it
up
securely
and
how
to
do
the
validation
of
the
likelihood
all
these
things
that
you
know
they
were
not
in
in
in
our
picture
and
so
putting
those
two
together.
You
know
the
ibc
is
really
a
successful
merging
of
those
two
streams
of
development
in
a
way
that
that
you
know
that
really
did
bring
us
the
best
of
both
worlds.
I'm
really
excited.
D
C
It's
been
interesting
to
play
catch-up
for
the
past
year
and
a
half
where
most
of
the
design
was
done
in
this.
Like
two-year
sprint,
I
think
they
spent
35
hours
in
the
same
room
as
each
other
during
the
conversation,
so
like
everyone
smelled
the
same
at
the
same
point
and
out
of
that
came
sort
of
like
this
tribal
domain,
now
oh
yeah,
the
light
client
and
like
backward
verification
right
and
all
these,
these
things
that
have
very
complicated
implications
which
are
never
discussed
because
everything
that
was
like
inside
the
room
took
place.
C
Talking
about
it's
well
understood
as
well
the
real
air-
we
all
know
how
that
works
right.
So
it
was
this
really
fun
process
of
working
with
with
dean
and
and
grace,
and
most
importantly,
anka
zempfier,
who
who
couldn't
make
it
today,
but
is
probably
the
best
representation
of
of
informal's
contribution
to
to
ibc
so
working
working
with
her
trying
to
bring
it.
Let's
say
to
like
production
great
from
from
from
rough
idea
on
on
a
whiteboard
in
berlin
and
marker
that
will
never
be
removed.
C
So
in
some
ways
it's
permanent
right
in
other
ways,
it's
completely
ephemeral
and
and
trying
to
to
to
make
it
real.
So
I
think
we've
made
good
progress
there.
Ibc
is
ready,
it's
been
running,
I
guess
what
we
could
call
a
stability,
but
it
is
really
just
just
just
really
the
start,
we're
really
at
almost
like
a
new
day,
zero
and
now
and-
and
we
anticipate
that
what
will
come
next
will
probably
be
nothing
like.
A
So
tomorrow
is
the
interchange
which
we
just
didn't
have
yesterday
and
that's
that
that's
really
a
sea
chain.
You
know
a
year
ago,
you
know
people
would
kind
of
go,
yeah
interact
will
be
interesting
someday
and
now
we
just
saw
lots
of
demos
of
things
that
that
just
like
yep
once
I'm
connected,
I
can
do
all
this
awesome
stuff
right
and
so
there's
this
pent-up
demand
that
suddenly
you
know
we're
going
to,
you
know,
drop
the
crystal
in
and
boom
it
all
it.
It
all
takes
off
so
very
excited
about
this.
D
So
early
on,
when
cosmos
white
paper
is
being
written-
and
you
know
this
idea
of
internet
of
blockchains
seemed
possible,
but
the
actual
implementation
or
how
we're
going
to
get
there
was
still
unclear.
I
think
you
know
the
the
minimum
bar
was
like
we'll
figure
out
token
transfers,
maybe
we'll
figure
out
arbitrary
data,
and
then
you
know
through
the
process
it
seemed
like.
Actually,
this
is
really
possible
to
be
really
flexible.
We
can
actually
do
so
so
much
I'd
be
curious
like
when
or
if
it
was.
D
Maybe
it
was
that
that
session
at
berlin
hackathon,
where,
where
you,
where
the
spec
transition
from
like
at
a
minimum,
be
able
to
do
this
to
like
oh
my
gosh,
we
can
do
this
full,
huge
and
exciting
range
of
things,
and
we
can
actually
do
it.
It's
not
like
a
hope
anymore.
I
see
the
past
was
that
was
that
that's
a
good
question.
D
E
You
know
credit
where
credit
is
due.
The
original
impetus
for
ibc
came
from
the,
of
course,
cosmos
white
paper
written
by
jane
becky,
and
I
even
believe
that,
according
to
some
conversations
I
had
with
jay,
there
were
even
earlier
conversations
jay
had
with
some
awesome
guy
in
noisebridge
san
francisco
that
a
day
to
think
of
some
of
the
initial
concepts
for
ivc,
so
the
ideological
genealogy
is
quite
deep
here.
E
E
The
people
involved
in
the
design
of
ibc,
such
as
myself,
have
an
aesthetic
preference
for
protocols
which
solve
all
the
possible
problems
that
is
possible
to
solve
for
the
particular
cost
of
protocol
at
once,
which
is
only
true,
because
we
are
very
lazy
and
I
don't
want
to
write
something
twice.
So
if
we
can
only
write
something
once
and
then
like
lots
of
people
can
implement
it
and
it
will
solve
many
problems.
That's
nice.
I
really
think
that
design
session
35
hours
is,
I
mean
it
wasn't
quite
35
hours,
but.
E
A
Forgotten
the
other
big
transition
period
was
the
the
review
right.
The
that
you
know
so
chris
did
has
done
an
awesome
job
driving
the
standard
right
and
then
we
you
know,
and
then
we
had
to
review
it,
and
it
was
one
of
those
things.
This
is
one
of
those
things
where
okay,
it's
going
to
take
a
couple
days
to
review
it,
just
like
no,
no,
it's
not
going
to
take
a
couple
days
to
review
it.
A
That
was
one
where
it
sort
of
started
like
right.
This
isn't
going
to
work.
We
trotted
out
a
review
process.
We'd
use
for
specification
documents
in
previous.
You
know
in
in
in
previous
lives,
at
edigoric
and
and
the
whole
gang
went
through
this
process
of
of
of
capturing
all
the
comments
and
then
capturing
responses
with
them
and
revisiting
and
making
sure
that
we
agreed
with
the
results
of
the
responses
and
applying
the
changes
you
know,
and
so
that's
where,
like
that's,
where
I
first
got
to
really.
A
You
know,
work
with
anka,
for
example
the
the
that
shawn
mentioned,
and
she
you
know,
and
just
the
different
people
that
came
in
with
thoughtful
comments
about
how
this
stuff
would
work.
That
gets
like.
Oh
that's
what
they
were
thinking
or
that's
what
they
needed
or
there's
a
problem,
that's
niggling
at
them
and
then-
and
it
finally
crystallized
here
stuff
like
that.
So
so
the
transition
from
you
know
coming
together
with
a
coherent
design
that
we
thought
could
do
all
of
these
things
to
reviewing
an
actual
design
going
yeah
yeah.
A
E
We
had
a
really
just
fantastic
collaboration
with
the
formal,
with
all
the
people
at
formal
who
are
looking
over
the
spec
thinking
about
it
from
the
perspective
of
tenement.
From
the
perspective
of
outsiders,
who
you
know
are
not
going
to
make
the
same
mistakes
that
we
made
since
we
wrote
this
back
and
then
implemented
it.
That
kind
of
reality
check
was
absolutely
necessary.
C
Yeah,
it
was
great
to
sort
of
have
our
our
team
really
dig
into
it,
and
actually,
even
though
there
were
some
some
issues,
there
was
a
shocking
few,
considering
how
how
deep,
when
how
thorough
and
how
let's
say
unproven
it
was
at
the
time
it
seemed
like,
like
99.99
of
of
the
stuff
was,
was
where
it
needed
to
be.
It
also
gave
us
an
opportunity
to
start.
You
know
expanding
the
field
of
human
capital
working
on
the
spec.
You
know
like
maybe
it's
maybe
so
far
it's
it's.
C
It's
been
people,
mostly
mostly
on
this,
in
the
chat
or
or
even
on
this
call,
but
the
next
generation
of
ibc,
when
it
really
does
become
the
internet,
is
going
to
be
a
far
larger
group
of
of
contributors.
So
it
was
the
first
step
in
sort
of
devoting
ourselves
to
the
community
like
expanding
the
range
of
human
capital
that
that
can
be
productive
in
in
ibc.
D
Sean,
I
remember
I
mean
you
were
maybe
the
first
one
of
the
first
users
who
really
like
onboarded
ibc
once
it
was
kind
of
at
a
finished
state.
I
mean
I
imagine
that
this
was
sort
of
in
parallel
with
the
informal
with
the
the
audit
and
maybe
there's
some
changes
but,
like
I
remember
you
know
seeing
you
in
the
office
one
day
and
you
were,
you
know,
also
still
relatively
new
to
rust.
I
think
this
came
with
the
idea
of
building
ibc
and
rust
and
it
felt
a
little
bit.
D
C
I
I
think
the
first
moment
that
I
had
that
you
saw
my
eyes,
as
I
sort
of
like,
was
able
to
like
do
the
chain
of
trust
that
this
actual
thing
is
is
like
secure
or
whatever,
because
we
talk
about
it
in
terms
of
like
channels
and
and
packets
and
all
these
constructions.
But
these
constructions
actually
serve
a
purpose.
C
You
know
to
so
like
amortize
verification
costs
or,
or
or
whatever,
and
and
being
able
to
to
understand
that
took
a
little
while
a
little
while-
and
I
think
you
know
goatee's
effort,
you
know
to
sort
of
provide
a
new
representation
of
what
ivc
is
beyond
just
like
you
know,
specification
is,
is
going
to
be
absolutely
critical
to
to
to
to
its
success.
So
for
for
me
you
know
I
I
really
had
to
let's
say
not
go
easy
on
chris,
and
he
was
of
course,
incredibly
generous
spending.
C
Spending
spending
time
with
doesn't
it's
always
been
been
generous,
but
obviously
we
need
that
that
process
to
scale
we
need
more
people
who
have
that
sort
of
neil
neil
moment.
So,
as
the
the
spec
right
now
is,
is
quite
a
quite
a
technical
document
but
informal
we're
quite
committed
to
sort
of
stewarding
the
specification
to
a
much
larger
audience,
and
that
means
not
just
having
you
know
a
a
technical
doc
for
people
that
have
been
working
on
it
for
a
year.
C
But
having
sort
of
an
english
version
that
sort
of
onboards
new
users.
It
also
involves
making
the
spec
not
just
something
to
be
read
by
and
understood
by
people,
but
something
to
be
understood
by
computers.
So
all
of
it
is
going
to
be
specked
in
tla
and
provides
sort
of
the
developer.
Experience
that
we
anticipate
is
one
that
people
building
on
ibc
will
get
sort
of
test
vectors
for
free.
C
So
essentially,
as
you
implement
your
your
your
extension
or
or
your
version
or
implementation
or
whatever,
you
could
sort
of
assert
conformance
with
the
specification
pretty
much
from
from
day
zero
and
sort
of
lining
that
up
with
with
the
onboarding
story
is
is,
is
what
we,
we
really
believe
is
going
to
drive
a
sort
of
cambrian
explosion
of
use.
Cases
for
ibc.
D
Yeah,
I
saw
a
demo
yesterday
from
starboard
team
at
tinderman
and
I
don't
know
if
this
is
meant
to
be
public
yet,
but
it
thought
it
was
really
exciting.
They've
basically
set
up
a
command.
So
if
you're
familiar
with
the
star
port
command
line
tool,
it
helps
scaffold,
custom,
sdk
chains
and
there's
a
command
to
sort
of
build
up
a
basic
chain
and
there's
a
command
to
instantiate
a
new
module.
And
then
you
can
start
adding
things
to
those
new
modules
similar
to
sort
of
scaffolding,
tools
that
are
available
for
ruby
on
rails.
D
So
you
will
add
a
type
and
that
type
you
know
gives
you
create.
Read:
update,
delete
sort
of
functionality
of
that
type.
Well,
they
have
a
new
command
for
building
a
module
which
is
ibc
ready,
so
it
imports
all
of
the
base
constructions
for
an
ibc
module
and
instead
of
putting
the
logic
inside
of
like
the
handler
to
handle
a
message,
you
start
putting
the
logic
and
the
on
received
sort
of
method
of
the
actual
sort
of
ibc
protocol.
D
So
it's
it's
a
scaffold
for
brand
new
ibc
modules,
and
I
was
immediately
like,
oh
my
god.
This
is
going
to
be
chaos,
we're
going
to
have
tons
of
new
ibc
modules
before
the
ics
specs
for
all
these
application
layers.
Sort
of
get
built
out
is
this
good?
Is
this
bad
and
then
it
made
me
also
think
about
interchange
accounts
and
how
kind
of
the
point
of
interchange
accounts
is
to
give
a
one
common
interface
for
for
any
message
type
to
come
through?
A
So
well
go
ahead,
go
ahead,
chris,
take
it
away,
okay,
so
a
fundamental
element
of
the
design
of
ibc
is
these
separate
layers?
I
I
will
chris
goes
referred
to
as
the
tao
of
of
ibc
right,
the
transport
authentication
and
and
ordering
that's
most
of
the
spec,
and
it's
because
that
was
done
right
and
based
in
everything.
We
need
that
we
can
build
application
layer,
protocols
easily,
and
so
the
interchain
accounts
is
an
application
level.
Protocol
transfer
is
an
application
level
protocol.
There
will
be
nft
transfer.
A
The
power
of
ibc
is
partly
we
can
get
connected.
We
can,
you
know
it
seems
to
integrate
into
all
these
other
chains,
but
every
zone
that
stargate
enabled
is
sort
of
ready
to
knock
ibc,
but
I
believe
there
will
be
a
lot
of
application
protocols
that
people
will
build.
Not,
ideally
you
know,
ideally
not
very,
very
customized,
but
the
same
way
there's
a
lot
of
ip
protocols.
Tcp
protocols
that
people
build.
You
know
some
of
them
are
great.
A
You
know
send
a
json
blob
across
and
you
can
do
that
over
ibc,
but
but
a
lot
of
them
are
very
structured
in
order
to
serve
some
application
purpose,
but
it
can
be
used
by
multiple
parties.
Right
they'll,
be
you
know,
messaging
social
messaging
protocols,
and
you
know
article
news,
distribution,
protocols
and
stuff
like
that,
where
the
more
reusable
they
are,
the
better,
but
there's
no
reason
to
just
have
it
be.
You
know
some
very
unstructured
things.
E
First,
I'm
thrilled
that
there
are
the
wonderful
thing
and
magical
thing
about
working
on
a
protocol
which
has
a
spec
and
then
becomes
slowly
disseminated
across
the
wider
ecosystem
of
idc,
neophytes
or
obviously
neo
moments
is
that
things
start
happening
involving
this
protocol.
You
wrote
that
have
completely
outside
your
control.
You
know
I
go
to
sleep
in
berlin
and
I
wake
up-
and
now
I
hear
about
this
like
magical
way
to
launch
new
ibc
modules,
which.
E
E
Unless
you
do
it,
you
know
I
wish
the
ibc
spec
would
just
magically
fix
itself
at
night
when
I
went
to
sleep
and
I
wouldn't
have
to
go
think
about
it
again
in
the
morning,
but
for
a
long
time
that
definitely
didn't
happen,
but
now
we're
at
the
stage
where
you
know
I
stay
up
too
late
and
get
too
little
sleep
before
coming
to
this
call,
but
then
wake
up
and
all
of
this
has
magically
occurred.
I
mean
I.
A
E
That
there
will
be
plenty
of
reasons
to
experiment
with
application
modules
before
writing.
Specs
you,
you
can
start
using
ibc
in
a
very
you
know,
sort
of
low
value
or
prototype
friendly
context
in
some
kind
of
test
net
or
pseudo
test
net
zone.
There's
probably
a
lot
of
space
on
the
spectrum
between
test
and
mainnet,
where
these
kinds
of
things
could
be
played
around
with
and
then
standards
can
emerge
and
be
agreed
upon.
Once.