►
From YouTube: Introduction to IPFS & Filecoin ft. Konstantin Tkachuk
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
hello,
everyone
also
from
my
side
what
a
great
bar
from
molly.
Let's
rise
into
the
presentation,
I
will
myself
I'm
constantine
kachuk
kechuk,
I'm
going
I'm
a
startup
operated
protocol
labs
and
I
will
go
through
more
details
about
ipfs
and
filecoin
and
how
they
shape
the
future
webfree.
So
today's
agenda
for
my
site
would
be
first
of
all
the
core
concepts
of
ipfs
and
filecoin.
Then
I
will
talk
in
details
about
the
tool
for
builders.
A
We've
already
seen
a
great
presentation
on
what
are
the
opportunities
building
with
filecoin,
and
I
will
give
you
the
exact
tools
which
you
can
use
straight
away
to
make
your
solution
better
using
distributed
technology
and
ivfs
and
filecoin,
and
then
I
will
tell
you
also
a
bit
of
the
highlights:
what
to
build.
What
is
coming
in
web3
and
what's
the
most
hot
topic
right
now,
so,
starting
with
the
core
concepts
of
ipfs
and
filecoin
yeah.
A
So
we
are
somewhere
between
web
2
and
web3,
and
what
exactly
web3
is
let's
suffice
that
it's
that
evolution
of
the
internet,
it's
the
next
step
of
the
internet
and
it
makes
web
read,
write
and
trust
trust
being
an
operative
thing
here,
and
it
is
achieved
through
a
verifiability
and
a
whole
bunch
of
underlying
primitives
and
technology
that
builds
up
to
that.
So
verifiable
data
is
essential
to
a
truly
distributed
system
and
data,
as
itself
is
one
of
the
big
pieces
of
a
free
stack
puzzle
which
comes
on
the
slide
here.
A
There
is
a
lot
a
lot
to
be
updated.
Development
in
web3
is
just
immense
right.
Now
there
is
a
lot
of
new
technologies
coming
up.
There
is
a
more
a
lot
of
lot
of
solutions
coming
to
the
web.
A
Free
stack,
but
still
the
storage
itself
is
one
of
the
core
points
of
any
operation
happening
in
web
free
and
ipfs
and
filecoin
is
here
to
also
support,
building
or
transitioning
for
web
2
to
a
more
resilient,
accessible,
scalable
and
also
cheap
internet
storage,
and
not
only
storage
but
generally
internet
operation
that
we
have
so
also.
I
would
say
that
ipfs
and
filecoin
is
here
not
only
for
storage
anymore.
A
We
are
also
building
the
web
free
architecture,
which
surely
will
support
very
very
soon
the
layer,
one
blockchain
coming
with
an
fvm,
and
we
also
can
easily
put
ourselves
into
the
part
with
off
chain
storage,
which
is
also
what
ipfs
can
do
and
coming
from
this
more
of
an
overview.
We
are
truly
right
now
in
this
transition
from
web
2
to
web3,
and
some
of
the
companies
are
more
to
the
left.
A
Some
of
the
companies
are
more
to
the
right,
but
what
we
are
all
aiming
for
is
a
truly
distributed
internet,
where
the
data
information
and
knowledge
first
of
all,
the
couple
of
most
important
assets
which
we
have
today
and
we
want
to
preserve
them.
We
want
really
to
have
them
in
the
hands
of
people,
so
how
to
do
this,
how
to
build
this
resilient
and
how
to
make
sure
that
we
actually
own
the
data
and
it's
not
centralized
and
not
blocked
from
us
and
not
used
on
our
behalf.
A
That's
the
topic
of
the
presentation
which
I'll
go
through
right
now.
So
if
we
are
aiming
for
distributed
data,
we
want
to
have
a
solution.
First
of
all,
which
is
resilient,
which
is
performant,
which
is
scalable.
At
the
same
time,
it
should
be
secure,
efficient
trustlessness
and
it
should
be
censorship
resistant.
Nowadays,
we
see
a
lot
of
the
failure
points
in
the
existing
centralized
solution
where,
while
having
a
single
point
of
failure,
it
immediately
leads
us
to
the
problems
like
censorship,
governmental
organizational,
and
there
is
no.
A
The
and
the
data
which
apparently
we
should
own
by
ourselves,
is
a
is
monetized
by
the
companies
which
have
the
access
to
it
or
the
central
access
and
monitor
into
it.
Instead
of
that,
we
actually
want
to
have
a
user-powered
source
user
power
service
which
ensures
that
we
have
privacy
of
our
own
data
and,
at
the
same
time,
the
data
has
to
be
self-verified
and
known
silent.
A
A
file
could
contain
any
content
and
essentially
folder
is
also
just
a
table
of
the
content
inside
with
the
files.
So
why
interplanetary,
though,
because
it
was
conceived
as
a
way
to
upgrade
the
web
in
a
way
that
it
would
still
work
if
our
network
stretches
across
planets
the
idea
behind
this
that,
if
you
are
on
mars-
and
you
are
wishing
to
take
some
data
from
earth,
it
will
take
at
least
one
hour
to
request
the
information
down
to
earth
and
backwards.
A
A
It
allows
you
to
retrieve
the
content
from
the
nearest
node
and
from
the
cache
solution
all
across
the
ipfs
network,
instead
of
just
referring
to
the
central
point
somewhere
on
the
database
on
earth,
and
that's
very
handy
in
order
to
implement
that
we
have
to
do
the
content
addressing
which
is
ipfs
really
addresses
the
content
by
what
it
is
instead
of
where
it
is.
Molly
already
gave
you
a
brief
explanation,
but
if
you
think
about
content
addressing
as
it
is
right
now
in
computers,
we
do
it
all
that
all
the
time
we
have
a
path.
A
We
have
structure
folders
and
we
get
an
index
of
a
certain
item.
We
replace
it
with
a
content
identifier
instead
of
asking
where
the
content
is.
Locating,
we
don't
need
to
go
to
a
library
as
and
then
just
say.
Okay,
I
need
the
location
of
the
book.
We
really
go
for
the
book
itself
for
the
content.
A
Here
we
give
you
a
content
identifier,
which
is
a
unique
fingerprint
of
what
you
are
looking
for,
and
it
tells
you
what
you
are
looking
for,
and
it
tells
also
the
network
what
you
are
looking
for,
and
the
network
itself
resolves
the
best
location
to
serve
it
from
either
your
backpack
or
the
nearest
library
or
the
amazon
shop.
It
doesn't
matter
for
us,
you
can
serve
it
from
anywhere,
but
we
give
you
the
opportunity
to
discover
the
objects
regardless
of
their
location
and
that's
how
we
do
the
cad
itself.
A
Cad
in
itself
is
a
cryptographic
hash
function,
which
is
ssh
sha
256,
which
allows
you
to
encrypt
any
object
into
a
string
which
gives
you
a
unique
identifier
and
the
same
content
always
resolve
you.
The
same
cid
and
the
content
cd
can
be
reproduced
at
any
time
from
the
original
content.
This
gives
us
this
layer
of
verifiability.
A
When
you
retrieve
a
file,
you
can
also
provide
a
hash
of
it
once
more
and
then
validate.
If
the
object
you
received
is
matching
the
hash
you
originally
requested,
and
that
brings
us
a
lot
of
a
lot
of
functionality
to
making
the
web
really
and
secured
in
the
way
that
we
can
receive
the
objects
which
we
are
actually
interested
in.
A
Also,
the
cid
provides
us
the
opportunity
to
encrypt
it
on
your
level,
so
there
is
no
secret
source
because
behind
the
ipfs,
which
actually
specifies
how
to
encrypt
a
certain
files,
no
that's
actually
happening
on
your
side
on
the
computer
on
the
user
side,
so
ev,
regardless
of
the
computer,
where
the
file
has
been
encrypted,
it's
always
resolve
returning
you
the
same
cid,
which
is
based
exactly
on
your
content
and
that's
the
beauty
of
it.
If
you
think
about
not
the
files
but
the
folders,
it's
that
it's
doing
exactly
the
same
thing.
A
So
a
folder
is
just
a
special
kind
of
a
file
which
lists
other
files
inside
of
it,
and
the
core
principle
remains
the
same.
You
can
create
a
cid
out
of
your
folder
and
it
will
be
pointing
to
exact
number
of
the
files
or
exact
list
of
the
files
which
you
have
inside
and
at
the
same
time,
the
files
inside
could
also
be
the
cads
themselves
so
that
we
reduce
the
number
of
overall
stored
files
on
the
internet
and,
at
the
same
time,
to
duplicate
the
need
for
storing
immense
amount
of
data.
A
Let
me
briefly
explain
you
how
it
works
in
life,
so,
on
the
bottom
line
we
have
multiple
objects,
each
of
which,
having
their
own
cids.
You
see
the
fingerprint
and
the
colors
are
explaining
the
uniqueness
of
the
cid.
So
we
have
a
roots
id
of
a
folder
which
contains
multiple
file
uploaded
by
different
users.
A
Here
the
benefit
of
merkle
dags
or
the
direct
acrylic
graphs
coming
in
into
the
help
we
are,
they
are
helping
us
to
create
a
graph
data
structure
which
in
which
each
node
is
content
addressed.
So
we
exactly
know
what
are
the
objects
inside
of
each
element
and
we
can
traverse
the
graph
to
receive
a
certain
point
or
an
object
inside
the
ipfs
first
file,
then
folders
and
folders
and
folders.
A
The
beauty
of
it
comes
when
a
user
wants
to
create
a
new
folder
with
a
list
of
files,
part
of
which
were
already
existing
in
the
network
before
so.
You
see
a
new
user
on
the
very
right
which
creates
a
folder
which
contains
only
two
objects
out
of
all
four.
He
creates
a
folder
which
points
to
the
same
object,
but
since
we
are
pointing
to
cads,
the
files
are
already
on
the
network
and
then
it
just
creates
a
new
pointers,
but
the
object
could
be
already
stored
could
be
already
served
from
the
ipfs
network.
A
Therefore,
it
reduces
the
redundancy
of
uploading,
many
many
of
the
same
type
of
objects,
and
you
can
retrieve
it
at
any
point
of
time
straight
away
from
the
ipfs
network,
from
the
closest
peer
which
contains
and
has
your
data.
So
this
is
how
cid
working
it
also
provides
the
opportunity
to
duplicate
the
files
on
the
network
and
verify
the
content.
If
the
cid
is
changing,
this
is
how
one
folder
works.
Then
we
go
to
the
network
itself.
A
First
of
all,
we
need
to
understand
that
there
are
multiple
multiple
of
peers
on
the
peer-to-peer
network,
which
stores
pieces
of
your
data
pieces
of
the
content
and
allows
you
to
retrieve
it
from
the
closest
cid,
where
closest
peer,
which
has
your
content.
So
we
have
a
huge
swarm,
a
network
of
peers
and
for
each
peer,
it's
very
important
that
it
has
to
be
first
discoverable
and
it
must
be
rootable.
A
So
we
need
to
know
how
to
reach
each
and
every
peer
in
the
network
so
that
whenever
you
are
looking
for
a
content,
you
can
really
point
to
the
certain
peer
and
request
the
data
from
it.
That's
where
the
content
routing
distributed
hash
tables
comes
in
place,
the
distributed
hash
tables
is
maintained
by
multiple
peers,
but
it's
only
a
small
number
of
rows
which
are
stored
within
each
pier
and
those
are
maintained
not
for
the
whole
network
itself.
A
But
more
a
piece
is
a
fragmented
part
of
it
which
allows
to
reduce
the
load
on
each
particular
node,
and
we
have
a
very
simple
two
column
table
which
provides
us
with
a
key
and
a
value
stored,
and
this
you
can
think
of
as
a
whole
as
a
phone
book,
but
the
phone
book
where
everyone
allows
where
everyone
maintains
it
together.
So
you
have
a
name,
and
you
have
a
number
of
a
person,
and
it's
very
nice
because
also
a
number
in
itself.
A
You
can
really
call
it
directly,
which
is
partially
how
cid
works,
because
you
really
address
it
to
the
to
the
person
who
stores
your
data
not
to
a
server
which
knows
where
the
person
is
located
and
ipfs
works
exactly
on
the
same
way
where,
when
you
request
the
data
from
this
dht
table,
the
peer
which
you
requested
it
from
either
can
serve
the
data
directly
to
you
from
his
storage
or
if
he
doesn't
know
where
the
data
is
located,
then
he
can
ask
nearby
peers
asking
if
you
have
the
same
data
which
my
user
requested,
and
we
also
know
approximately,
where
the
closest
peer
which
can
serve.
A
You
the
data,
is
located
so
that
we
don't
need
to
go
through
the
whole
swarm
on
the
network.
We
rather
just
request
the
points
or
the
peers,
which
are
most
probably,
which
are
more
likely
to
have
your
data
than
the
other
one,
and
in
this
case
peers
are
maintaining
the
dht
table
and
declaring
where
the
peer
id,
which
provides
a
specific
cid
and
how
to
connect
to
these
peers.
So
then
peers.
All
the
time
can
query
the
dht
table
to
find
which
peer
is
providing
which
content.
So
this
is
how
the
ipfs
works.
A
A
Then
you
can
request
the
data
from
your
node
and
be
make
it
available
over
the
ipfs
network,
but
if
you're
far
from
the
node,
then
it
will
not
be
very
reliable
or
it
will
be
long
to
retrieve
and
so
on.
So
then,
you
can
maybe
run
your
own
network
of
the
nodes
and
then
the
infrastructure
and
the
team
to
support
building
this
network,
or
you
can
pay
a
pinning
service
to
pin
your
content
on
their
nodes,
such
solutions
as
pinata
temporal
and
fura
and
many
more.
A
And
then
you
just
hope
that
your
content
becomes
popular
enough,
that
other
nodes
will
pin
it.
So
does
that
sound
to
you
as
a
really
decentralized
and
reliable
web
to
me?
Not
really.
You
really
should
not
rely
on
someone's
good
faith
in
order
to
store
your
data
and
that's
exactly
where
filecoin
comes
in
place.
Filecoin,
incentivizes,
persistence
and
verifiable
storage
designed
for
webfree
filecoin
uses
the
same
process
as
ipfs
for
resulting
content
identifiers
on
filecoin,
and
these
are
exactly
the
same
cids
we
just
talked
about.
A
Moreover,
ipfs
is
a
storage
layer
agnostic
and
that's
because
the
magic
of
ipfs
cads
they
becoming
the
property
of
the
data
itself,
so
that,
regardless
of
what
solution?
Do
you
want
to
use
for
permanence
of
your
data,
whether
it
will
be
a
file
coin
or
cloud
solution,
or
maybe
both
or
there
any
amount
of
solutions
which
you
want
to
develop?
A
We
still
provide
you
the
same
content
identifier
which
is
independent
of
us,
even
so
that
regardless
what's
happening
for
the
future,
we
still
can
detect
or
trace
the
content
by
trace
the
data
by
its
content.
In
fact,
filecoin
network
is
based
on
time,
limited
deals
which
allow
you
to
store
the
data.
So
whenever
you
put
an
object
or
ipfs
object
to
the
filecoin
deal,
you
make
a
deal
with
a
storage
provider
to
store
your
content
and
ensure
cryptographically,
that
your
store
content
is
persistent
and
available
through
the
time
of
the
deal
on
the
network.
A
It
gives
you
this
reliability
and
the
verifiability
of
the
content
persistence
over
a
long
time
and
makes
sure
that
your
content,
stored,
redundantly
and
verified
by
network
via
proof
of
replication,
which
proves
the
storage
provider,
is
storing
a
unique
copy
of
original
data
and
proof
of
space
time
with
which
proves
that
data
is
stored
continuously
over
time.
We
run
checks
for
each
data.
Every
24
hours,
which
guarantees
us
and
guarantees
the
final
user
that
his
content
is
persistent.
We
really
run
it
also
redundantly.
A
So,
regardless,
if
one
content,
provider
or
storage
provider
is
losing
your
data
for
some
of
the
reasons
we
still
have
redundant
copies
on
the
network,
which
will
be
able
to
serve
you
and
replicate
again
to
the
minimum
required
amount
for
most
of
our
solutions.
We
use
at
least
five
redundant
copies
so
that
your
data
is
always
secure
with
ipfs
and
filecoin,
and
you
really
can
retrieve
it
whenever
you
want-
and
that's
where
I
can
say
that
ipfs
is
really
loving.
Filecoin
ipfs
here
is
for
fast
and
flexible,
retrieval
with
the
gateways.
A
A
We
really
want
to
have
a
solution
which
is
not
dependent
on
one
centralized
approach
or
one
centralized
logic.
Therefore,
there
is
a
lot
of
different
layers
that
serve
different
functions.
We
have
first
of
all
the
front-end
layer
which
could
be
web
2
existing
solutions.
You
already
know
it
could
be
also
a
web-free
layer.
A
Then
we
have
a
logic
which
multiple
of
the
smart
contract
networks
or
layer,
one
solution
networks
already
have,
and
that's
where
also
we
will
be
able
soon
to
place
file
coin,
with
the
smart
contracts
and
a
vm
coming
and
then
we
have
a
storage
helpers.
A
Storage
helpers
serve
you
with
the
handy
tools
which
allow
you
to
do
the
file
coin,
dealing
and
storage
on
ipfs
network,
with
the
knees
and
that's
what
our
advice
generally
is
to
use
the
storage
helpers
directly
so
that
for
your
applications,
it's
very
handy
and
simple
to
operate
the
ipfs
and
filecoin
networks.
So
what
are
some
of
the
storage
networks
or
storage
helpers
that
can
give
you
the
opportunity
to
build
on
top
of
ipfs
and
filecoin?
First
of
all,
there
is
a
web
free
storage
solution.
A
It's
designed
for
file
coin
and
ipfs
storage,
it's
familiar,
and
it
has
familiar
and
simple
interfaces
and
it's
a
production,
level,
storage
and
retrieval
which
provides
you
with
the
retrieval
reliability
and
performance.
It's
very
simple
to
use.
There
is
only
an
api
key
which
you
need
to
generate
from
registering
on
the
website,
and
then
you
can
call
the
api
key
and
store
the
all
your
data
from
your
traditional
web
solutions
on
ipfs
and
filecoin.
A
We
also
provide
this
is
also
provided
from
protocol
apps
directly,
so
we
provide
one
terabyte
always
for
free
and
then
it's
possible
to
extend
it
for
your
specific
solutions,
and
we
are
more
than
happy
to
support
you
developing
on
free
storage,
then
one
of
the
subset
or
a
specific
tool
which
was
also
developed
for
the
nfts
directly,
which
is
nft
dot
storage.
We
treat
nfts
as
a
public
good,
which
should
be
available
for
people
all
the
time.
A
Therefore,
this
particular
solution
is
completely
free
and
it's
very
very
easy
to
use
so
that
artists,
developers
and
creators
of
all
kinds
on
the
web
are
have
a
handy
tool
with
almost
no
code
to
update
from
their
content.
So
that
their
content,
whatever
they
create,
is
reliably
and
redundantly
stored
on
the
web.
A
Therefore,
nfg.storage
provides
you
the
same
opportunity
to
use
ipfs
to
store
your
data
and
it
provides
the
unique
cids
which
you
can
store
on
chin
and
use
as
the
pointer
to
the
content
which
you
have
created,
and
that
becomes
very
handy
when
you
think
about
nfts
in
the
long
term.
This
tool
really
allows
you
to
not
only
rely
on
someone's
storage
provider,
but
really
have
a
persistence
of
your
content
and
not
wrote
the
links
which
you
have
on
ip.
On
the
nfts
which
points
to
the
data
you
created.
There
is
also
a
flick
hosting
solution.
A
It
allows
you
for
to
have
a
fast,
modern
and
censorship-proof
websites
and
web
apps
on
the
open
web.
It
really
builds
on
top
of
ipfs
and
filecoin,
where
you
can
host
your
particular
solution
or
your
website
on
ipfsnotes,
and
it
will
be
served
to
you
directly
from
web
browser,
brave
or
solution
like
this.
It
also
is
very
easy
to
implement
in
your
code.
You
can
just
connect
it
to
your
github
repository.
A
Add
the
build
settings
and
deploy
your
site
on
ipfs,
it's
also
backed
by
the
file
coin,
which
is
a
redundant
solution,
and
it
really
provides
the
opportunity
to
make
sure
that
your
content,
your
website,
is
available
whenever
you
need
it.
One
other
solution
which
I
want
to
talk
with
you
about
is
the
power
gate,
which
provides
you
more
functionality
than
I
than
dot
storage
solutions
and
which
gives
you
the
powerful
ways
to
connect
and
extend
leap,
b2b
solution,
ipfs
and
filecoin.
A
It
bridges
near
and
more
networks
are
coming
soon
and
it
allows
you
to
wrap
the
docker
container
around
ipfs
and
file
code
and
use
for
your
particular
applications.
And
the
last
topic
I
want
to
touch
with
you
today
is
what
to
build
and
believe
me
or
not.
There
is
a
lot,
a
lot
of
things
which
you
can
build
in
web
free,
we're
just
on
the
very
beginning
of
the
web
free
and
there
are
lots
of
opportunities
which
in
which
you
can
develop
projects
with
ipfs
and
filecoin.
A
There
are
common
five
major
points
which
people
can
focus
or
break
down
the
development
in
the
web
free
right
now.
First
of
all,
you
can
definitely
develop
user
and
client
interfaces.
You
can
also
work
on
smart
contracts.
You
can
develop
the
compute
and
consensus
layer
and
there
is
also
a
lot
of
opportunities
on
developing
the
hardware
and
networking
solutions
if
you're
building
with
us
or
generally
building
in
web
free,
there
is
no
need
only
to
build
apps.
There
is
really
this
amount
of
opportunities
to
build.
A
Therefore,
we
are
more
than
happy
to
welcome
you
in
our
ecosystem.
We
have
discord
slack
available
to
you
at
all.
The
time
find
us
on
ipfs
on
filecoin
and
visit
our
amazing
hackathons
and
other
events.
There
was
a
highlight
of
all
the
events.
We
also
run
a
tremendous
number
of
hackathons
each
year,
so
you
can
not
only
build
something
right
now
straight
away
on
your
spare
time,
but
you
can
also
participate
in
awesome
events.