►
From YouTube: Polkadot by Gautam Dhameja
Description
Berlin Ethereum Meetup 2019/06/18
Interoperability Edition
A
Hello:
everyone
good
evening,
thanks
for
coming
out
here
today,
so
I'm,
going
to
talk
about
polka
dot
in
the
context
of
interoperability
of
blockchains
and,
let's,
let's
basically
just
right
jump
right
into
it.
So
brief
about
me:
I'm
Gotham,
the
major
I'm,
a
Solutions
Architect
with
parity
technologies,
most
of
the
time
I'm,
helping
our
potential
customers,
enterprises,
blockchain
or
governments
or
startups
to
help
build
on
the
parity
stack
mostly
on
the
building
app
based
blockchains
and
how
to
connect
them
with
polka
dot
and
so
on.
A
So
that's
me
and
let's,
let's
go
into
the
polka
dot
side
of
things,
how
we
look
at
interoperability
and
how
we
actually
realize
that
we
want
something
like
this.
So
it's
going
to
be
something
in
continuation
to
what
Billy
just
mentioned
like
why
we
need
interoperability
and
based
what
what
has
brought
us
to
this
point.
So,
let's
look
at
what's
the
status
quo
at
the
moment.
A
First
of
all,
the
whole
categorization
and
building
of
these
APIs
blockchain
started
when
we
realize
that
one
framework,
one
platform
or
one
network,
will
not
be
able
to
provide
all
the
fundamental
characteristics
needed
for
all
kinds
of
block
chains.
We
are
everyday.
We
are
looking
at
these
different
block
chains
popping
up
around
the
ecosystem.
Some
some
of
them
are
providing
identity.
Some
of
them
are
providing
payments.
Some
of
them
are
providing
us
a
few
other
characteristics,
but
the
focus
has
now
been
moving
more
and
more
towards
one
single
use
case.
A
Do
it
and
do
it
better
and
do
it
best
basically-
and
it's
not
about
like
doing
everything
anymore.
So
that's
one
of
the
patterns
that
we
have
been
seeing
coming
up
a
lot
in
the
recent
developments
in
our
blockchain
ecosystem
and
that's
one
part
of
it.
Basically,
the
second
most
important
part
is
the
mass
adoption.
A
What
I,
personally,
also
believe
is
that
until
the
larger
enterprises
and
the
government's
don't
start
using
our
ecosystem,
our
technologies,
they
will
not
be
gaining
mass
adoption
in
the
near
future,
so
it
is
important
to
help
them
also
build
the
solutions
that
they
want
to
build
for
the
decentralized
space
and
most
of
the
time,
their
requirements
are
very
different
from
what
conventional
blockchains
will
will
look
like
so
a
lot
of
times.
They
need
some
level
of
permissioning
lot
of
times.
They
need
some
privacy
of
state,
arbitrary,
message-passing
and
so
on.
A
So
those
are
some
of
the
characteristics
which
are
specifically
needed
for
some
of
the
use
cases
and
not
the
current
frameworks
or
platforms
of
today.
Not
all
of
them
provide
this
in
a
more
in
a
fully
decent
lies
of
permissionless
way.
And
finally,
when
we
combine
the
last
two
arguments
that
I
just
presented,
that
there
are
several
chains
popping
up
every
day
and
then
there
are
different
requirements
from
the
enterprise
side
and
the
government
side
of
things.
We
are
looking
at
all
these
fragments
being
created
in
different
corners
of
the
world
like
today.
A
Again
there
was
this
announcement
of
the
Facebook
coin
chain
and
then,
a
few
weeks
ago
there
was
an
identity
to
chain
being
built
by
Microsoft
and
so
on.
So
we
are
again
looking
at
those
fragments
which
we
actually
wanted
to
not
have
when
we
were
starting
with
the
whole
blockchain
ecosystem.
We
wanted
a
connected
world.
We
wanted
a
more
decentralized
and
transparent
world,
and
now
again
we
are
looking
at
these
fragments.
So
how
do
we
basically
make
sure
that
we
are
bringing
these
things
together?
A
We
are
bringing
these
ecosystems
together,
so
that's
where
the
whole
need
for
interoperability
is,
is
realized
and
before
before
we
go
into
how
we
solve
that
problem
with
polka
dot.
Let's
also
look
at
what
exactly
is
needed
to
solve
the
problem
of
interoperability,
so
the
first
thing
is
a
common
platform
until
chains
or
networks
or
systems
are
not
able
to
talk
to
each
other
in
a
standardized
way,
they
will
not
talk
to
each
other.
A
Basically,
so
it's
as
simple
as
that,
if
I'm
able
to
communicate
things
to
you
today
in
English,
you
are
listening
to
me.
If
I
was
speaking
Hindi
back
from
India,
you
will
not
be
listening
to
me
most
of
you,
so
we
need
a
common
platform
to
talk
to
each
other
or
the
systems
need
a
common
platform
to
talk
to
each
other.
First
of
all,
and
hence
we
are
looking
at
something
like
an
infrastructure
for
the
infrastructure.
A
So
if
the
new
teams,
which
are
coming
up
with
their
own
app
based
blockchains,
they
are
creating
infrastructure
for
solving
a
use
case.
We
need
infrastructure
to
actually
enable
their
infrastructure
itself.
So
that's
the
first
need
where
we
are
looking
at
when
we
want
to
solve
the
problem
of
interoperability.
The
second
and
the
most
important
thing
is
trust,
of
course,
while
we
are
looking
at
a
lot
of
trust,
less
systems,
we
talk
about
environments
where
we
want
to
give
up
a
trust
and
look
at
immutability,
and
decentralization.
A
If
one
chain
has
a
state
that
can
be
reverted
or
there
are
Byzantine
actors
which
are
working
towards
making
this
chain
unstable,
then
the
other
chain
should
not
be
impacted
by
that.
Secondly,
the
most
important
point
is
the
security.
If
a
chain
is
feeling
basically
secured
with
by
connecting
to
a
network
by
exchanging
information
over
that
particular
infrastructure,
then
it
will
be
very,
very
helpful
for
these
chains
to
interoperate
with
each
other.
So
those
are
the
primary
two
needs.
When
we
are
trying
to
solve
the
problem
of
interoperability,
we
need
a
common
platform.
A
We
need
chains
to
be
able
to
talk
to
each
other
in
an
in
standardized
way
and,
secondly,
and
most
importantly,
they
should
be
able
to
trust
this
platform
which
they
are
using
to
talk
to
each
other.
So
that's
where
I
want
to
jump
now
into
the
polka-dot
side
of
things,
how
we
are
solving
these
two
problems,
how
we
are
bringing
a
common
framework,
a
common
platform
into
the
ecosystem
and
how
chains
are
allowed
or
enabled
to
trust
this
common
infrastructure.
So
let's
look
at
how
we
are
looking
at
the
interoperability
side
with
polka
dot.
A
So
when
it
comes
to
block
chains,
there
are
two
basic
things
that
we
are
looking
at
most
of
the
times.
It's
one
is
the
state
transition
that
there
are
these
transactions
coming
in
into
the
chain
and
they
are
taking
the
chain
from
one
state
to
the
next
state,
and
that's
basically,
depending
upon
use
case
to
use,
is
that
the
first
a
lot
among
chains
for
our
identity
related
chain.
This
could
be
a
creation
of
a
new
identity
or
an
update
of
a
new
identity
for
a
financial
settlements
chain.
A
It's
just
subtraction
and
addition
of
balances,
so
that's
very
different
from
chain
to
chain,
and
then
the
second
part
is
consensus
on
how
you
basically
agree
that
a
state
has
really
changed
or
not.
So
what
we
are
doing
with
polka
dot
is
allowing
both
of
these
side
of
block
chains,
the
state
transition
and
the
consensus
to
be
basically
connected
together.
Even
if
the
chains
are
doing
different
kind
of
state
transitions
for
their
different
use,
cases
underlying
infrastructure
allows
them
to
still
interoperate
with
each
other.
A
They
are,
they
are
required
to
do
a
lot
of
other
things,
apart
from
just
decentralization
and
keeping
the
state
immutable.
So
how
do
we
make
sure
that
we
connect
both
private
chains
and
public
chains
is
also
a
most
thing
that
polka-dot
helps
us
solve
so
high
level
and
10,000
feet
level
view
of
polka
dot
is
basically,
we
have
three
major
components
in
the
system:
the
relay
chain,
which
is
basically
the
the
central
infrastructure
of
polka
dot,
which
allows
other
chains
to
connect
and
talk
to
each
other.
A
Then
we
have
the
para
chains,
and
these
are
the
application
of
specific
chains
which
are
kind
of
being
built
using
the
same
framework
and
the
platform
so
that
they
can
communicate
with
each
other
if
they
are
not
following
the
same
practices.
If
they
are
not
following
the
same
standard
standards,
then
again,
there
is
a
problem
of
fragmentation.
So
this
is
how
we
are
basically
coming
up
with
this
whole
framework
for
building
para
chains
so
that
they
can
connect
to
the
polka
dot
relay
chain
and
talk
to
each
other
and
finally
bridges.
A
So
bridges
are
basically
allowing
existing
chains
which
are
not
built
using
the
para
chain
framework,
which
is
substrate
if
you
heard
about
it.
So
if,
if
your
chain
is
not
following
the
exact
the
consensus
and
the
N
is
not
connected
directly
to
the
polka
dot
network
using
a
slot,
then
they
can
still
be
connected
to
the
network
using
bridges.
A
How
this
looks
like
is
basically
something
like
this,
which
I
will
explain
in
detail,
so
the
core
middle
part,
which
you
see
as
a
dark
black
outline
in
the
middle,
that's
the
religion
and
those
white
things
inside
that
is
are
the
blocks
for
the
religion.
The
lines
that
you
see
in
between,
which
are
basically
like
kind
of
creating
the
web
are
interchange
passing.
So
that's
how
the
religion
is
helping
pass.
All
these
messages
from
one
chain
to
other.
A
The
next
layer,
basically
are
the
validators
for
the
religion,
so
they
are
making
sure
that
the
blocks
are
being
added
to
the
chains,
one
after
the
other,
and
they
are
taking
care
of
the
security
and
the
recentl
ization
of
the
religion
itself
and
the
third
layer
are
the
parrot
chains
themselves.
They
are
directly
connected
to
the
relation
and
submitting
their
blocks
to
validators
of
the
religion.
A
And
finally,
if
you
look
at
the
next
level,
those
are
the
second
level
relay
chains
and
the
bridge
chains
which
are
connecting
to
the
religion,
using
bridges
or
second
level
or
the
first
level
religion
itself.
So
this
is
how
basically
a
whole
ecosystem
based
on
polka-dot
looks
like
that
everything
is
fully
decentralized,
fully
permissionless,
but
it's
still
able
to
interact
and
interoperate
with
each
other
in
a
very,
very
standardized
way.
A
A
So
this
vaasam
allows
us
to
do
that
without
any
problem,
because
you
can
simply
upgrade
the
environment
on
wasum
and
still
the
native
environment
is
fully
functional
at
that
point
in
time.
So
that's
that's
the
second
most
important
aspect
and
a
third
finally
aspect
is
about
the
lip
p2p,
the
flexible
p2p
protocol,
which
is
like
designed
by
the
protocol
labs
team,
and
then
we
have
implemented
that
in
rust,
and
we
are
using
that
for
polka-dot
and
for
substrate
based
chains
as
well.
A
They
can
have
their
state
transition
function
as
as
they
want.
There
should
be
scalability.
The
whole
problem
of
the
major
major
problem
at
in
our
space
right
now
is
scalability
and
that's
again
how
we
solve
it
is
by
pooling
these
chains
together.
So
if
there
is
an
identity
chain-
and
if
there
is
a
payment
settlement
chain-
and
if
there
is
let's
say
a
supply
chain
blockchain-
then
they
are
actually
now
and
they
are
all
connected
to-
let's
say
the
polka
dot
relay
chain.
A
They
are
actually
not
doing
all
of
the
same
thing
together
in
one
chain
but
they're.
You
know
dividing
these
users.
If
somebody
needs
to
just
transfer
a
Bitcoin,
they
don't
have
to
really
do
or
not
Bitcoin
or
some
financial
coin.
They
don't
have
to
really
go
through
a
chain
which
is
doing
everything
which
is
also
having
transactions
of
supply
chain
or
having
transactions
of
identity.
They
are
just
interested
in
basically
getting
and
transferring
some
financial
value.
A
Similarly,
if
somebody
wants
to
authenticate
using
their
identity
system
or
if
they
want
to
create
an
identity,
self
sovereign
on
the
blockchain,
then
they
don't
have
to
worry
about
other
transactions
that
are
coming
from
the
financial
chain.
So
this
is
how
we
are
approaching.
The
problem
of
scalability
is
like
the
chains
will
have
their
own
use
cases
and
they
will
do
that
in
a
more
efficient
way
and
they
don't
have
to
worry
about
other
things,
which
generally
are
being
being
done
in
most
of
the
current
frameworks.
A
So
polka-dot
uses
this
pooled
or
shared
security
model,
where
the
validators
of
the
Pera
chain
are
basically
allowing
or
sorry
the
validators
of
the
relay
chain
are
swapped
and
they
allow
and
they
basically
allow
the
para
chains
to
add
blocks
to
the
relay
chain,
and
they
are
allowing
all
these
para
chains
which
are
connected
to
the
polka-dot
ecosystem
to
basically
be
secured
in
a
more
comprehensive
way
by
basically
interacting
with
each
other.
So
that's
how
the
pool
security
works
and
let's
look
into
where
we
are
with
the
polka
dot
development.
A
So
it's
it's
being
approached
in
a
very
similar
way
how
cerium
was
being
build
in
the
initial
stages
and
our
founder
Gavin
wood
is
also
he
was
also
the
first
co-ceo
of
aetherium,
and
so
we
are
following
the
exact
same
approach.
We
are
doing
a
bunch
of
pocs
tackling
one
problem
at
a
time,
so
we
have.
We
have
recently
done
the
these
some
of
these
pocs
and
the
next
ones
are
basically
coming
up
here.
A
B
A
So
the
way
it
works
is
basically
that
there
will
be
not
all
the
status
private
state,
it's
basically
a
subset
of
this
state,
which
needs
to
be
there
on
the
needs
to
be
looked
by
the
parties
which
are
interested
in
looking
into
that
and
which
are
authorized
to
look
into
that
or
to
be
done
with
that,
and
there
is
always
a
verification
that
there
is
a
state.
Change
has
happened
for
examples,
you
don't
always
proof
or
something
like
that.
B
A
C
A
Actually,
nothing
makes
me
sure,
but
it's
it's
more
like
when
the
patterns
that
we
have
seen
in
the
past
how
we
started
with
so
it's
it
goes
back
to
like
how
the
computing
has
evolved
in
the
last
few
decades.
It's
always
the
same
thing
that
we
start
with
one
system
doing
everything
trying
to
do
all
of
the
things
at
the
same
time,
and
then
we
realize
there
are
limitations
to
use
that
framework
or
platform,
and
then
we
try
to
you
know
fork
out
of
that
system
and
try
it
like.
A
Just
like
Billy
explained
that
in
the
beginning
there
were
so
many
folks
of
Bitcoin,
because
we
wanted
to
scale.
We
wanted
to
do
something
different,
so
fragmentation
always
happens
when
there
are
limitations
with
one
thing
and
people
want
to
innovate.
So
there
is
always
one
thing
that
is
I
am
very
sure
of
is
innovation
that
people
will
keep
on
doing
that
will
they
will
keep
on
breaking
the
boundaries,
and
to
do
that,
you
need
extensible
framework,
you
need
something
which
can
allow
for
doing
that.