►
From YouTube: Interview with Juan Benet of IPFS at DEVCON1 in London
Description
IPFS, the Inter Planetary File System, is an ambitious data transfer and versioning system that seeks to deliver a fast scalable architecture for the next generation of the Web. At Epicenter Bitcoin, we covered IPFS on Episode 100: https://www.youtube.com/watch?v=erB7i6Uc4DM
I caught up with Juan at the Ethereum Devcon and delved into the opportunities enabled by combining IPFS and Ethereum. The discussion veered into the following topics:
How IPFS and Ethereum are synergistic - censorship resistant financial logic coupled with a permanent censorship resistant data web.
Opportunities for synergy - storing Ethereum state in IPFS and storing contract data in IPFs.
Challenges with merging Ethereum and IPFS.
Mutability in IPFS.
Current state and future plans.
Check out the video to gain an appreciation of how you could combine these two powerful systems and build great applications!
Links:
IPFS on Epicenter Bitcoin: https://www.youtube.com/watch?v=erB7i6Uc4DM
IPFS whitepaper: https://ipfs.io/ipfs/QmR7GSQM93Cx5eAg6a6yRzNde1FQv7uL6X1o4k7zrJa3LX/ipfs.draft3.pdf
IPFS website: https://ipfs.io/
- Visit our website: http://epicenterbitcoin.com
- Subscribe to the podcast: http://soundcloud.com/epicenterbitcoin/
- Follow us on Twitter: http://twitter.com/epicenterbtc
A
Right
now,
I'm
with
one
who
I
suspect,
could
just
be
the
next
time
honestly
he's
he's.
Building
a
system
called
I
PFS,
which
is
the
interplanetary
file
system.
It's
meant
to
complement
in
HTTP
in
the
beginning,
but
then
it
might
end
up
doing
just
a
lot
more
than
HTTP
and
be
a
replacement
to
it
would
also
be
replacement
to
it.
So
one,
let's
have
your
introduction.
First,
my.
B
A
So
so
far
our
listeners,
we
already
have
an
episode
from
one
on
episode,
a
Bitcoin.
You
recommend
you
to
go
and
watch
it,
because
it's
it's,
it's
really
good
and
it
really
clears
up
a
lot
of
things
about
the
future
of
the
of
the
web
in
general.
So,
right
now
we
will
focus
specifically
on
the
combination
of
I
PFS,
any
Syrian,
because
a
lot
of
developers
seem
to
be
building
on
it.
So
one
what
kinds
of
projects
have
you
seen
at
the
DEFCON
during
that
combined
I,
PFS
and
athyrium
yeah.
B
Actually,
a
lot
so
I
got
it
so
I
spoke
on
on
Monday
kind
of
about
I
professed
generally
and
I
included
some
examples
there.
So
they
vary
between
applications
that
are
built
with
athyrium
that
have
some
other
component
outside
and
they
are
usually
using
I
PFS
to
address
all
of
their
content
and
to
distribute
all
of
their
content.
B
There
is,
there
are
the
most
interesting
use
cases,
for
me
at
least,
are
when
so
one
of
them
is
when
people
are
actually
using
smart
contracts
that
address
objects
in
ipf
s
and
when
people,
when
the
etherium
chain
itself,
both
the
state,
the
Merkel
Patricia
state
tree
and
the
entire
theorem
chain,
can
be
layered
over
IP
FS
and
can
be
made
into
I
PFS
objects.
And
so
that's
something
that
we've
been
talking
about
and
discussing.
I've
been
discussing
with
a
core
team
for
Question
Time
already
in.
That
is
an
interesting
thing
for
the
future.
B
It's
not
clear
how
a
will
be
done
on
whether
it
be
done,
but
that
is
a
very
appealing
way
to
layer
the
projects
together
and
leverage
the
strengths
of
ipf
s4
athyrium.
One
thing
that
if
your
room
notes
would
get
is
the
ability
to
use
to
address
a
theorem
content,
both
contracts
or
state
in
the
state
tree
or
change
the
chain
itself
like
elements
of
the
chain
itself
and
create
links
that
link
into
that
the
chain
that
other
I
PFS
nodes
can
understand
that
perhaps
don't
implement
athyrium
specific
stuff.
A
So
so
so,
let's
break
break
down
break
down
these
two.
These
two
examples,
so
the
first
one
is
an
example
where
you
have
a
contract
like,
for
example,
there's
an
artist.
He
he
releases
music
and
he
has
data
about
how
much
he
wants
to
charge
for
that
piece
of
music
on
the
etherium
network
and
on
the
etherium
network.
Somebody
can
pay
this
contract
in
order
to
compensate
the
artist
now.
B
And
the
point
is
like
the
link
that
you
put
on
the
chain
is
an
IP
FS
link,
so
this
is
true
for
both
athyrium
and
bitcoin
and
other
block
chains.
People
are
starting
to
put
links
to
content.
That
is,
you
know,
large
files
that
you
don't
want
to
include
on
the
chain
itself,
and
these
are
necessarily
files
you
could
be.
This
could
be
a
large.
You
know
record
system.
B
So,
if
you
put
a
URL
or
you're
right
into
a
blockchain,
it
might
not,
if
you
put
a
URL,
it
may
not
survive.
You
know
a
hundred
days
or,
however,
whatever
the
mean
lifetime
of
a
website.
Is
these
days
you,
our
eyes,
are
better'n
I
PFS
links
are
your
eyes,
but
it
gives
you
a
nice
way
to
resolve
all
these
links
because
we
people
were
doing
before
was
just
putting
hashes
into
the
chain,
and
these
hashes
are
just
hashes
like.
Where
do
you
look
them
up?
A
B
There's
the
second
example
so
Christian
from
consensus,
build
persona
and
persona,
puts
the
profiles
and,
like
all
of
the
data
on
I
PFS,
so
they
have
a
set
of
ipf
us
notes
and
they
back
up
the
persona
content.
And
but
it's
all
addressed
with
ipf
s.
So
you
could
add
your
own
node
and
help
back
it
up
and
eventually
there'll
be
some
incentive
layer
to
get
nodes
to
distribute
that
data
as
well.
A
Now,
let's
go
into
this
scenario
where
actually
a
smart
contract.
So,
let's
say
let's
say:
there's
a
profile:
data
on
I
PFS
through
the
persona
system
and
the
smart
contract
is
structured
in
a
way
that
when
a
certain
transaction
hits
the
smart
contract,
it
wants
to
make
a
change
to
this
data
item
on
I
PFS.
So
it
wants
to
actually
transform
that
data
item
from
a1
to
a2
and
link
it
with
with
that.
First
of
all,
you
do
something
like
this
I.
B
Believes
you
can
yeah
I,
think
that
so
I
don't
know
if
the
smart
contract,
the
citizen
now
can
mutate
any
state
beyond
the
state
tree
I'm,
not
a
hundred
percent
sure
about
that.
It
was
in
FN
discussions
early
on
where
that
was
a
possibility,
but
it
may
be
that
the
AVM
right
now
is
just
pure
and
there
it
can
do
no
io
beyond
its
own
state
tree,
but
you
could
totally
see
that
being
a
trivial
addition,
like
you
could
add
certain
up
codes
that
mutate
state
on
I
PFS.
A
And
suppose
a
contract
for
its
functioning
depends
on
some
data,
which
was
on
I
PFS,
so
there
might
be
a
contract
that
does
one
action.
If
this
deeper,
the
gender
of
a
purse
of
a
profile
on
persona
is
male
and
some
other
thing
if
the
gender
is
female.
Now,
if
you
have
a
contract
like
that,
it's
not
trying
to
change
the
data
on
I
PFS,
but
it's
just
acting
on
some
data,
one
that
is
on
I
PFS.
Then.
B
Believe
that's
the
case.
I
have
to
look
carefully
at
how
the
personal
contracts
are
set
up,
but
I
believe,
like
the
addresses
that
are
stored
into
the
contracts
are
pointers
to
are
basically
address.
Ip
addresses
so
yeah.
It
can
manipulate
it's
just
a
string
at
the
end
of
the
day
right.
So
you
can
manipulate
strings
I.
Don't
think
that
the
evm
itself
can
load
data
from
my
because
yet
it
might
be
able
to
Roger
so.
A
B
A
This
kind
of
kind
of
yeah,
so
this
actually
leads
to
the
other
other
application
you
are
talking
about,
which
is
to
basically
remove
this
barrier
between
the
etherium
state
state
tree
and
and
the
IPF
esmeralda
all
together
and
have
the
etherium
state
tree
as
a
part
of
the
I
PFS,
multiple
diagram
itself.
That
would
be
the
ultimate
thing,
because
then
a
contract
could
basically
refer
to
anything
else
that
exists
on
the
on
the
IPS.
B
So
that's
an
extremely
powerful
use
case
where
you
suddenly
get
the
ability
to
reference
any
data
on
the
network
itself
and
act
upon
it
from
the
EVM.
So
the
EVM
can
then
create
references
to
objects
that
are
outside
of
its
normal
state
tree
and
that
are
linked.
I
mean
you
can
think
of
these
as
like
git
repositories
or
even
even
other
block
chains
like
you
could
address
objects
on
Bitcoin
or
some
other
block
chain
or
the
web
itself
right.
So
there's
a
lot
of
websites
that
are
now
being
distributed.
B
I
PFS,
there's
people
creating
websites
and
web
apps,
where
the
data
models
of
the
of
the
application
are
just
nodes
in
the
I
PFS
graph.
So
you
can
now
have
a
way
to
address
all
of
that
content
and
manipulate
it
with
with
the
evm,
even
if
it
wasn't
initially
constructed
as
part
of
the.
If
it
wasn't
it,
it
wasn't
initially
and
a
theorem
application,
it
can
now
become
one
which
might
be
a
powerful
way
of
increasing
adoption.
So.
A
How
would
that
work?
So
in
a
sense
today,
when
you
I
want
to
an
idiom
full
note,
I
have
to
download
gets
from
from
github
and
it
it
basically
starts
a
full
node.
It
connects
to
other
nodes
in
the
theorem
Network
fetches
data,
so
instead,
so
gates
would
basically
have
an
IP
FS
module
inside
it.
So
when,
as
soon
as
I
start
guess,
I
PFS
is
initializing
the
background
and
it's
trying
to
gather
all
the
data
and
just
as
it
pulls
each
helium
transaction
data
from
the
network
it
also
starts
pulling
in.
B
Could
be
whatever
is
linked
to
right,
so
you
could
potentially
create
something
like
bit
helps
a
bit
hub.
Was
this
program
a
while
back?
That
was
a
bot
that
would
tip
people
with
Bitcoin,
so
it
had
a
it
had
a
fund
and
it
would
tip
people
with
Bitcoin
for
every
commit
they
did
Tory
passare.
So
if
the
commit
got
merged,
then
people
could
claim
some
reward
and
that
reward
which
is
sent
to
them
is
a
Bitcoin
transaction,
and
this
was
a
program
that
someone
had
to
run
and
you
had
to
run
this
bot
right.
B
But
you
could
just
do
this
as
it's
not
smart
contract
on
a
theorem
itself
like
you
need
to
not
run
no
infrastructure,
but
then
the
interesting
part
would
be
being
able
to
do
this
as
just
a
contract
manipulating
the
graph
and
checking
the
commits
themselves
without
those
commits
being
part
of
the
theorem
state
tree
there.
You
know
part
of
a
get
in
the
part
of
github
or
whatever,
but
now
the
theory
vm
could
load
those
up
and
manipulate
them.
So
yeah.
A
A
B
B
B
Bitcoin
had
to
again
implement
its
own
hope,
your
peers
things
if
your
room
the
same
stuff.
So
all
these
different
webs
are
starting
to
emerge
again,
but
these
webs
are
different.
They
they're
not
just
hypertext
systems
like
the
old
days.
These
are
hyper
hyper
set
media
systems
where
the
links
are
actually
merkel
links.
These
are
links
that
are
addressed
by
hash,
so
their
content
address
links,
but
all
of
these
data
structures
and
networks
have
the
same
property
in
mind.
B
Look,
you
could
have
that
or
why
is
it
that,
like
eh
yeah,
you
should
be
able
to
like
create
a
contract
that
causes
people
to
become
seeds
on
the
Victorian
network
or
that
causes
people
to
like
distribute
files
on
I,
PFS
right,
and
so
all
of
that
could
be
possible
if
we
start
adopting
like
one
common
way
of
linking
between
the
systems
yeah
one's
shine,
we
should
have
one
web
right
like
we
shouldn't
have
multiple
labs.
We
should
have
one
web
where
you
can
address
anything
from
any
other
place:
solo.
A
That
seems
like
a
very,
very
great
idea,
but
so
let's
also
say
that
I
BFS
is
also
taking
a
position
on
how
data
should
be
moved
across
across
physical
networks
across
the
web
right.
So
you
have
this
bit
swap
protocol
to
move
BitTorrent
like
based
on
BitTorrent
you,
you
have
a
way
of
moving
data
across
the
face.
B
Yeah,
well,
we
don't.
We
don't
claim
that
that's
the
only
way.
So
the
thing
about
I
PFS
is
that
it's
a
very
modular
protocol
that
there
are
some
problems
we
have
to
solve
right.
We
have
to
be
able
to
move
the
content
and
so
on,
and
so
we
have
some
protocols
for
that,
but
I
bffs
itself
is
designed
so
that
you
can
swap
out
all
those
pieces.
B
But
it's
going
to
be
called
lip.
P2P
nvidia
is
to
create,
like
one
central
place
where
we
can
write
all
the
different
period
of
your
protocols,
because
there's
a
lot
of
use
cases
where
you
know
one
use
case
is
not
going
to
match
every
other
use
case,
and
one
solution
to
that
use
case
is
definitely
not
going
to
be
the
same
across
the
board
right.
B
So
some
applications
want
to
work
globally
and
are
fine
using
a
DHD
and
so
on,
but
other
applications
weren't
want
to
work
inside
of
a
data
center
and
they
need
really
fast
resolution
times
and
they
need
to
be
able
to
move
content.
You
know
less
than
a
second
like
really
we're
talking.
You
know
tens
of
milliseconds
and
we're
dealing
with
tens
of
milliseconds.
B
You
can't
afford
to
go
across
the
network,
so
ADHD
doesn't
make
any
sense
in
that
case
or
like
a
DHD,
that's
global
doesn't
make
any
sense,
and
so
for
those
kinds
of
use
cases
you
need
a
protocol
that
is
able
to
have
modules
that
can
be
swapped
out
by
the
people,
building
the
applications
on
top
of
them,
but
are
using
the
the
node
and
I
BFS.
Is
such
a
system?
It
allows
you
it
is
well
layered.
This
is
an
idea.
B
Let's
pick
one
middle
layer,
that's
very,
very
simple,
and
that's
just
a
way
of
defining
the
data
to
have
merkel
links
such
that
you
can
create
a
path
traversal
over
them
over
that
graph
and
then
create
room
for
all
of
these.
These
peer-to-peer
systems
to
be
plugged
in
and
for
you
to
be
able
to
choose
what,
whichever
one
makes
sense
for
your
application,
whichever
one
satisfies
your
requirements
and
constraints
without
forcing
you
to
use
one
that
doesn't
at
all
yeah,
so.
B
A
Let's
say,
let's
say
this
is
next
thing
comes
on,
I,
don't
know
how
intergalactic
something
I
don't
know
compared
to
move
data
along
that
doesn't
matter
to
I
PFS
or
to
Ethie
Liam
if
they
put
all
their
state
tree
into
I
PFS,
because
that
new
system
can
the
old
bowl
make
way
of
moving
data.
A
night
I
PFS
can
really
move,
and
you
can
swap
in
this
new
system
and
the
the
whole
permanent
web
keeps
yep
on
without
er.
Exactly.
B
Right
keeping
the
heartbeat,
we
already
have
this,
where
there
are
groups
of
people
making
private
networks,
private
IP,
FS
networks
that
have
different
routing
protocol,
so
so
they
don't
use
the
global
tht
they
use
either
they're
only
hg,
that's
lets
you
know
smaller
or
something
or
they
use
other
routing
protocols,
and
so
these
yeah
discovery,
routing
and
distribution.
Like
the
exchange
part.
All
of
these
are
layers
that
people
can
write
and
systems
for
and
plug
them
in
easily.
B
A
So
big,
what
kind
of
future
invention
can
so
like
I
PFS
today
from
the
from
the
perspective
of
the
peer-to-peer
community,
it
seems
like
a
very
great
idea,
because
it's
like
in
like
in
this
integrated
system
that
can
handle
all
of
these
peer-to-peer
applications
into
one
like
what
kind
of
future
invention
can
can
break
this
and
say:
okay,
we
are
not
satisfied
with
ipf
s
anymore,
and
something
is
it.
Is
it
so
fundamental
right
that
would
have
to
be
a
better
way
of
storing
data
right?
Well,.
B
B
So
in
a
sense,
these
are
these
aren't
systems
that
replace
each
other
wholesale.
These
are
systems
that
start,
collaborating
and
and
complementing
each
other
and
over
time
are
used
by
different
kinds
of
systems
right.
So
if
you
look
at
HTTP
pages,
many
of
them
include
links
to
FTP,
and
many
of
them
include
links
to
bittorrent,
and
many
of
them
include
links
to
a
whole
bunch
of
other
systems,
and
the
whole
point
is
to
have
a
web
that
can
address
every
kind
of
system
out
there.
This
is
not
ipms
idea.
This
is
an
old
idea.
B
This
is
Tim
berners-lee's
idea
about
creating
one
unified
web.
We
were
just
extending
that
unified
web
to
a
whole
class
of
protocols
that
weren't
that
required
a
different
kind
of
distribution
mechanism
that
were
more
peer-to-peer
that
were
decentralized
that
were
that
you
smirk,
linking
as
the
core
basic
idea
yeah.
A
So
so
one
of
the
one
of
the
components
of
I
PFS
that
sort
of
came
a
little
later
is
the
idea
is
it
was
in
there
in
the
design
from
the
beginning,
but
that
was
implemented.
Perhaps
a
bit
later
was
mutability.
The
idea
that
I
can
give
a
link
to
somebody
like
I,
p,
NS,
/,
something,
and
that
always
goes
to
a
single
page,
but
that
page
could
keep
changing
over
time.
Yeah.
B
So
basically,
the
the
core
I
PFS
data
structure
is
a
Merkel
linked
data
structure
which
is
immutable
kind
of
like
get
underneath.
The
hood
has
a
bunch
of
immutable
objects,
but
you
still
want
to
be
able,
and
so
you
can
hand
out
references
to
people
that
are
that
are
always
going
to
be
pointing
to
that
file,
and
so
nobody
can
change
it.
Those
are
immutable.
Now
you
also
want
to
be
able
to
hand
out
references
and
links
to
that
point
to
a
mutable
file
that
changes
over
time.
That
you
know.
B
Today's
is
a
web
page
that,
like
a
blog
right,
for
example,
like
you
have
a
blog
and
I,
could
have
one
message
today
and
I:
give
you
the
URL
to
that
blog
or
that
you
are
right
to
that
blog
and
tomorrow
you
can
check
it
and
there's
another
post
there
right.
Without
that
name,
changing,
and
so
the
point
here
is:
how
can
you
do
that
in
a
decentralized
way,
and
so
the
the
construction
of
I
pns?
B
If
you
were
looking
up
for
you
know
food
calm
on
DNS,
you
run
a
DNS
resolver
that
goes
and
talks
to
other
DNS
servers
and
gets.
You
know
some
record
that
tells
you
where
you
know
it
gives
you
an
IP
address
for
food
com.
The
DNS
system
has
some
authentication
system,
but
it's
different
from
this
one.
So
the
idea
here
is
when
I
give
you
the
name,
it's
actually
the
hash
map
of
public
key,
which
means
that
the
only
people
capable
of
changing
that
name
must
control
the
private
key.
B
So
it's
a
way
of
giving
you
a
naming
authority
that
is
cryptography
itself.
So
it's
not
mediated
by
anything
except
cryptography.
You
don't
have
to
register
any
name.
You
don't
have
to
like
pay.
Anyone
or
anything
you
just
create
a
public/private
key
pair
now.
The
thing
about
that
is
that
it's
not
human
readable.
So
it's
not
a
nice
and
memorable
name.
So
you
know
that
that
doesn't
it's
not
very
nice.
You
have
to
copy
paste
these
hashes,
but
the
benefit
is
that
you
don't
I
in
you,
don't
have
to
register
anything.
B
You
can
just
create
them
entirely
distributed.
So
you
could
have
a
register.
You
don't
need
a
registry
that
centralized
right,
so
all
name
registries
knee
require
the
form
of
consensus
to
clear
them
right.
So
whether
you're
registering
a
name
through
you
know
the
DNS,
registrar's
or
you're,
registering
a
name
on
etherium
or
you're,
registering
a
name
on
bitcoin
and
so
on.
There
is
a
central
body,
that's
doing
the
allocation
of
names,
even
though
bitcoin
and
etherium
are
decentralized
networks.
B
You're
still
participating
in
a
central
system
that
allocates
the
namespace,
and
that
is
is
good
to
be
able
to
do
human
readable
names.
But
if
you
don't
require
human
readable
names,
you
can
create
a
pointer
and
just
do
it
entirely
decentralized
and
like
really
honestly,
completely
decentralized,
you're,
just
mediated
by
physics.
Right
and
like
that's
a
very
kind
of
appealing
way
of
doing
names
right,
you
don't
have,
and
so
this
is
something
you
absolutely
need
to
be
able
to
do
names.
B
You
know
like
we
mentioned
before
across
planets,
because
if
you
had
a
registry
that
took
like
sinking
across
planets
before
you
could
register
a
name,
then
you
would
have
a
key
huge
lag
time
before
you
could
actually
get
a
name.
I
guess
like
dns
is
actually
so
bad
that
the
dns
register
system
is
so
bad.
That
is
worse
than
if
you
had
to
let
go,
send
messages
to
Mars
and
back.
But
you
know
today
you
can
register
our
name
on
a
theorem
in,
like
you
know,
a
block
time
right.
B
So
it's
super
fast
I
guess
is
to
block
times
I
think
maybe
silicon's,
but
whatever
its
you
can
register
names
extremely
quickly
and
you
can
also
register
names
on
Bitcoin
as
well
and
again
it's
super
fast
way
better,
but
it's
centralized.
And
so,
if
you
wanted
to
have
a
blockchain
on
Mars
or
you
know
some
area
that
is
disconnected
from
the
backbone,
so
you
can't
reach
the
Bitcoin
network
like
then
you
couldn't
register
a
name
and
that's
an
issue
right
and
so
I
pns
is
there
as
a
layer
of
indirection.
B
It's
been
live
for
a
while,
and
people
are
using
it.
We
still
are
we're
still
not
recommending
people
rely
on
it
yet
because
we
are
working
on
a
whole
bunch
of
optimizations
around
it
and
increasing
that
consistency
and
a
whole
bunch
of
issues.
But
it
is
there
and
you
can
play
with
it,
and
you
can
check
it
out
and
yeah.
So.
B
B
You
can
write
a
website,
one
I,
PFS
and
ship
it
and
then
give
people
and
address,
and
that
address
will
first
tell
them
to
download
this
JavaScript
implementation
and
then
load
everything
through
our
PFS,
but
the
user
will
not
have
to
install
anything
like
it'll.
The
brass
rail
just
do
everything
so.
A
B
B
Team
yeah,
so
you
can
you
can
the
website
for
I
PFS
is
ipf
SEO
and
you
can
come
talk
to
us
on
github.
You
can
file
issues
there.
It's
really
a
very
open
and
active
community.
You
can
also-
and
we
have
tons
of
repositories-
lots
of
really
interesting
collaborations
with
lots
of
other
groups
and
we
have
a
very
active
IRC
channel.
B
So
if
you,
if
you're
old
school
like
us,
you
can
before
before
slacked
up
over
all
the
centralized
communities
you
can
log
on
IRC
and
come
to
pound
I
PFS
on
freenode,
and
you
can
talk
to
us
there
by
the
way
yeah,
if
you,
if
you
were,
have
a
decentralized
attributed
project
and
you're
using
slack.
You
should
think
twice
about
that.
B
That's
true!
But
anyway,
I
actually
really
like
select
the
product
is
very
good
I.
Just
don't
like
that.
It's
a
centralized
system
that
doesn't
have
end-to-end
encrypted
data
and
it's
actually
a
huge
honey
pot
for
hackers
that
are
going
to
come
in
and
steal
all
your
data
from
slack
servers.
So
good.
B
Exactly
and
if
you're
not
part
of
the
slack
team,
please
like
just
give
us
authenticated
into
an
encryption
and
let
us
host
around
nodes,
and
just
have
us,
pay
you
for
the
software.
You
can
totally
make
one
ins
with
anyone.
It's
another
whole
other
thing,
I
guess
one
less
thing
to
say
is
I
have
seen.
So
I
came
to
give
this
talk
about
I,
PFS
DEFCON,
because
a
lot
of
people
are
using
IP
FS
in
the
theorem
networking
community,
but
I
was
extremely
impressed
by
by
just
how
popular
it
is.
B
I
didn't
know
that
so
many
projects
were
depending
on
it,
and
so
that's
that's,
really
exciting
and
cool,
and
so
I
guess
as
a
message
out
to
all
of
the
theorem
community
like
if
you
find
any.
If
you
have
any
features
that
you
want
any
any
anything
just
please
come
come
and
tell
us
and
we'll
we'll
improve
the
stuff
for
you
and
yeah
yeah.
That's
all
I,
great,
really
cool.
All
social
systems
are
addressing
stuff
when
I
PFS,
like
from
the
persona
so
that
I
mentioned
people
are
soaring
like
music
and
video
files.