►
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
A
A
Finally,
why
well
we
made
it
because
we
need
it
for
I
give
us,
so
we
need
an
interplanetary
file
system,
really
we
needed
some
form
of
inode
or
block
system,
but
if
you
look
at
and
I
note
or
block
they
just
like
I
know,
it's
point
I
know
it's
going
to
blocks.
So,
at
the
end
of
the
day,
we
needed
an
interplanetary
deck.
I
say
like
some
direct
data,
simply
very
quick.
So
how
did
we
do
this?
Well?
A
First
of
all,
we
need
some
way
of
dealing
with
latency
and
deduplication
for
deal
with
networks,
so
we
use
thing
called
constant.
Addressing
you
probably
aware
of
basically
concert
dressing,
you
have
some
like
global,
unique
in
global,
a
verifiable
name
for
David.
Currently,
we
use
cryptographic.
Hashes
now
actually
have
these
properties.
However,
you
can
use
other
schemes
because
grip
coupling,
which
is
actually
addition
properties,
don't
necessarily
need
also
just
warnings
for
crypto
like
get
me
out.
A
So
first,
we
started
out
with
we
called
the
Merkel
during
the
Merkel.
Dag
is
a
minimal
Merkel,
linked
data
or
directed
acyclic
graph.
Basically,
in
this
system
you
would
have
objects
in
the
data
field
in
a
links
field
where
the
data
just
includes
like
blob
in
your
data
links
just
point
other
objects.
A
This
is
what
a
structure
would
look
like
in
this
merkel
bag.
There
I'm
using
Jason
from
Ava,
but,
like
you
know,
PFS,
we
just
use
binary
and
it's
me
really
painful
to
work
with.
It's
like
you
have
to
know
what
the
data
is
and
you
Syrian.
Why
is
it
which
means
you're,
actually
serious
twice
you
do
serialize
the
Merkel
Dimmick
object,
then
you
just
saw
has
a
PI
PFS
object?
Also,
the
data
section
can't
point
to
anything
because
only
in
linked
skin.
So
you
have
a
separate
section
of
wings
point
of
various
things.
A
It
gets
kind
of
missing
to
deal
with,
but
that's
a
so
then
we
decide.
You
know
what
nobody
need.
Something
more
general,
so
we
came
up
with
I,
peeled
dates:
I
filled
these
structured,
so
I
think
higher
data
structure,
structure,
you're,
not
just
limited
to
this
data
section
and
Link
section
it.
The
entire
data
structure
is
self
describing
so
so
like
you
can
like.
You
can
see.
A
This
gets
built
into
the
object,
so
you
don't
need
extra
maecenas,
it's
a
versioned,
so
the
the
pointers
sort
of
the
punch
addresses
we
use
in
ideally
the
reverse
and
touch
them.
So
we
keep
upgrading
it
to
upgrade
the
entire
system.
The
current
version
is
not,
which
is
painful
per
se,
the
old
version
the
was
painful
to
it.
A
Basically,
this
allows
us
to
like
point
to
get
objects
or
III
ma
and
whatever
by
just
like
saying,
like
in
the
pointer
itself,
we
said
like
what
the
data
type
is
and
until
you
had
to
decode
it
say
we
can
actually
point
to
get
commits
from
ideal
view
and
even
explore
and
get
trees
in
I
ability
and
transmit
get
objects
over
like
I
businesses.
It's
really
quite
cool,
might
activate
suggest
you
take
an
hour
yeah.
So
the
key
part
here
is
the
self
describing
function
identifier.
A
This
is
what
we
call
CID
and
the
components
are,
has
has
a
version.
The
ability
for
Matt
tells
you
could
have
to
understand
the
data
and
then
a
hash
which
tells
you
like
where
the
data
is
it's
a
constant
dress.
An
object
in
the
field.
Ii
would
look
something
like
this:
it
just
has
fields
and
company
there's
a
pointer
to
a
different
object.
For
example,
you
can
actually
recently
come
up
having
you
connection,
resolving
paths
like
this,
where
you
pass
through
/ip
all
these
some
continental
Irish
companies,
like
name
and
get
back
Protocol
labs.
A
So
that's
how
that
works.
We
don't
need
to
go
into
the
details,
so
I
see
ideas,
work
team,
you
can
look
at
this
live
later
and
status.
We
have
basic
equipments
of
my
PFS
because
your
duties
get.
We
were
working
on
new
formats
p.m.
et
cetera,
user
friendliness
and
more
senior
duties,
and
the
next
talk
will
actually
be
about
research.
So
I
won't
cover
that
now.