►
From YouTube: libp2p and IPFS Overview - Matt Zumwalt
Description
Originally recorded during the Berlin Developers Meetings from July 9-13, 2018.
A
The
next
round
of
talks
we're
gonna,
do
a
round
of
lightning
talks,
so
this
next
section
is
going
to
be
short,
quick
project
updates
that
are
each
about
five
minutes,
long,
I
and
and
what
we're
gonna
do
is
I'll
do
the
first
one
one
mine
might
be
slightly
more
than
five
minutes:
I'm
gonna
try
to
keep
it
too
hung.
Let's
tie
me
and
then
what
I
will
answer
questions
I'll
take.
Maybe
two
questions
but
I'll
answer
questions.
A
While
the
next
person
is
setting
up
they're
setting
up
their
computers,
so
we're
gonna
try
to
turn
this
around
quickly
because
we
want
to
pack
in
a
bunch
of
rapid-fire
information
before
our
brains,
collapse
from
all
the
inputs
and
then
after
that,
we'll
go
to
lunch
and
lunch
will
be
right
out
here
in
the
lobby.
So
I
beginning
my
talk.
This
is
an
overview
of
the
whole
ipfs
and
lib
p2p
ecosystem
or
a
review
of
that
ecosystem.
A
It's
also
about
who
has
access
to
the
technology.
Who
has
the
knowledge
to
wield
that
technology,
so
we're
working
in
a
big,
ambitious
space
and
are
many
different
projects
which
sometimes
seemed
scattered,
are
touching
many
things
because
we're
trying
to
upgrade
the
whole
the
whole
web.
The
whole
system
to
give
everyone
this
technical
capacity.
So
three
key
items
in
here
are
ipfs
the
again,
as
you
saw
in
Juan's
keynote,
we
haven't
finalized
a
mission
statement
for
ipfs.
A
So
these
are
not
what
are
in
slides
are
not
mission
statements
they're
more
like
a
gesture,
a
reminder
of
what
these
projects
are
focused
on,
so
ipfs
is
focused
on
upgrading
the
web
to
be
content
addressed
and
it's
which
that
means
identifying
a
content
by
what
it
is,
rather
than
identifying
content
by
where
it
is,
and
then
having
done
that.
Having
that
identifier
space
allowing
people
to
exchange
data
peer-to-peer
without
relying
on
central
parties.
A
In
order
to
achieve
that,
we
need
Lib
p2p.
We
need
a
robust
networking
stack
and
libraries
that
allow
us
to
find
peers
connect
with
them
securely
and
exchange
data
directly
with
them
without
relying
on
central
parties.
So
it's
that
second
part
of
the
ipfs
purpose
that
is
primarily
tackled
by
Lib
p2p
and
then
there's
no
point
in
having
all
that
connectivity.
A
On
the
network
being
able
to
compute
and
process
and
find
that
data,
so
to
go
a
little
bit
more
detail
into
each
of
those
projects,
ipfs
speaks
to
many
different
things
for
many
different
people,
so
there's
the
sense
of
resilience
of
imagining
a
library
of
alexandria
that
can't
be
burned.
So
how
do
you
achieve
that?
A
How
do
you
achieve
data
be
existing
in
many
places
and
being
held
in
ways
that
it
can't
be
lost,
building
distributed,
applications
making
it
possible
for
people
to
build
offline
first
applications
purely
peer-to-peer
applications
blockchain
based
applications,
then
there's
data
stewardship.
Allowing
people
excuse
me
to
manage
their
data,
coordinate
storage
of
that
data
replicating
it
describing
it
analyzing
it
recontextualizing.
It
excuse
me
which
leads
to
this,
which
leads
to
this
topic
of
possession
and
participation.
So
what
data
will
we
choose
to?
What
data
will
we
participate
in
redistributing
or
decline
to
participate
and
redistributing?
A
Meanwhile,
Lib
p2p
handles
a
lot
of
most
of
the
written
many
or
most
of
the
really
difficult
challenges
of
ipfs.
So
it's
handling
things
like
NAT
traversal,
the
DHT
content,
routing
peer
discovery.
This
is
the
stuff
that
makes
it
possible
for
ipfs
to
function
as
a
peer-to-peer
network
alright.
But
the
interesting
thing
is
that
it's
not
just
ipfs
that
needs
that
it's
anyone,
who's,
building,
peer-to-peer
applications,
and
so
this
is
where
lit
p2p
is
growing
into
its
own
thing,
with
a
broader
use
of
users,
there,
a
broader
set
of
users
and
then
finally
IPL
D.
A
A
Now
all
three
of
those
things
intersect
when
you
start
applying
these
technologies-
and
you
want
to
deal
with
things
like
access
control,
reader,
privacy,
writer,
privacy,
real-time
updates
of
data
on
a
network,
handling,
identity,
censorship,
allow
lists
and
block
lists,
or
also
indexing
data
querying
and
versioning
and
discovery
of
the
data.
It
relies
on
all
of
these
pieces
being
assembled
in
ways
that
actually
work
for
people,
and
so
how
do
we
achieve
that?
A
Our
approach
is
to
build
community
structures
and
decision-making
structures
that
allow
many
many
people
to
participate
in
imagining
what's
possible
and
build
build.
The
tools
that
make
those
things
possible,
and
so
a
key
thing
here
is
that
the
innovation
on
the
protocol.
We
are
configuring
things
so
that
the
innovation
on
the
protocol
is
driven
by
product
development.
That's
folk
just
on
users
in
the
world.
A
Meanwhile,
in
order
to
achieve
this
and
actually
include
as
many
people
as
possible
in
this
innovative
process,
this
reimagining
of
the
future,
we
need
to
work
really
hard
on
having
a
genuinely
diverse
global,
inclusive
community,
that's
using
open
source
principles
and
then
fundamentally,
like
one
hammer
Don
in
a
lot
of
ways:
ship
stuff
that
works
just
work
really
hard
to
polish.
What
we
make
and
make
it
work
really
well
for
people
make
it
easy
to
use
a
preview.
Some
of
these
working
groups
are
giving
lightning
talks,
so
you'll
get
a
lot
more
detail
of
them.
A
Then
we
have
the
web
browsers
and
GUI
working
groups
documentation
working
group.
We
have
all
the
activities
around
community
offs
that
Michael
is
spinning
up.
We
have
the
dynamic
data
and
capabilities
working
group
dealing
with
these
challenges
of
data
structures
and
dynamic
data
and
encryption
and
identity
for
building
applications
in
a
distributed
context.
We
have
the
work
around
decentralized
data
stewardship
that
Michele
Hertzfeld
is
is
taking
on,
and
then
we
have
an
infrastructure
team,
that's
doing
a
huge
amount.
So
that's
a
sampling
of
the
working
groups
that
we
have.
A
A
So
this
is
this
is
very
exciting,
and
that
is
also
a
precursor
to
having
an
IP
FS
Kampf,
which
we're
aiming
to
do
in
Lisbon
in
November,
and
that
will
be
a
much
larger
venue
for
people
to
gather
and
learn
about
ipfs
and
share
their
work,
so
that
I
hope
this
helps
as
a
preview
of
what
you're
gonna
see
in
people's
individual,
slides
from
different
working
groups
and
teams,
and
so
then,
if
they
divvy
to
you
next,
all
right
so
wall
to
bead
setting
up
his
his
laptop.
Does
anyone
have
questions
for
me.