►
From YouTube: The Dynamic IBC Experience
Description
Learn about how the proposed IBC standard provides the foundation for a new token economy, permitting anyone around the world to accomplish quick and secure exchanges.
A
All
right,
well
I'm,
very
excited
I
hope.
All
your
sessions
were
amazing.
I
hope
that
you
did
some
networking
I
hope
you're
having
fun
to
keep
moving.
Today.
Our
next
session
is
going
to
be
the
dynamic
IVC
experience
here.
You're
going
to
learn
about
how
the
proposed
IBC
standard
provides
a
foundation
for
a
new
token
economy,
permitting
anyone
around
the
world
to
accomplish
quick
and
secure
exchanges.
This
talk
is
going
to
be
led
by
Jack.
A
Jack
is
from
cosmos,
he's
a
product,
strategist
and
developer
relations,
adviser
to
several
approved
for
stake,
blockchains,
and
then
we're
also
going
to
have
Dean
Tribble
Dean
Tribble
is
from
a
gorrik
he's
a
CEO.
There
he's
also
co.design
and
negotiated
the
process
and
contract
for
the
first
smart
contracting
platform,
a
mix
excited
and
to
have
both
of
these
guys
coming
up
and
I
hope.
You
guys,
you
know,
are
excited
as
well:
who's
ready.
A
B
B
C
Then
Dean
just
one
note
as
we
go
throughout
this
presentation:
if
anyone
has
questions,
please
drop
them
in
the
chat.
I
will
be
answering.
Questions.
Dean
and
I
will
also
be
doing
a
breakout
session
afterwards
to
dive
in
any
of
these
topics
in
more
detail.
If
you
have
more
questions,
so
we
would
like
this
demo
to
be
a
little
bit
interactive
and
really
help
you
guys
understand
what
we're
doing
here.
So
please
just
ask
those
and
I
will
try
to
get
through
those
quickly.
B
Okay,
so
so
I
asked
the
question
about
smart
contracts
for
a
simple
reason.
You
know:
I
work
on
the
first
production,
smart
contract
back
in
1989,
which
is
sometime
after
the
the
foundations
of
the
internet
and
five
years
before
batalik
was
born
just
to
put
it
in
context
and
and
what
what
and-
and
this
was
a
smart
contract
system
that
predates
the
coining
of
the
term,
where,
where
nick
szabo
identified
a
bunch
of
the
ideas,
he
was
developing
his
own
thoughts
about
what
smart
contracts
were
and
could
look
backwards
at
it
and
go
yep.
B
That
was
the
first
production
smart
contract
and
he
put
all
the
ideas
together
and
realized
that
hey
that
thing
that
people
were
doing
there,
that's
worth
doing
moral.
That's
something
that's
going
to
be
powerful.
So
what
do
we
mean
by
that?
It
is
a
contract
like
arrangement
expressed
in
software,
expressed
in
code,
where
the
behavior
of
that
code
enforces
the
terms
of
the
contract,
so
that
means
Bitcoin
is,
of
course,
a
smart
contract.
You
can't
change
what
it
is,
but
the
execution
of
Bitcoin
is
actually
oh.
C
B
No
I
can
turn
on
my
screen
here
in
just
a
while.
The
jokes
deep,
like
with
my
hands
it's
worth
having
in
all
right
so
so
Bitcoin
is,
of
course,
a
smart
contract,
but
an
aetherium
was
the
first
platform
to
be
able
to
do
smart
contracts
that
are
provided
by
the
users,
but
all
of
these
ideas
predate
blockchain,
so
eBay
PayPal
venmo
much
Airbnb
much
of
Amazon.
B
All
of
these
systems,
where
there
is
a
trusted
third
party,
are
also
smart
contract
systems,
and
so
that's
why,
when
I
asked
have
you
used
one
before
now,
everyone
should
go
back
and
think.
Ok,
let's
take
that
poll
again
and
see
whether
the
number
is
different,
because
smart
contracts
are
upwards
of
a
trillion
dollar
market
cap
even
before
we
get
to
blotching
and
then
what,
if
block
chains
add
to
this
well
wood
block
chains.
Add,
is
they
add
multiple
independent
computers?
B
Is
the
gold
standard
right
in
multiple
different
administrative
zones,
so
no
one's
in
charge
and
in
multiple
different
jurisdictions?
So
no
government
can
compromise
it
voting
to
agree
on
data
like
I
wanted
to
pay.
You
know
Alice
wanted
to
pay.
Bob
order
of
events
did
Alice
pay
Bob
before
Alice
paid
Carol
and
the
results
of
computation.
You
know,
Alice
is
a
smart
contract.
He
did
some
execution.
B
Did
the
execution
work
the
same
on
a
hundred
different
machines
in
a
hundred
different
countries
in
a
hundred
different
data
centers,
and
the
big
result
of
that
is
we
get
computing
with
integrity?
We
now
know
that
there's
no
single
party
that
can
compromise
the
data.
Historically,
that
can
compromise
the
execution
of
a
contract
which
now
means
that
smart
contract
model
I
can
pull
that
trusted.
B
Third
party
out
of
the
middle
right,
I
no
longer
need
venmo
to
host
and
orchestrate
my
payments
with
a
total
stranger
in
some
location
that
I'm
unaware
of
I
no
longer
need
Airbnb.
To
take
a
big
chunk
of
my
negotiation,
to
use
someone's
house
in
some
low
in
some
distant
location
and
so
any
example
of
block
chains
that
are
not
leveraging.
B
So
remember
this
whole
idea
of
smart
contracting
predates
blockchain,
so
as
cryptographic,
protocols
between
machines,
right
and
so
Amisha,
a
blockchain
is
just
a
machine
built
out
of
agreement
rather
than
silicon
right.
So
ethereal
is
a
machine
with
about
the
power
of
an
old
cell
phone,
and
that's
going
up
and
with
v2
it'll,
be
much
more
than
that,
but
it
has
vastly
higher
integrity.
B
It
incorporates
that
into
an
abstraction
which
we'll
get
into
in
just
a
moment
in
just
let
me
go
to
more
levels
above
that
and
then
skip
into
a
little
bit
more
into
that.
So
above
these
layers,
the
low
level
execution
and
communication,
you
know
the
TCP
and
packet
sending
we
have
a
computational
model.
You
know,
EVM,
you've
got
solidity
on
top
of
it.
Cosmos
you've
got
you've,
got
modules
built
in
go
in
Agoura.
You
have
JavaScript
programs
that
are
just
deployed
as
as
contracts
and
in
our
system
that
allows
us
to
have.
B
You
can
see
an
object.
All
these
tiny
little
script
objects
with
a
remote
reference
to
an
object
on
another
machine
and
it
can
send
messages
to
those
objects
on
another
machine
and
get
a
response
back,
and
we
end
up
with
a
nice
uniform
fabric
of
distributed
computation
that
can
incorporate
that
you
have
the
same
abstract
model
spans
across
multiple
languages
and
across
multiple
chains
and
then,
finally,
above
that
and
I'm
not
going
to
go
into
it.
Very
much
is
our
contract
layer
with
a
set
of
abstractions
in
work.
B
But
our
focus
today
is
on
the
low-level
communications.
So
I
will
skip
past
that
and
we
will
talk
about
IDC.
So
at
the
bottom
layer
you
know
now
this
sort
of
reversed.
There
is
what
what
Chris
goes
coined
the
term
the
towel,
we
transport,
authentication
and
ordering
layer-
and
that
looks
a
lot
like
TCP
in
the
normal
internet
internet
protocols
and
in
some
of
our
presentations.
B
We
go
into
details
on
that,
but
for
an
important
thing
to
understand
about
the
details
at
that
layer
is
just
like
most
programmers
don't
need
to
know
the
guts
of
how
TCP
works
with
packet,
timeouts
and
IP
and
headers
and
and
routings
and
all
those
kinds
of
things
they're.
Just
millions
of
programmers
that
use
TCP
all
over
the
you
know,
TCP
everywhere,
without
understanding
those
details,
sometimes
we'll
go
into
those
details,
but
mostly
from
a
programmer
point
of
view.
B
What
you
want
is
everything
above
that,
so
the
towel
layer
of
IBC
is
well
documented
in
the
standard
and
that's
the
place
where
you
know
Chris
knows
and
sucky
and
Ethan,
and
you
know
all
the
game
working
on
the
design
of
IVC
have
incorporated
best
practices
from
a
lot
of
the
people
out
there
and
implemented
that
into
the
spec.
And
then
there
are
multiple
implementations,
I'm
starting
with
ones
on
cosmos,
but
hey.
There
are
other
people
out
there.
B
There
are
people
working
on
a
rust
part
of
it,
working
on
integration,
with
polka
dot,
working
on
the
etherium
bridge.
Anyone
out
there
who's
working
on
one
of
these
platforms
put
in
the
chat,
the
the
platform
that
you
guys
are
working
on.
Okay,
so
so,
just
to
let
people
know
that
these
other
projects
are
happening
out
there.
Ok
and
then
above
that
layer.
B
That
looks
like
TCP
that
I
had
down
to
the
bottom,
and
my
thing
is
the
app
protocol
layer
and
that's
where
everyone
that's
where
most
of
the
programming
is
going
to
happen
in
the
world.
That's
where
most
of
the
innovation
happens,
where
by
abstracting
out
those
best
practices
of
how
to
let
two
chains
verify
each
other's
life,
client
and
route
packets
across
and
all
that
sort
of
thing.
B
We
end
up
letting
people
escape
away
from
that
in
the
same
way
that
they
don't
have
to
deal
with
low-level
packets
on
TCP
and
they
can
focus
on
their
application
behavior.
So
the
IBC
standard
rolls
out
with
one
particular
application
protocol
transfer
for
doing
asset
transfer,
fungible
and
non
punchable
token
transfer,
but
you
know
there's
obviously
an
echo
packet
and
that
sort
of
thing.
B
But
the
main
thing
is
the
next
generation
of
app
protocols
that
you
know
I
and
Jack,
and
all
you
people
out
there
are
going
to
build,
for
you
know
having
one
chain,
the
dustproof
of
location,
be
able
to
bring
location
over
to
a
different
chain
so
that
an
Oracle
chain
that
that's
got
a
nice
summary
of
their
Oracle
computation
and
abstraction
can
bring
those
assets
over
to
a
zone
that
doesn't
have
a
bunch
of
Oracle's
so
that
you
know
fancy
new
computation
on
a
book
that
odd
a
pair
of
chain.
Sorry,
yes,
that's
that's!
B
When
I
whack
and
normally
I
have
a
space
seen
behind
me.
So
that's
just
my
shift
taking
damage,
but
even
so
so
so
I
can
have
applications
on
on
pair
of
chains
able
to
bridge
over
to
a
cosmos
zone
and
pull
those
assets
over
and
compute
with
them
and
the
cosmos
zone
and
so
forth.
So,
let's
so
having
said
that,
let
me
now
give
you
some
encouragement,
all
right:
here's
where
our
demo
comes
in.
So
let
me
pop
out
of
here
so
I'm
going
to
show
a
small
demo.
B
This
is
like
hello
world,
but
hello
world
isn't
encouraging
enough
right,
so
I'm
going
to
show
my
little
encouragement
dab.
This
was
our
main
developer
on
our
contract.
Rain
Brigade
cells,
just
wasn't
satisfied
with
hello,
world
and
and
and
we
totally
bought
in
it's
very
very
simple.
It
is
you
know,
I.
Just
click
encourage
me
for
free
and
I,
get
a
pop-up
saying,
I'm
doing
great,
all
right,
lovely
right,
so
I
feel
now
encouraged.
I
feel
warmed
by
all
of
this.
B
Hopefully
you
all
you
all
pay
for
that
now
what's
happening,
there
is
I've,
got
a
browser
talking
to
a
web
application.
So
just
as
if
this
was
a
Eunice
whopper,
you
know
so
so.
I've
got
here.
It's
local
local
host
here
so
I'm
running
in
local
development
mode,
but
that's
as
if
that
was
you
know,
you
know
swap
exchange
or
some
web
application.
This
is
my
cheesy
web
front-end
right
and
it
talks
to
the
web
application
on
the
server.
And
yes,
yes,
I
love
my
I'm.
B
B
B
B
B
Right
here
we
jump
into
the
into
our
into
our
simple
little
wallet.
This
one
I
will
shrink
a
tiny
bit
and
I.
Just
not
an
offer
to
you
know
in
my
wall
am
I
willing
to
spend
one
moolah
from
my
account
in
order
to
get
some
encouragement
and
I
say
yes,
that
goes
back
to
the
change.
This
is
now
on
chain,
doing
the
money
transfer
and
it
says,
wow
I
have
never
seen
such
talents.
Okay,
I
am
clearly
way
over
the
top
and
now
I
feel
really
good
about
this.
B
Okay,
so
I'm
gonna
do
one
more
thing
and
then
we'll
get
to
Jack's
part
of
the
demo
here.
So
this
was
a
simple
application
right.
What
does
it
take
to
take
this
simple
contract
which
is
up
on
our
website
or
up
on
github
and
very
straightforward
and
I'm
not
going
to
go
into
the
into
the
guts
of
it
but
I'm
going
to
show
what
it
takes
to
add
IVC
to
it?
So
here
this
is
just
JavaScript.
I
will
make
this
one
two
little
larger.
B
This
is
just
JavaScript
where,
in
the
setup
of
this
I
have
an
IP
seaport
that
came
in
at
the
top,
where
I
got
as
part
of
starting
my
contract.
I
should
add
one
thing
in
a
John
in
this
JavaScript
architecture.
In
our
Zoe
contract
framework,
a
smart
contract
is
just
a
JavaScript
module
that
exports
a
make
contract
function.
That
will
return
a
particular
set
of
things
and-
and
you
know,
there's
other
presentations
that
will
go
into
that
I'm.
Just
gonna
show
you
the
extensions
so.
C
B
That's
right:
yes,
someone
asked
us
for
JavaScript.
You
know
they
were
asking
is
what
are
we
doing
about
a
development
environment
to
which
I
said
well,
given
that
you
know
Microsoft
has
thousands
of
people
in
up
spent
and
has
spent
you
know
millions
of
dollars,
building
a
development
environment
to
the
JavaScript.
We're
done.
We
didn't
do
anything
anyway,
so
this
is
just
a
delta
and
github.
Where
now,
for
this
IBC
port
I,
say,
add
a
listener
for
new
connections
right.
B
B
If
this
was
a
bid,
I
could
be
collecting
offers
and
then,
when
a
timer
kicks
over
I,
then
close
the
auction
and
say
who
the
winner
is
all
that
kind
of
thing.
But
this
is
just
a
very
simple
hello
world
kind
of
content,
and
so
this
is
all
it
takes
to
be
able
to
do
this
thing
so
now,
let
me
jump
in
and
I
should
see
how
I'm
doing
on
time
occasion.
So
let
me
go
back
to
here
and
I
will
grab
my
little
sample
code
here.
You
can
see
what.
C
B
Okay,
so
in
that
first
user's
repple,
so
alice
is
port
8000,
so
I've
got
two
chains
in
development
mode
running
on
this
very
machine.
Obviously
these
would
be
to
public
chains
when
this
was
all
deployed,
but
I've
got
a
repple
here
that
just
lets
me
do
JavaScript,
okay,
the
github
link.
Yes,
we
will
certainly
give
you
the
github
link
at
the
end
and
so
on.
B
So
I
have
here
is
I'm
going
to
do
a
connection
locally
as
this
user
on
this
chain,
and
you
can
see
that
I
go
to
my
IBC
port
I
connect
to
a
court
and
on
receive
I'm
like
I'm,
just
going
to
output
to
the
console.
Here's
what
I
got
back
from
that
chain
right.
So
let
me
copy
that
paste
it
here
in
my
repple.
It
goes
out
to
the
chain
it
now
is
going
to
going
through
my
repple
as
my
user
and
saying
hey
for
my
host
objects.
B
B
Yeah
well,
alright,
okay,
so
so
jack
is
do
clearly
doing
better
than
me.
Alright.
So,
let's
now
get
to
Jack's
part
of
this
thing.
This
was
only
on
one
chain:
right,
I,
the
user.
That
has
an
account
on
this
gene,
so
Jane
using
IBC
connection
and
the
same
API,
just
locally
connected
to
talk
to
that
to
that
smart
contract
that
is
deployed
on
the
chain.
But
let's
now
do
something:
fancier
I'm
going
to
go
over
to
Bob
on
chain
8001,
which
is
the
second
chain
okay.
B
B
I'm
going
to
do
this
and
it
goes
BAM,
there's
a
whole
bunch
of
information,
alright.
So
what
happened
here?
A
key
element
in
IBC
architecture,
as
we
said,
is
best
practices
for
moving
data
back
and
forth
where
each
chain
is
able
to
execute
the
life
client
for
the
counterparty
chain
for
the
opposing
chain.
So
here
chain,
one
is
able
to
verify
the
headers
and
the
IABC
information
directly
of
packets
presented
from
chain
zero
and
vice
versa.
But
how
do
they
get
back
and
forth?
B
The
key
ingredient
is,
is
the
is
the
is
the
the
the
relay.
So
let
me
just
show
one
picture
here
and
then
we'll
go
over
and
show
how
that
actually
happens
where
we
had
chain
one
on
the
chain,
one
on
the
right,
where
I
did
my
original
application?
I
talked
to
the
contract
directly
and
now
what
we're
showing
is
chain
two
where
I
did
in
my
repple
is
the
user.
B
I
said:
hey
I
want
to
connect
to
that
contract
running
over
there
and
ask
it
for
some
encouragement,
and
so
now
all
of
this
work,
all
of
the
layers
of
ibc,
have
to
happen
underneath.
But
these
layers
here
that
all
happens
because
there's
a
separate
process
of
a
relief
relayer,
that's
going
to
do
the
shuttling
and
so
jack
is
going
to
go
in
and
talk
how
that
all
works
as
we
look
at
the
config
for
that
process.
So.
C
The
relayer
is
just
this
very
important
role
in
IBC.
That
really
falls
into
the
background
very
quickly
and
we're
gonna
kind
of
see
that
in
this
demo,
but
the
core
problem
here
is
that
one
sort
of
machine
made
out
of
agreement
steam
very
eloquently
put
it
earlier
in
this
talk,
can't
really
send
HTTP
requests
upon
its
own.
You
know,
there's
a
number
of
problems
with
blockchain
sending
HTTP
requests
that
we
can
gonna.
C
Do
it
another
talk,
but
there
needs
to
be
some
sort
of
actor
performing
the
transactions
on
behalf
of
users
and
the
relayer
is
this
sort
of
automated
piece
that
looks
on
the
two
chains
that
are
involved
in
an
IBC
transaction
and
moves
any
data
between
them.
That
needs
to
be
done
so
obviously
for
configuration.
A
relayer
needs
data
about
how
to
reach
an
RPC
end
point
which
chains
it's
being
connected
to
a
little
bit
of
information
about
the
wallet
formats
and
like
client
formats
that
it
needs.
C
The
relayer
has
local
versions
of
the
light
client
for
each
chaining
that
it
keeps
up-to-date,
and
that
is
how
it
proves
the
data
coming
from
all
the
chains,
and
it
also
submits
proofs
to
one
chain
or
the
other,
to
allow
the
chains
to
prove
that
the
data
coming
in
is
real.
So
that's
what
this
configuration
is
here
and
then
dump
it
back
bottom.
You
also
see
this
path
configuration
which
gain
is
setting
up
here,
and
this
is
the
series
of
IBC
primitives
that
you
want
to
relay
over.
C
So
the
major
IBC
primitives
that
we
have
here
are
clients.
The
client
is
an
on
chain
commitment
to
a
light
client
from
another
team.
So
this
is
what
the
chain
uses
to
prove
various
data
that
it's
receiving,
so
those
clients
are
periodically
updated
through
the
process
of
IBC
transactions
and
you'll,
see
that
in
this
demo
the
next
one
is
a
connection
and
the
connection
is
sort
of
the
actually
is
not
where
a
connection
is
authentication.
C
How
are
we
going
to
talk
to
each
other,
and
this
is
different
packet
formats,
different
IVC
applications
we're
going
to
see
an
example,
sort
of
switching
and
dynamically
creating
a
new
application
protocol
here
and
the
relator
sort
of
helps
set.
All
of
that
up
so
with
that
I
know,
folks
probably
will
have
more
questions.
Please
drop
them
in
the
chat
and
I
think
the
breakout
session
I'm
happy
to
cover
the
reason.
The
relay
are
in
great
deal
more
detail,
because
this
is
kinda
what
I've
been
working
on
for
a
while
eeen.
B
Great,
so
I
will
so
this
relayer
was
built
by
occlusion
and
jack
here
in
particular.
So
when
we
have
a
session
afterwards,
we
can
dig
deep
into
how
it
works.
I
should
note
that
I
started
the
to
change
your
run.
You're
talking
about
locally
using
the
relay
I
could
of
course
start
them
using
our
infrastructure,
but
by
plugging
into
that
that
tool
the
jet
built
to
be
able
to
create
these,
it
makes
it
very
easy
to
test
and
deploy
and
iterate,
which
is
an
important
element
of
game
game
of
zones.
B
C
Just
to
note
the
relayer
repo,
you
know,
the
real
layer
is
a
role
within
this
protocol.
We
anticipate
seeing
a
lot
of
different
implementations
of
real
layers.
You
know
it's
very
easy
to
build
a
JavaScript
relayer,
where
an
individual
browser
session
would
establish
like
clients
between
two
chains
and
be
able
to
accommodate
transactions
on
behalf
of
a
user.
So
there's
a
lot
of
different
ways
to
build
this
and
I
tried
to
make
this
repos,
basically
a
tools
for
working
with
IBC
and
trying
to
help
understand
the
protocol.
B
So
this
thing
can't
proceed
without
a
relayer.
I
will
go
ahead,
but
of
course,
I
have
a
promise
for
the
connection
over
here.
I'm
gonna
start
the
relay.
You
can
see
it's
creating
the
client,
it's
open
to
connection
it's
acting
back
and
forth.
You
can
see
the
messages
from
IBC,
0
and
IBC
1.
Those
are
the
names
of
the
two
chains
on
either
side.
It
is
connecting
over
those
channels
and.
B
It
is
now
I,
don't
know
you
establishing
the
channel
is
delivering
the
messages,
and
you
can
see
that
this
promise
here
for
a
connection
at
the
other
end
result.
Okay,
so
now
going
back
to
my
remember,
I'm,
on
I'm
on
I'm
in
a
repple
on
chain
to
set
up
with
now
a
connection
to
the
the
encouragement
DAP
on
chain.
One
so
I
should
now
be
able
to
say
send
of
hello,
jack.
B
And
oh,
and
that
will
send
you
can
see
it's
now
sending
packets
delivering
messages.
You
see
messages
on
either
chain
the
chat,
the
you
know
and
I
should
scroll
down
here,
help
if
I
scroll
down,
so
you
could
see
that
indeed
it
got
the
act
back
from
the
sand
which
came
back
over
IBC
and
the
message
sent
from
the
client
from
the
smart
contract
all
there.
On
the
other
end
saying,
wow
I
have
never
seen
such
talent,
of
course,
and
if
I
send
the
same
thing
to
Dean,
you
will
see
that.
B
B
B
Jason
do
you
know
Jason
decoder,
you
know
you
can
have
a
at
packets
that
are
fine
in
in
protobuf
and
so
forth
and
be
able
to
issue
commands
from
in
this
case,
a
ripple,
but
I
can
perfectly
I'll
have
a
smart
contract
on
this
chain
that
is
issuing
those
requests
to
a
smart
contract
on
the
other
chain.
Well,
let's
talk
about
what
the
dynamic
part
is,
because
this
you
could
already
do.
B
It
would
just
me,
have
to
install
these
these
modules
in
cosmos
or
install
these
elements
in
whatever
is
and
deploy
the
chain
that
has
these,
but
if
I
go
back
and
I
look
at
my
example
here,
let
me,
let
me
know,
fill
this
relayer
for
a
moment.
Go
back
and
look
at
my
example.
Contract
here
in
my
example,
contract
right
I
have
that
on
receive
that.
B
Let
me
not
change
that
where,
if
the
message
coming
in
has
the
message
attack
in
it,
then
I'm
going
to
return
naughty
naughty
instead
of
AK
and
I'm,
not
gonna,
send
back
and
encouragement
right,
so
I'm,
just
gonna
save
this
and
I'm
gonna
go
down
here
and
I'm
going
to
redeploy
this
contract,
and
so
now
what
this
is
doing
is
this
is
has
the
owner
of
the
application
of
the
encouragement
application.
I
am
updating
my
contract,
so
I
connect
to
my
website.
It
connects
over
and
deploys
the
new
version
of
the
contract.
B
This
is
configures
configures.
It
locally
then
deploys
to
the
cloud
where
the
cloud
here
is,
of
course,
this
local
machine
at
the
moment,
but
this
configure
to
go
to
other
clouds.
It
deploys
to
the
cloud
the
web
application
side
of
it,
so
if
I
change
either
the
contract
or
the
web
application,
they'll
all
get
deployed
and
now
I'm
running
a
new
version
of
this
contract,
and
this
is
as
I
had
mentioned.
B
Yes,
as
Michel
thing
pipe
in
this
is
just
vs
code
right,
as
I
said
earlier,
you
know,
since,
since
our
smart
contracts
are
built
in
JavaScript,
it
just
runs
under
vs
code
or
webstorm
or
Emacs
or
whatever
your
favorite
environment
is
VI.
Take
your
pick,
ok!
So
now
having
done
that,
I'm
gonna
go
back
over
to
Bob,
so
I'm
now
on
the
second
chain.
B
Remember
the
the
smart
contract
was
deployed
on
the
first
chain
and
I'm
gonna
go
ahead
and
make
a
new
connection
so
I'm,
just
gonna
I'm,
just
going
up
arrow
and
re
running
that
same
invocation
to
get
a
new
connection.
Now.
The
important
thing
here
is
this
goes
back
to
the.
There
will
be
multiple
relays
here.
The
relayer
that
I
clusion
is
built
is
a
channel
focused
relayer
for
doing
specific
things
in
enabled
in
game
of
zones.
B
There
will
be
fancier
ones
that
just
set
up
a
connection
set
up
the
client
and
it
just
relays
everything,
including
these
open
connection.
Requests
in
this
case
I
actually
need
to
update
the
the
the
that
configuration
specifically
so
I'm
going
to
go
ahead
and
go
to
the
config
and
change
the
channel
ID
that
I
want
it
to
relay,
because
it'll
only
relay
one
channel
of
time.
So.
C
Just
to
know
you
need
to
do
this
because
you've
deployed
this
more
contract
to
a
new
address
and
we're
sort
of,
like
you
can
think
of
the
ibc
connection,
is
connecting
these
two
smart
contracts
directly,
because
there's
a
new
one.
We
need
to
change
the
connection
between
the
correct
mmhmm
right
and.
B
So
and
I
can
have
both
of
these
channels
up
and
running
simultaneously.
Obviously,
once
we
have
the
thing
that
relays
all
channels,
we
on
a
connection
between
two
chains,
where
the
chains
need
to
install
the
light
clients
for
the
opposing
chains,
but
the
chain
doesn't
need
to
trust
anything.
That's
going
across
that
it's
just
the
end
point,
so
the
channels
that
are
receiving
messages
that
might
care
what's
on
the
other
side.
So
having
done
this,
I
will
now
go
back
to
my
relayer
and
start
up
the
relay.
B
And
now
it's
established,
so
I
can
go
ahead
and,
as
I
said
before,
I
will
of
course
send
hello
to
I'm
gonna,
say
hello
to
Sookie,
who
I
think
is
in
the
audience
right
and
Sookie
has
been.
You
know
one
of
the
champions
for
IBC
across
all
these
things.
Now
I
should
note
so
obviously
Wow
yes,
never
seen
such
talents.
Obviously
now
since
I
mean
I'm
going
to
hello,
I'm
attacking
Jack
right.
B
Sends
the
message
across
it
goes
into
the
smart
contract
and,
as
you
saw,
instead
of
sending
an
encouragement
back,
it
comes
back
with
naughty-naughty
having
detected
the
the
this
packet
that
was
obviously
evil.
Now
the
important
thing
is:
that
is
that
you
know
so.
What
happened
here
is
I've
got
IBC
running
it's
running
between
multiple
chains.
It's
already
enabled
on
multiple
zones
out
there
that
are
setting
out
to
attack
each
other.
There
are
projects
that
are
implementing
implementing
IBC
for
lots
of
other
different
consensus,
algorithms
and
infrastructures.
B
So
the
goal
of
Cosmos
Eric
Knox
right,
the
goal
of
IBC
is
not
cosmos,
focused
the
goal
of
IBC
the
goal
of
agora.
With
respect
to
this,
the
goal
of
Jack
and
Zaki
and
Ethan
and
everyone
else
working
on
this
project
and
Chris
goes,
you
know,
Michael
I
mean
there's
a
whole
litany
of
these
folks
that
are
working
on
this
is
to
get
this
is
to
enable
this
interoperability
across
multiple
different
ecosystems.
Across
you
know,
every
you
know,
we've
got
we've
got,
we
want,
tells
us.
B
B
The
big
thing
that
happens
that
that
we
just
showed
here,
is
not
just
static
connections
with
established
careful
pegging
relationships,
but
ad
hoc
updates
to
application
protocols
that
I
was
able
to
deploy
and
design
in
a
permissionless
fashion
on
an
existing
running
chain
right
and
be
able
to
dynamically
update
it
on
the
fly
of
be
able
to
assuming
whatever
governance.
My
smart
contract
is
under,
to
be
able
to
deploy,
updates
to
the
contract,
to
deploy,
updates
to
a
protocol
to
fix
things
in
flight
and
and
so
forth.
B
Now,
in
the
current
game
of
zones
that
recent
that
just
got
started
is
now
in
progress.
There
are
hundreds
of
hundred
plus
teams
working
to
connect
with
each
other
and,
of
course,
working
to
corrupt
each
other,
because
this
is
a
beautiful.
After
all,
an
adversarial
test
met
in
the
environment
being
able
to
rapidly
iterate
is
very
important,
but
even
after
that,
as
we're
developing
new
block
chains,
new
zones,
new
new
contracts
on
etherium,
new
pair
of
chains
and
etc.
B
Being
able
to
deploy
them
and
instantly
deploy
a
counterparty
in
an
Agora
chain
and
a
causal
Azzam
chain
and
in
the
theory
of
chain
that,
once
once
they
have
similar
support
for
for
dynamic
IBC
will
be
crucial
for
not
just
easy
Interop
but
rapid
innovation
in
the
space,
and
that's
something
that
I
think
we're
all
very
excited
about.
So
thank
you
very
much
for
your
thoughts.
Sometimes
any
things
you
want
to
add
to
that.
Jack
know.
C
That
this
is
a
this
is
a
great
way
to
sort
of
wrap.
This
up
here,
I
believe,
were
to
be
doing
a
breakout
as
well
after
this.
For
folks
who
want
more
detail
on
this
topic,
please
drop
by
we'll
bring
them
onstage
answer.
Questions
I
can
do
a
more
thoroughgoing
description
of
the
relayer,
which
I
think
some
folks
on
this
call
might
find
interesting,
especially
to
dig
in
some
of
those
IBC
internals,
which
I
know
were
very
exciting.
C
You
know
here
at
cosmos,
were
extremely
excited
about
the
virtual
machine
environments.
Coming
live
on
top
of
the
platform
here
soon
nagura
is
the
one
that
I'm
most
excited
about.
You
know
the
ability
to
code
in
JavaScript,
which
is
by
far
the
most
supported
and
easy-to-use
language
out.
There
I
think
it's
going
to
be
huge
for
the
huge
for
the
whole
community,
not
to
mention
the
fact
that
IBC's
deeply
integrated
the
system,
and
you
guys
have
fun
deeply
about
how
to
work
with
IBC
in
between
differents
for
contracts.
C
It
had
been
involved
in
the
design
from
the
beginning,
so
yeah,
that's
what
I
would
have
to
say
there.
Anyone
trying
to
build
all
the
other
fire
levers
above
IBC
like
the
session
layer
and
application
layer,
etc
about
three
DVR
UI.
So
as
far
as
the
application
layer,
we
do
have
a
specification
for
different
application
protocols
and
what
Dean
was
actually
demoing
here.
Virtual
rendezvous
is
the
creation
of
a
new
application.
The
whole
protocol,
when
he
was
sending
across
the
channel,
was
different
versions
of
that
application.
C
For
her
call
so
right
now
we
only
have
one
standard
protocol,
and
that
is
the
token
transfer
protocol.
There's
a
full
write-up
on
that
on
the
cosmos.
Ics
repo
I
will
drop
a
link
to
that,
but
as
far
as
a
session
layer
in
some
other
stuff
there's
a
lot
of
exciting
work
to
be
done
on
top
I
know
Dean
and
the
Agora
to
none
so
I'm
thinking
on
the
session
layer,
but
there's
obviously
some
more
work
to
be
done
there
and
as
far
as
you
eyes,
you
know
there's
only
some
very
basic.
C
B
Dad
so
so
session
layer
in
some
said
corresponds
to
channels
where,
that's
you
know,
a
TCP
TCP
connection
would
correspond
to
an
IBC
channel
here
or
RPC
connection
would
correspond
to
an
IBC
Channel
here,
as
Jack
mentioned
right.
These
protocols
here,
where
I'm
sending
I'm
in
the
encouragement,
DAP
and
knack
and
naughty-naughty.
B
Think
of
that
as
my
having
done
an
ad
hoc
protocol
here,
but
indeed
the
real
thing
here.
Would
you
know
on
receive
tape
these
bytes
and
Jason
decoded
and
the
the
trance
respect
is
defined
as
a
particular
format
of
Jason
future
specs
would
then
take
these
bytes
and
protobuf
decode
them
into
a
protobuf
to
find
a
api.
You
know
back
and
forth,
and
so
this
is
the
layer
which
you
can
define
new
app
protocols
and
just
implement
them
in
JavaScript
wrapped.
You
know
in
our
framework
and
wrap
them
with
various
things.
B
There's
the
meta
UI
stuff
that
the
jack
is
talking
about
where
there's
already
explorers.
There's
the
lots
of
command-line
examples
that
Jack
can
go
into
in
the
relayer
for
being
able
to
dump
logs
and
see
the
state
of
connections
that
sort
of
thing,
but
one
of
the
things
we'll
get
out
of
game
of
zones
is
fancy
and
fancy
or
metadata.
What's
the
connected
graph
of
chains
connected
with
ibc,
but
really
the
the
UI
layer
in
that
you
know
I,
so
stack
of
layers
where
you
know
the
political
layer
is
layer,
8
or
whatever
it
is.
B
You
know.
That's
you
know
you
know
that's.
This
is,
in
some
sense
a
toy,
a
layer
right.
It's
an
example
of
a
web
application
of
a
UI
in
a
browser
talking
to
a
web
app.
It
could
perfectly
well
be
mobile
talking
to
a
web
app
server
talking
to
the
chain.
That's
the
standard.
Api
I
stack
using
standard
libraries
with
standard
API
frameworks
and
so
forth
that
all
composes,
together
with
this
in
this
in
this
stack
that
I
was
showing
on
the
right
well,
yeah.
C
I
mean
dear
what
I,
what
I
would
say
to
agree
with
you
here.
It
is
like
this
is
really
a
full
stack
demo.
I
mean
this
is
the
sort
of
entertained
future
that
a
lot
of
folks
in
the
space
have
been
working
for
for
a
long
time,
some
truly
independent
projects
with
very
different
management
structures,
very
different
groups
of
folks
working
on
them
connecting
together
and
really
building
this
world,
where
we
don't
have
to
rely
on
exchanges
to
be
the
interoperability
layer
between
different
block
chains
and
just
transfer
data
between
them.
C
One
of
the
questions
that
we
had
in
the
chat
was
from
Bowen
Wang
Jackie
said
that
store
contracts
are
listening
for
incoming
messages.
How
does
that
work
under
the
hood
and
how
does
it
get
triggered
on
these
foreign
contracts?
Ibm?
That's
a
great
question
and
essentially
an
IBC
there's.
This
thing
called
a
port
ID
and
you
can
think
of
a
port
ID
very
similar
to
the
way
a
port
works
in
UNIX.
C
So,
according
UNIX,
when
you
start
listening
to
it
with
a
process,
any
data
that's
forwarded
to
that
port
will
get
forward
to
directly
to
that
process
via
a
standard
method
and
IBC
is
very,
very
similar.
Once
you
hook
up
this
IBC
connection
to
a
port
on
a
given
blockchain,
the
specification
says
that
politically
are
not
currently
implement.
C
This
specification
says
that
those
application
bytes
to
travel
over
that
chain
need
to
be
delivered
to
the
process
or
smart
contract
listening
on
that
port.
So
in
this
case
it's
our
encouragement
for
our
contractors.
Listening
on
the
port,
the
protocol
sets
up
all
of
these
definitions,
and
you
know
if
you're
looking
to
sort
of
learn
a
little
bit
more
about
it.
I
think
looking
through
the
relayer
and
trying
to
understand
it.
That
way
is
very
important.
I
do
like
the
idea
of
outsourcing
the
political
layer
to
Devon
all
sounds.
B
C
B
That's
where
I
was
showing
you
in
this
code.
Sorry
in
the
code
here
this
IBC
port
object
is
a
no
cap
for
being
able
to
listen
on
that
particular
port
that
was
configured
there,
that
that
happened
to
have.
You
know
this
name
in
the
config
file.
So
there
is
a
connection
between
them,
but
we
haven't
done
the
security
review
to
make
sure
that
it
is
in
fact
you
know
one-to-one
semantics.
But
but
you
know
all
the
basics
are
all
there.
Yeah.
C
C
B
This,
let
me
know
so
our
focus
is
public.
Blockchain
and
work
will
be
doing
a
a
public
blockchain,
for
you
know
millions
of
JavaScript
developers
to
be
able
to
build
smart
contracts
in
JavaScript,
but
the
JavaScript
implementation
that
we
intend
to
use
working
with
the
model
folk
moddable
builds
the
excess
JavaScript
implementation,
which
is
a
standards
compliant
JavaScript
implementations
that
runs
inside
of
lightbulbs
and
washing
machines
and
and
and
and
and
other
kinds
of
devices.
So
it's
very
small
memory
footprint
and
that's
what
we'll
be
using
in
our
chain
engine
right
now.
B
This
one
is
using
node,
which
works
just
fine,
but
having
a
smaller
machine
makes
it
more
memory,
footprint,
say
easier
to
verify
easier
to
ensure
secure
that
sort
of
stuff
and
so
being
able
to
have
that
whole
engine
and
parts
of
it
run
indeed
inside
of
IOT
devices,
totally
something
that
that
that
we
expect
to
have
happen
in
the
future,
whether
we
do
it
or
someone
else
does.
But,
but
you
know,
the
stack
is
all
open
source.
B
C
B
There
is
a
also
we
had
a
meet
up
with
after
the
last
JavaScript
Standards
Committee
right,
we
mark
millar,
and
it
has
been
on
the
job
search,
Standards
Committee,
for
what
13
years
I've
been
on
it
for
a
couple
of
chip,
Morningstar
has
been
there
for
several
years,
etc,
driving
the
security
elements
into
JavaScript,
so
that
we
can
achieve
this
secure
version
of
JavaScript.
That
lets
us
do
this,
but
there
was
a.
There
was
a
wonderful
meet-up
where
you
know
we
showed
the
secure
JavaScript
environments.
B
Really
awesome
and
yeah.
Yes,
the
aguar
chain
is
the
second
chain
that
metamath
supports
payments
were
because
we
use
their
that
javascript
extension
method
mechanism,
but
the
third
one
was
moddable,
demonstrating
javascript
inside
of
a
light,
bulb
and
demonstrating
how
important
it
is
to
be
able
to
download
secure
components
into
your
light
bulb
so
that
a
programmable
light
bulb
that
lets.
B
You
do
awesome
light
shows
can't,
for
example,
the
rate
that
causes
epileptic,
fits
or
or
flash
of
the
rate
that
causes
the
light
bulbs
to
burst
into
flame,
which
it
turns
out,
has
been
actual
problems
in
real
light
bulbs.
The
people
have
deployed
so
so
having
the
secure
extensibility
of
the
same
kind
of
framework,
you
need
for
smart
contracts.
Same
thing,
you
need
for
wallet,
extensions,
same
thing.
You
need
for
devices
one.
C
B
C
B
Whatever
our
protocol
from
the
chain
to
the
individual,
app
server
will
be
IBC.
Obviously,
between
chains
will
be
IBC
and
eventually
from
the
app
server
to
the
to
the
light
client
running
in
the
browser
or
running
in
the
mobile
device
that
can
all
be
over
IBC
IBC
is
is
not
heavyweight.
It's
really
defined
to
capture
the
best
practices
for
how
to
do
efficient
chain.
You
know
counter
party
validation
without
having
a
trusted
intermediary,
so
we
leverage
lots
of
prior
work
work.
That's
prior
to
us,
certainly
prior
to
cosmos
and
work.
B
C
B
C
Soon
we
will
be
relaying
things
out
of
order,
and
in
that
case
it's
going
to
depend
on
the
individual
relay
or
implementation.
The
relay
er
implementation
that
I've
been
working
on
just
sort
of
tries
to
provide
a
basic
example
for
folks
now
some
people
are
going
to
want
to
only
relay
packets
from
wallets.
They
control
understandable,
but
well
as
far
as
front-running
work
work,
the
ordered
packets
at
the
application,
the
unordered
channels
at
the
application
layer.
C
You
would
have
to
take
care
of
those
types
of
attacks,
and
you
know
we
have
a
lot
of
support
for
things,
like
sequence,
numbers
on
both
chains
and
there's
a
lot
of
checks
for
all
of
that
stuff,
so
pretty
easy
to
enforce
those
type
of
things
at
the
protocol
level.
The
relayer
is
really
meant
to
be
this
untrusted
piece.
That's
just
shuffling
data
in
back
and
forth
will
soon
be
deleting
things
out
of
order
in
general
in
life
and
absolutely
thank
you.
B
Well,
the
key
things
about
the
design
of
IBC
is
that
the
relayer
is
not
trusted
right.
All
it
does
is
it
takes
a
it
takes
the
the
headers
and
the
IBC
and
potentially
the
IBC
data
from
the
chain
on
one
side
and
presents
them
properly
to
the
chain.
On
the
other
side,
the
counterparty
chain
verifies
the
light
client
proof
where
the
the
slightly
reduced
proof
necessary
in
order
to
verify
that.
Indeed,
the
first
thing
sent
this
message,
so
it
is
not
trusting.
The
real
Ayers
claim
that
the
first
chain
sent
the
message.
B
C
So
it's
in
ER,
it's
an
interoperability
bridge,
not
just
a
real
layer.
I
think
that's
a
much
better
way
to
think
of
it,
and
you
know
the
relayer
is
just
the
the
actor
in
actor
within
this
system
is
a
real
layer
in
some
ways
you
need
to
just
be
able
to
communicate
with
multiple
chains
in
order
to
fulfill
this,
but
it's
meant
to
be
an
easy
enough
to
satisfy
role
where
there's
multiple
different
modalities
of
how
users
can
interact
with
us.
Yeah.
B
That's
a
real
name,
real
sense
in
which,
just
again
back
to
the
TCP
sort
of
analogy,
it's
just
the
router
in
the
middle.
It's
you
know
it's,
it's
you,
you
gotta
have
one,
but
it
doesn't
opine
on
your
packets,
so
it
could
hold
up
messages
it
dislikes,
but
if
that's
an
in
order
to
stream,
that'll
be
detectable
and
any
other
relayer
can
come
along
and
the
packets
that
the
other
relayer
wasn't
saying
and
that'll
show
up
in
the
light
client
you
know
and
the
again
the
the
changes
the
either
end
don't
care.
B
C
A
great
discussion
topic
that
we
can
just
move
right
into
from
here
is
Bowen
asks
if
you
don't
mind,
asking
bit
more
about
IBC
without
reading
the
spec
first.
Can
you
give
an
overview
of
the
economics
of
IBC
like
how
real
layers
are
paid
and
what's
the
cost
of
using
IBC
on
zones,
but
within
IBC
each
of
the
zones
is
sovereign
and
each
of
the
chains
has
their
own
rules.
You
know
whether
you're
going
over
to
aetherium
or
finance
chain
or
over
to
the
cosmos
SDK
or
over
the
Agora
chain.
C
Each
of
those
chains
will
have
their
own
way,
that
they
handle
fees
and
because
you
have
to
submit
transactions
to
each
of
those
chains,
you're
going
to
end
up
having
to
pay
fees
on
each
of
those
chains.
As
for
the
relayer,
you
know
we
mentioned
that.
There's
multiple
different
ways
that
you
can
do
real
ayres
as
an
individual
user.
You
can
relay
your
own
packets
and,
in
that
case,
you're
paying
for
them,
but
for
some
of
these
more
persistent
channels
and
links
between
chains
that
are
more
broadly
used
by
larger
numbers
of
folks.
C
We
anticipate
that
the
validators
who
are
validating
on
all
of
these
chains,
you
know
I
validate
on
a
few
different
cosmos
chains,
I'll
likely
be
validating
allegoric
as
well.
Those
validators
have
sufficient
economic
incentive
to
ensure
that
data
can
flow
between
those
chains
that
we
anticipate
a
lot
of
the
real
a
load
will
be
taken
up
by
the
validator
sets
at
first.
C
We
have
not
actually
built
relayer
in
cinemas
ation
into
the
protocol,
because
you
know
doing
cross
chain
fees
and
different
currencies
and
settlement
across
those
is
complicated,
very
very
complicated
and
I
think
would
have
delayed
the
launch
of
IBC
quite
a
bit.
So
we
basically
said:
there's
economic
actors
within
the
system
that
we
anticipate
will
say,
take
this
load
and
we
think
that
getting
an
earlier
version
of
the
protocol
out-
it's
good,
maybe
not
perfect-
is
better
than
sort
of
waiting
for
another
two
years
to
launch
this
thing.
B
Two
that
are
that
are
that
are
more
or
less
related.
The
first
one
is,
is
you
mention
that
their
sovereign
zones,
but
there
are
people
working
on
an
app
level
protocol
to
be
able
to
have
cross
zone
security
or
cross
chain
security?
So
being
able
to
you
know,
I
mean
the
polka
dot
folk
have
thought
a
lot
about
doing
shared
security
across
multiple
multiple
pair
of
chains.
Can
that
be
stretched
over
to
something
that
looks
like
a
cosmos
zone?
B
Can
I
take
security
on
you
know,
deployed
in
an
aetherium,
smart
contract
and
say
I'm
willing
to
stake
this
against
the
correct
execution
of
that
cosmos
zone
over
there
once
we
develop
a
protocols
that
allow
cross
that
allows
sticking
and
presenting
of
slashing
proofs
as
an
IBC
protocol,
now,
suddenly,
we've
got
much
richer
ability
to
do
decentralized,
shared
security
across
a
wide
variety
of
infrastructures
and
a
wide
variety
of
zones.
The
other
thing
I
wanted
to
add,
was
to
go
meta,
and
then
we
come
back
to
the
the
shared
security
stuff
comes
out
of.
B
There
is
a
git
coin.
There
is
a
hackathon
in
progress
right
now
corresponding
to
all
of
this.
That
started
a
couple
of
weeks
ago,
but
there
are
challenges
for
doing
IBC
and
DB
IBC
connection,
it's
primarily
sponsored
by
cosmos,
with
agaric
as
prizes
in
there
we're
a
co-sponsor
and
ban
protocol
were
banned
as
a
cosmos
zone
that
acts
as
an
oracle.
So
there
are
challenges
and
prizes
to
take
a
banned
Oracle
presenting
their
format,
which
is
their
own
apt
format,
taking
it
across
IBC
and
use
it
inside
of
a
JavaScript
contract
on
agaric.
B
Just
like
you
saw
me
using
the
app
the
encouragement
and
a
protocol
here
to
go
back
and
forth
so
that
hackathon
is
in
progress,
there's
still
plenty
of
time
to
swoop
in
and
build
interesting
stuff
and
take
prizes.
So
so
so
do
that
look
at
game
of
zones
and
then
pick
this
stuff
up
and
start
building
stuff
with
it.
B
Thank
you,
thought
China,
just
posted
the
link
off
to
those
prizes
for
for
the
Agora
prizes
again,
there's
also
big
cosmos,
prizes
and
hackathon
and
ban
protocol
prizes,
and
some
things
can
could
potentially
win.
All
three
is
because
you
know
that's
what
interoperative
out
is
the
synergy
of
these
things.
B
So
yes,
so
so
it
is,
you
know
the
spec
is
out
is
it
is
released,
there's
an
implementation
in
in
the
Kosmos
test
net
in
the
Agora
test
net
and
and
that's
what's
being
used
in
game
of
zones
there.
The
cosmos
is
in
the
process
of
converting
a
lot
of
things
to
use
protobuf,
which
is
which
is
resulting
in
higher
performance,
and
you
know
higher
throughput
on
on
several
different
avenues,
but
one
of
the
things
that
will
be
happening.
You
know
after
game
of
zones
completes.
B
B
And
other
projects
that
are
working
on
the
rough
side
of
things
to
be
able
to
talk
to
this
in
other
protocols,
you
know
hey
near
folk.
You
ought
to
be
able
to
now
start
building
it
into
near,
so
that
we
can
all
talk
to
near
because
I'd
love
to
you
know
be
able
to
have
our
assets
available
in
your
chain,
and
so
so.
This
is
one
of
those
things
where
you
know
by
the
end
of
the
year.
Having
multiple
chains
in
production
able
to
share
assets
across
is
really
what
I
want
to
see.
Yeah.
C
It's
a
it's
an
exciting
future
that
we've
been
building
to
for
a
long
time
and
one
of
the
most
exciting
things
for
me
throughout
this
process.
It's
like
seeing
the
software
take
shape
and
come
together,
and
you
know
that
moment
where
it
went
from
an
idea
to
actually
having
a
couple
of
chains
connected
was
really
really
cool,
and
you
know.
C
B
C
Think,
oh
right,
maybe
you
know
in
about
a
month
and
a
half
since,
since
we've
kind
of
reached
that
milestone
we've
gone
from,
like
oh,
my
gosh
like
can
we
get
this
connection
working?
Keep
it
alive
to
like
that's
just
kind
of
the
base
of
everything
else
that
we're
building
on
top
and
that
piece
of
it's
super
reliable.
Now
it's
very
cool
and
something
I've
encouraged
funds
to
check
out
so
I
will
again
drop
the
relay
or
repo
in
here
too,
for
anyone
who's
interested
in
trying
some
of
this
stuff
out
and.
C
Getting
a
phone
within
there
I
get
as
well
we're
in
the
process
of
building
a
light
client
for
posts
back
there.
Oh
and
one
thing
that
I
would
mention,
if
you
guys,
are
interested
in
rust,
like
clients
for
IBC
talking
to
the
informal
team
Bucky.
Who
is
this
leave
interference
in
ermine?
One
of
the
founders
of
Cosmos
is
running
up
there
in
Toronto.
They
have
a
lot
of
work
done
here
and
would
be
useful
to
integrate
with
on
that
they're
also
doing
some
relay
or
code
as
well.
Sweet.
B
Even
in
cases
or
even
in
cases
where
it
is
where
the
I,
what
you
need
for
IBC
is
not
quite
it's
not
quite
the
same
as
a
polite
client,
but
it's
it's
most
of
the
same
difficulty
so
so
and
hard
to
get
right,
something
that
requires
a
security
review,
something
that
everyone
should
pay
attention
to
something
where
we're
really
looking
to
people's
feedback
and
we're.
You
know
right
now,
it's
just
shakedown
IBC,
but
we
will
have
a
continuing
sequence
of
events.
B
I
think
with
what
you
know
Interop
days,
where
you
know
great,
you
know,
there's
IBC!
Now,
let's
get
you
know
everyone's
implementation
on
different
chains
and
a
game
of
instead
of
just
a
game
of
zones.
It's
a
game
of
chains.
We're
now,
can
they
you
know.
Can
the
near-light
client
crush
the
cosmos
like
clients,
so
11
right.
A
C
All
right,
we
will
be
doing
a
pop-up
Q&A
session
after
this
person
actually
has
drop
me
at
the
link.
Click
in
the
sessions
area
and
I
think
someone
I
will
try
to
drop.
A
link
in
here
afterwards
also
looks
like
Adrienne
challenges
revolving
away
when
one
protocols
will
be
up
next
I
worked
with
Adrienne
&
Kosmos
for
a
while
and
we've
been
doing
some
great
work
on
Tesla's
and
conference
governance
over
a
criterium
along
with
Chris
goes.
B
B
A
Really
really
appreciate
that,
and
you
know
super
technical
and
I'm
sure
a
lot
of
people
really
enjoyed
it.
So,
as
Jack
and
Dean
said
they
have
a
hackathon
going
on
right
now
make
sure
you
get
into
it
speaking
of
hackathons
Neer's
having
a
hackathon
at
the
end
of
this
event
and
tune
in
tomorrow
tomorrow
end
of
end
of
it-
and
you
will
definitely
get
more
information
about
that,
but
I'll
post
the
link,
so
you
can
start
getting
some
info
there.