►
From YouTube: Web 3.0: The New Stack
Description
This panel on Web3 features IPFS project lead and Filecoin network lead Molly Mackinlay, IPFS ecosystem lead Dietrich Ayala, Textile co-founder and CEO Andrew Hill, and physicist and blockchain scientist Adrian Manning.
Join us for Filecoin Liftoff Week, an action-packed series of talks, workshops, and panels curated by the web3 community to celebrate the Filecoin mainnet launch and chart the network’s future. https://liftoff.filecoin.io/
Events take place all week, October 19-23, 2020. #FilecoinLiftoff
For more information on Filecoin
- visit the project website: https://filecoin.io/
- or follow Filecoin on Twitter: https://twitter.com/Filecoin
Get Filecoin community news and announcements in your inbox, monthly: http://eepurl.com/gbfn1n
Chapters
00:00 How has Web3 evolved since its inception?
04:30 The elephant in the room
12:58 Shifting from Web 2.0 to Web3
14:32 What areas of the Web3 stack are making great progress?
20:00 The vision of interoperability
A
A
3.0
stack
a
static
content,
publication
system
with
a
publish
and
retrieve
content
by
its
hash,
dynamic
messaging
system
for
p2p
networking
a
way
to
do
trustless
transactions
with
a
consensus
engine
and
the
integrated
user
interface
to
bring
it
all
together,
do
name
resolution
and
like
find
and
access
and
browse
content.
So
that's
like
a
pretty
good.
A
You
know
four
major
components
of
web
3.0
and
I
think
we've
seen
a
lot
of
that
evolve
over
the
past,
oh
six
years
since
2014,
and
that
was
written
back
then
I
think
it
was
like
highlighting
things
like
bittorrent
and
name
coin
and
a
couple
of
other
things
as,
like
the
be
all
end,
all
of
those
those
components.
But
I'm
curious
for
this
group
like
how
have
these
concepts
evolved
in
the
past
six
years.
B
B
Back
then,
I
was
looking
into
ethereum
and
and
swarm
was
available,
so
swarm
was
kind
of
going
to
be
the
the
or
is
the
file
storage
layer
inside
of
ethereum,
and
it
allowed
you
to
do
static
hosting
of
like
daps
and
and
javascript
things,
and
at
the
time
I
was
kind
of
like
look.
We've
got
it.
You
know
you
can.
B
I
found
myself
I
now
work
in
ethereum
too,
specifically
in
the
networking
layer
so
fundamentally
for
web
three.
We
need
to
one
of
the
components
that
we
need
to
kind
of
advance
is
the
the
networking
layout
so
in
the
traditional
kind
of
web
stack,
we've
got
like
a
client
server
architecture
and
we
now
shifted
over
into
peer-to-peer
networks.
B
So
that's
specifically
kind
of
where
I'm
working
in
ethereum
too,
and
I
guess
the
main
shift
that
I've
seen
since
when
I
started
is:
is
the
research
protocol
labs
and
and
pretty
much
the
entire
community
putting
into
p2p
networks
to
try
and
change
the
fundamental
dynamics
of
how
computers
interact
and,
and
that's
like
one
of
the
core
backbones
for
for
building
like
a
decentralized
web
three.
So
we're
still
doing
that
today,
but
wait.
Wait,
wait
significantly
closer.
In
my
opinion,.
B
C
Oh,
I
can.
I
can
toss
a
couple
out
there,
just
things
that
I
think
are
really
big
speaking
of
elephants
in
the
room
that
I
don't
think
we
have
necessarily
solutions
for.
I
know
a
lot
of
people.
A
lot
of
projects
are
still
working
on
the
user
model
for
web3.
I
think
it's
a
really
tricky
subject
and
I'm
not
sure,
there's
any
clear
sort
of
winning
model.
C
Yet
that's
going
to
help
us
there,
but
like
the
amount
that
I
still
move
through
the
internet,
signing
into
applications
and
services
using
a
handful
of
user
model,
user
identity,
user
security
providers,
that's
a
really
big
thing
that
we
still
need
to
figure
out
and
another
one
is
the
index.
I
think
google
still
has.
You
know
the
best
searchable
index
on
the
internet,
and
I
think
that's
a
really
that
that
has
a
really
good
role
for
us
to
be
able
to
discover
things
on
the
internet.
C
But
it's
not
going
to
be
the
only
index.
I
think
that
there's
a
lot
of
work
still
to
be
done
to
figure
out
how
we
can
build
sort
of
powerful
knowledge
aggregation
systems
on
top
of
these
web
3
protocols
and
I'm
curious
to
see
what
people
build
as
things
like
filecoin
become
real
open
data
sets
become
sort
of
available
over
filecoin
apis
indices
start
getting
built
there.
C
Something
I've
had
a
lot
of
conversations
with
teams
about
is
like
before
when
data
storage
was
a
limiting
sort
of
factor
in
what
you'd
build,
you'd
store
raw
data
and
you
would
create
you'd
create
sort
of
products
on
top
of
that
through
compute.
And
now,
if
you
can
think
of
the
world
having
sort
of
a
boundless
hard
drive,
we
can
think
of
storing
every
facet
of
that
data.
C
We
can
build
indices
that
we
also
store
and
we
also
share,
and
it
can
actually
break
that
model
of
having
to
have
a
singular
sort
of
index
creator
and
provider.
We
can
all
be
indexed
creators
and
providers,
I'm
not
sure
what
that
looks
like
and
I'm
not
sure
where
it
could
go,
but
it
seems
like
an
interesting
other
piece
there.
Those
are
two
that
were,
on
my
mind.
D
I
I
think
that
latter
one
is
fascinating
to
me
like
we,
we
kind
of
the
the
cooperative
nature
of
building
resilient
networks
is
kind
of
implicit
in
these
architectures,
and
what
you're
talking
about
is
something
that's
more
explicit
and
and
with
centralized
infrastructure.
You
get
that
explicit
by
default,
like
it
comes
with
the
company
that
build
the
thing
right
and
that's
not
the
nature
of
how
these
applications
work
are
gonna,
stay
resilient
online
and
immediately
useful
to
end
users.
D
These
are
the
things
that
are
pretty
well
developed
and
articulated
in
the
in
in
the
old
stack,
but
but
aren't
so
clear
in
the
new
stack
when
we
have
when,
like
you
say
when
we
are
both
the
provider
and
and
the
consumer,
those
boundaries
aren't
as
clear
and
the
responsibilities
of
ownership,
and
also
some
of
the
threat
model
in
there
as
well.
About
our
participation
in
that
network
are
as
well
articulated,
so
I
I
think,
making
finding
out
what
those
things
are.
A
Okay,
I
think
we're
all
we're
tapping
into
this
idea
that,
like
integrated
user
interface,
is
actually
probably
a
lot
a
lot
more
in
there
a
lot
more
complex
than
like
just
name
resolution,
there's
a
lot
of
additional
pieces
in
there
from
like.
You
know
the
user
model
to
how
you
know
how
you
think
about
externalizing
information
to
people
who
are
consuming
services.
A
You
know,
yeah
and
fear
is
also
a
great
example
of
like
infrastructure
providers
that
are
layering
on
things
that
empower
a
whole
new
kind
of
ecosystem
of
development
on
top
and
that
I
don't
think
falls
super
easily
into
the
the
previous
encapsulation
of
the
world,
but
is
like
so
critical
for
what
web
3.0
wants
to
do
in
gender,
which
is
a
a
whole
teaming
ecosystem
of
people
building,
on
top
of
it.
So
kudos
to
you
guys
and
excited
for
for
also
like
more
things
in
of
that
nature,
that
like
empower
empower
other
groups.
C
That
necessarily
have
to
guard
themselves
so
like
apis
on
textile,
we're
not
trying
to
build
them
in
a
way
that
protects
them
and
locks
users
and
applications
in
we're
trying
to
build
them
as
apis.
That
move
the
ideas
to
this
to
these
new
protocols
and
these
new
systems
more
quickly,
and
so
it's
sort
of
like
a
temporary
state,
which
I
think
is
interesting
and
he
doesn't
really
cover,
as
kind
of
like
one
of
those
necessary
steps
to
get
there.
But
that's
that's
a
lot
of
where
we
see
ourselves
right
now.
A
B
So
it's
going
to
be,
I
think,
as
andrew
saying,
you've
got
to
take
some
steps
to
transition
people
from
how
they're,
currently
using
the
internet
and
the
general
ideas
of
how
how
the
applications
they're
using
at
the
moment
with
how
they
work.
You
can
easily
search
things.
All
these
kinds
of
things
have
to
fundamentally
shift
because
we're
changing
the
fundamental
just
literally
the
the
way
that
these
things
kind
of
interact
so
yeah.
B
Maybe
we
have
to
build
some
kind
of
you
know
like
kind
of
transition
or
like
extra
layers
on
top
that
kind
of
mask
some
of
how
these
things
operate,
underneath
so
that
users
can
gradually
stack
until
they
become
more
comfortable
and
then
you
know
we
can.
We
can
take
it
from
there
as
they
as
they
get
used
to
kind
of
the
new
way
of
doing
things.
D
D
We
have
given
them,
maybe
a
foot
gun
in
some
respect.
We
found
from
basic
things
like
you
know.
I
dropped
my
phone
with
my
keys
into
the
ocean,
but
also
increasingly
the
the
safety
of
the
data
that
they're
encrypting
so
from
one
part
of
like
when
we
talk
about
stacks
oftentimes,
we're
talking
about
libraries
architectures
how
what
what
is
the
new?
D
What
is
the
new
osi
layer,
but
but
design
and
communication
is
left
for
something
as
an
exercise
that
comes
after
that
and
oftentimes
the
maybe
the
model
should
be
flipped,
and
how
do
things
like
anti-surveillance
get
baked
into
this
stack,
I
think,
is
going
to
be
something
that
is
like
now
that
we
know
those
threats
in
the
old
web.
How
have
we
designed
for
those
threats
in
in
the
new
stack
and
that
that's
going
to
be
a
really
big
responsibility
when
you're
talking
about
how
do
you
migrate?
A
A
One
one
I'll
throw
out
there
is
definitely
in
the
past
year,
seeing
kind
of
the
development
around
web
applications
and
kind
of
the
building
up.
Web3
websites
like
made
a
whole
like
a
giant
leap
forward.
I
feel
over
the
past
year,
like
fleek,
unstoppable
domains,
ens
like
a
ton
of
these
groups,
just
made
it
way
like
10x,
easier
to
go
and
and
put
up
your
first
website
on
the
d
web
like
it
was
definitely
possible
before,
but
now
it's
just
like
has
the
tooling
the
infrastructure.
A
The
developer
ux
around,
like
just
making
it
happen,
like
three
box
did
a
lot
of
stuff
around
deep
blogging
as
well,
like
it's
become
much
more
accessible
for
people
to
do
that,
and
so
that's
that's
one
of
those
areas
where
it
feels
like
things
are.
You
know,
moved
moved
to
like
a
whole
leap
forward
exceedingly
quickly,
which
was
super
interesting.
B
Yeah,
I
can't
not
say
it:
I've
been
working
on
ethereum
too
for
the
last
two
years,
so
I
might
as
well
I
mean
everyone's
heard:
it
scalability
right
so
layer,
two
solutions
and
everything's
kind
of
grown.
I
mean
I've
been
working
on
on
ethereum
too
for
the
last
two
years.
So
scalability
is
one
of
the
things
we've
specifically
been
trying
to
focus
on,
although
all
the
latest
next-gen
blockchains
are
all
focusing
on
scalability.
B
C
C
The
next
area
that
I'm
really
focused
on
and
I'm
excited
to
see,
projects
starting
in
is
actually
getting
these
things
integrated
into
tools
and
systems
that
people
are
already
using.
I
think
that
a
lot
of
a
lot
of
development
in
the
space
has
been
to
build
things
totally
new
and
I
think
that's
really
great
for
creativity
and
exploration
of
what
the
limits
of
these
protocols
are.
C
But
I
also
think
that
there's
just
a
huge
opportunity
to
go
to
where
users
already
exist
and
find
ways
pathways
to
integrate
and
give
them
new
capabilities,
new
services,
new
values
in
those
places,
and
so
we've
been
really
trying
to
encourage
teams
to
look
at
you
know
what
are
the
open
source
tools?
What
are
the
open
source
networks
where
we
could
add
something
and
do
small
integrations
and
get
people
exposed
to
this
stuff?
C
And
I
think
this
is
the
year
that
that
stuff's
really
going
to
happen
because
we're
already
seeing
projects
do
that,
and
so
some
of
those
are
going
to
take
off
and
we're
going
to
see
not
only
10x
usability
but
10x
usage
really
quickly
and
and
it's
going
to
be
because
of
those
inroads.
And
I'm
really
excited
for
that.
D
I
I
really
suck
at
that.
I
think
that
the
the
success
of
this
stack
depends
on
its
ability
to
to
to
bring
people
with
it
and
to
bring
people
in
one
of
the
one
of
the
things
that
we're
doing
to
be
able
to
get
basic,
ipfs
libraries
functional
inside
existing
frameworks,
like
some
of
the
work
that
we're
having
to
do
for
react.
Native
support
is
really
upstreaming.
D
Some
changes
that
some
of
these
communities
have
needed
for
a
while,
so
there
are
really
opportunities
that
web
three
projects
can
bring
to
existing,
really
large
developer
communities
that
both
bring
some
some
of
the
benefits
of
our
architectures
and
exposure
and
visibility
into
those
communities,
then,
along
with
participation
and
engaging
them
by
giving
back
into
them.
So
looking
for
those
opportunities
where
you
can
kind
of
get
that
that
double
win
is
really
important
for
both
credibility
and
and
engagement,.
D
Yeah,
I
I
think
we're
really
just
on
the
cusp
of
that
too.
We're
getting
to
the
point
where,
like
when
you
say,
install
multiple
applications.
I
think
one
of
the
end
user
experience
goals
that
we
have
for
people
on
on
web3
and
distributed
applications
is
to
not
have
to
have
that
install
step
in
as
much
as
possible
to
do
so.
D
We're
gonna,
see
probably
more
native
integrations
in
2021
for
sure,
into
browsers
and
more
way,
I
guess
removing
some
of
the
paper
cuts
of
integration
of
hybrid
applications
so
where
you
access
it
like
it's
a
lot
of
the
applications
that
we've
seen
in
the
last
couple
days
are
distributed.
Applications
that
you
access
through
the
http
web,
that's
going
to
be
a
hybrid
statement
that
we're
going
to
be
out
for
a
while.
D
So
if
we
can
remove
paper
cuts
in
that
and
make
those
applications
work
a
little
bit
more
smoothly
in
that
transition,
that's
going
to
help
everybody
developers
and
end
users
alike.
The
work
that
we've
done
with
the
galia
is
landing,
some
of
the
fixes
in
in
chromium
and
in
firefox
to
be
able
to
make
browsers
today's
browsers
work
better
with
local
nodes
that
are
running
simultaneously
and
also
things
like
the
protocol
handler
work
that
we've
done
in
chromium
to
be
able
to
register.
D
B
One
of
the
go
ahead:
sorry,
just
really
quickly.
One
of
one
of
the
other
things
that
we're
we're
trying
to
encourage
and
advance
is
for
users
to
also
run
run
their
own
local
nodes,
as
you
said,
so,
as
as
things
kind
of
integrate.
One
way
to
do
that
is
with
to
try
and
slim
down
the
client
so
that
the
clients
who
don't
have
to
spend
you
know
two
weeks
downloading
100
gigabytes
of
data.
B
If
you
have
a
client
that
can
run
and
it
just
it
kind
of
sits
there,
you
can
run
it
on
a
raspberry
pi,
it
doesn't
chew.
You
don't
need
to
sync
millions
of
gigabytes
of
data
that
that
the
the
way
that
that
kind
of
makes
you
kind
of
more
secure
locally,
but
it
strengthens
the
the
p2p
network
and
the
health
of
the
health
of
the
network
as
well.
So
that's
one
way
going
forward
is
to
to
kind
of
simplify
the
client
so
that
they
can
run
very
locally
with
minimal
resources.
A
Help
with
that
accessibility
and
more
people
participating
more
like
clients,
more
things
that
kind
of
make
it
left
less
heavy
to
to
run
blockchain
infrastructure
as
well
andrew.
I
know
you
guys
are
doing
a
ton
of
stuff
with
like
powergaid,
and
you
know
better
apis
so
that
you
don't
have
to
be
running
your
own
local
node.
In
order
to
do
things
as
well.
C
Yeah,
there's
something
that
didn't
come
up
with
your
first
question:
either
is
just
kind
of
the
whole
vision
of
interoperability.
I
think
so
many
projects
share
it,
but
it
isn't
a
clear
path,
necessarily
how
we
how
we
get
there,
but
I
I
mean,
I
think
a
lot
of
smart
people
are
working
on
the
problem,
so
I
think
there's
some
promising
directions,
but
that's
really
related
to
this
problem,
because
at
the
end
of
the
day,
it
doesn't
necessarily
matter
if
you
run
it.
C
For
a
little
bit
longer,
but
not
everybody
does
not.
Everybody
does
just
like
just
doing
that.
The
easy
way
for
a
lot
of
people
that
are
trying
to
onboard
quickly
or
try
to
figure
these
things
out
or
get
your
ideas
disseminated
to
people
easily.
That's
the
way
to
go
immediately,
but
not
everybody
has
to
do
that
and
that
that's
really
cool.
D
The
the
birdie
project
they
they
did
an
implementation
like
a
a
smaller
implementation
of
of
go
ipfs
for
embedding
in
native
mobile
applications
and
one
of
the
things
I
thought
was
interesting
about
that
was.
Was
this
idea
of
kind
of
contextual
capability
designing
this
stacked
that
we
talked
earlier
about
the
modularity
of
the
stack
with
with
http
and
web
rendering
engine?
That's
not
really
something
you
can
do
so
much,
but
here
you
know
they
played
with
the
idea
of
you
know,
there's
it's
like
full
node
and
then
there's
http
client
for
an
fps
node.
D
D
If
a
node's
gonna
run
down
your
battery,
that
might
be
totally
fine
depending
on
the
user
need
at
the
time,
and
vice
versa,
and
that
intersection
of
where
that
stock
is
and
the
how
we
design
these,
for
these
capabilities
is
going
to
be
key
to
be
able
to
meet
that
user
need.
So
some
some
people
are
doing
some
some
pretty
interesting
work.
There.
A
A
Like
you
know
you,
as
the
user
have
have
the
say
in
where
your
data
goes
or
what
you
store
on
your
node
or
how,
how
you
configure
your
own
knobs
and
then
combining
that
with
how
you
make
it
accessible
so
that
you
know
what
knobs
to
configure
and
you're
not
overwhelmed
by
like
choice
and
paralysis,
but
you
can
kind
of
choose
from
a
variety
of
different
ways
that
you
can
intersect
with
the
network.
Like
the
thing
that
brings
to
mind
to
me
is
like
the
ipfsdht
and
kind
of
differentiating
you
know.
A
I
mean
they'd,
be
really
cool
to
see
more
research
on
that
space
and
like
more
mapping
of
like
all
the
different
ways
that
to
highlight,
like
you
know,
which
which
things
should
exist,
that
don't
exist.
Yet
I
feel
like
there's
so
much
evolution
going
on
that
we're
gonna
identify
a
lot
a
lot
of
new
maxima
that
we
haven't
haven't
found.
Yet
so
I'm
psyched
for
that,
and
I
feel
like
there's,
there's
more
to
be
done
in
that
space
as
well
cool.
We
are
just
about
a
time.
A
C
Well,
I
I
don't
know,
I
think,
related
to
all
of
that.
I
think
of
I
think
of
like
so
many
big
ambitious
projects
around
you
know
connecting
infrastructure
and
smart
cities
and
remotes
these
things
that
are
just
like
streaming
data
and
connecting
things
in
really
advanced
ways,
and
I
think
so
much
of
it
comes
from
a
really
intelligent
workforce
and
really
smart
people
just
thinking
about
creative
new
ways
of
solving
problems,
and
so
for
this
space.
I'm
really
excited
because
I
think
we
might
have
just
like.
C
C
Getting
people
taught
about
these
protocols
early
on,
so
that
when
you
know
when
the
next
wave
of
students
graduate
college,
they
go
off
to
all
kinds
of
workforces
with
these
armed
with
these
ideas
and
innovate
and
bring
totally
new
concepts
to
the
space
that
we're
not
expecting
we're,
like
so
small
still
as
exciting
as
everything
is
we're
like
still
such
a
small
fraction
of
the
sort
of
thinkers
in
the
world,
and
I
think
there's
so
much
more,
we
can
get
so
that's
above
everything
else.
That's
like
the
exciting
next
step,
I
think,
is
stream
energy.
A
I
lost
your
audio,
but
at
the
end,
but
I
completely
agree.
The
idea
of
like
you
know
now
is
now
is
the
opportunity
to
like
take
the
amazing
work
that
we've
done
so
far
and
like
bring
it
to
more
people
like
call
to
action,
go
and
go
and
share
this
new
ecosystem
that
everyone
can
participate
in
help
others
learn
about
it,
understand
it
build
on
top
of
it.