►
From YouTube: IPFS at Infura: A Web3 Development Suite - Mike Godsey
Description
Mike Godsey presents this overview of the past, present, and a brief glimpse of the future for IPFS at Infura. IPFS is an essential part of the Infura Web3 development suite and we will talk about why we started to support it, how developers use it today, and what's to come.
Read more about the inaugural IPFS Pinning Summit on the website: https://ipfspinningsummit.com/
For more information on IPFS
- visit the project website: https://ipfs.io
- or follow IPFS on Twitter: https://twitter.com/IPFS
Sign up to get IPFS news, including releases, ecosystem updates, and community announcements in your inbox, each Tuesday: http://eepurl.com/gL2Pi5
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
A
My
name
is
Mai
Godsey
I'm,
the
GM
at
and
fira
were
a
product
inside
of
the
consensus
family,
so
very
happy
to
be
here.
Also,
thank
you
for
having
us.
You
know
we
have
we've
been
committed
to
ipfs
for
for
almost
four
years
now,
and
it
is
it's
been
such
a
core
part
of
our
product
and
working
with
the
protocol.
Labs
team
has
always
been
such
a
pleasure.
A
So
that
meant
offering
a
standard
API.
That
was
exactly
the
same
as
if
you
were
right
running
your
own
aetherium
nodes.
This
made
it's
super
easy
for
interoperability
and
just
kind
of
getting
the
infrastructure
out
of
the
way
of
the
developer,
so
that
they
could
build
really
fast
and
really
cool
experiences.
So
this
this
proved
to
be
really
a
awesome
thing
for
developers.
A
It
really
showed
its
value
very
early
on
and
it
has
been
growing
and
continuously
ever
since
that
we
we
officially
launched
at
DEFCON
2
with
metamath
being
one
of
our
first
use
cases
early
adopters
and
it
was.
It
was
a
really
awesome
combination
of
here's
your
window
into
experiencing
this
web
3
technology
and
and
and
having
the
confidence
that
it's
running
on
infrastructure
that
that
really
it
was
bulletproof.
A
A
If
we
can
make
building
on
aetherium
as
easy
as
possible,
then
we
can
help
push
this
new
era
of
the
internet
forward
and-
and
this
was-
and
so
this
really
became
our
core
mission
statement
of
we
want
to
deliver
the
absolute
best
infrastructure
and
developer
tools
for
people
to
to
build
web
3
applications
and
and
and
this
mission
statement
kind
of
led
us
to
a
question
of
ok.
You
know,
web
3
is
broad
and
an
application
requirements
is
equally
as
broad
and
so
it
you
know,
etherium.
B
A
So
we
we
really
wanted
to
kind
of
to
meet
this
entire
package.
So
you
could
go
to
one
place
and
really
have
this,
this
the
tools
to
build
this
distributed
application,
and
so
we
set
up
one
of
the
very
first
gateway
and
API
services
and
and
ever
since
then,
we've
seen
a
ton
of
developers
using
the
service
asking
us
questions
about
it
and
always
kind
of
growing
together
around
you
know
what
people
need,
how
they
need
to
access
it.
A
What
the
issues
with
it
are
and
kind
of
exploring
the
the
spectrum
of
use
cases
with
this
awesome
community.
So
when
we
launched
this,
we
decided
that
you
know
this
was
going
to
be
free.
Just
like
our
aetherium
API,
we
thought
that
getting
developers
to
start
building
on
this
was
was
the
right
first
step
and
then
moving
towards
offering
additional
value.
On
top
of
that,
that
developers
were
really
gonna
want
to.
You
know,
spend
money
on,
and
so
so
this
kind
of
takes
me
to.
Where
are
we
now?
A
A
A
So
this
basically
meant
that
we,
since,
since
the
inception
of
this
feature
and
support,
it
was
super
important
to
us
to
maximize
people's
ability
to
experiment
on
this
technology,
and
so
so
we
left
it
open,
authentication
to
really
Drive
that
experimentation
and
and
we've
seen
such
cool
use
cases
built
on
top
of
it
because
of
that
and
and
and
researchers
and
education
programs,
and
all
of
these.
These
early
ecosystem
necessities
were
able
to
build
on
top
of
this
and
really
push
the
adoption
forward.
So
we
have
our
full
documentation
at
and
fear
that
I.
A
So
this
is
a
command-line
tool
to
be
able
to
copy
data
between
ipfs
nodes,
cluster
or
storage,
so
makes
it
extremely
easy
to
to
shift
data
from
node
to
node,
affirm
cluster
to
cluster
or
any
other
type
of
storage
solution
that
you
have
for
your
your
Gilad
PFS
client
and
then
the
other
tool
that
we
built
is
our
Go
ipfs
data,
plugin
and
so
I'll
talk
a
little
bit
more
about
this
in
in
the
next
couple
slides.
But
you
know
we
we
cut
out
of
the
the
inferior
team,
comes
from
heavy
background
of
infrastructure,
sre.
A
So
what
it's
so
so
a
few
few
numbers
everyone
likes
numbers,
so
we
have
over
forty
million
unique
objects,
currently
supported
on
our
service.
So
to
be
to
be
clear,
that
pinned
pinned
data
and
objects
are
a
bit
different
because
pin
data
can
be
broken
down
into
multiple
objects
for
for
more
efficient
storage.
A
So
the
you
know
the
more
exciting
went
on
here
is:
we
have
over
two
terabytes
of
data
transfer
every
single
day,
so
there's
two
over
two
terabytes
of
data,
either
being
added
or
being
accessed
through
our
service
every
single
day,
and
this
has
been
consistent
for
years
now,
and
then
we
have
what
like
I
said.
Part
of
our
you
know.
Our
mission
is
to
to
be
contributing
to
these
open
source
libraries
that
build
this
ecosystem,
and,
and
in
that
mission
we
we
had
25
plus
unique
contributions
and
PRS
to
the
the
version.
A
Oh
dot,
five
of
Go,
ipfs
and
and
a
lot
of
these
were
a
lot
of
these-
were
around
performance
and
bug,
fixing
or
usability
enhancements
of
domains
and
data
storage,
pinning
and
the
DHT.
So
we're
our
our
team
is
deeply
passion
about
in
improving
and
offering
this
service
for
everyone
in
the
ecosystem
and-
and
this
is
really
been
possible
because
of
our
contract.
A
Our
collaboration
with
the
protocol
labs
team,
they're
engineering,
a
group
for
LIGO
ipfs,
client
they're,
their
communication
with
us-
has
been
absolutely
stellar,
they're,
always
extremely
easy
to
get
in
touch
with
we're
iterating
with
them
all
the
time
on
on
improvements
in
the
client
and
and
metrics
that
were
seeing
from
an
operational
standpoint.
So
this
is.
This
has
been
a
really
critical
partnership
for
us
to
offer
this
service.
A
B
A
So
that's
that's
basically
zooming
in
on
the
client
and
going
what
are
the
core
systems
here
and
then
splitting
those
out
to
be
cloud
optimized,
so
that
we
can
not
only
individually
optimize
and
scale,
but
we
can
individually
operate
and
and
monitor
each
of
these
unique
systems
so
that
we
can
hone
in
on
issues
or
operational
problems
that
we're
seeing
in
real
time,
24/7
and-
and
so
this
is.
This
has
led
us
to
having
shared
services
across
multiple
nodes.
A
So
we
run
a
kind
of
a
number
of
mole
of
ago
IPS
clients,
those
have
services
that
they
share,
that
kind
of
increase
the
data
resiliency
for
our
users
and
allow
it
to
scale
really
easily
up
and
down,
and
so
one
of
the
really
cool
systems
that
we
have
is.
It
is
a
standalone
system
for
public
data
on
the
DHT,
which
makes
it
much
much
more
performance
rich
for
getting
data
to
and
from
the
peer-to-peer
network.
So
this
is
that's
been
a
really
awesome
system
that
we're
really
excited
to
release
here
soon.
A
A
We
are
actively
in
discussions
with
the
protocol
labs
team
about
how
all
of
the
interesting
ways
that
we
can
utilize
file
coin
inside
of
our
infrastructure,
we're
exploring
direct
ways
to
connect
our
current
offering
with
file
coin
rock
we're
exploring
fake
file
coin
functionality
that
would
be
separate
from
our
ipfs
functionality,
and
so
this
is
all
still
very
much
in
progress.
But
I
wanted
to
mention
it
here,
because
it's
it's
super
important
to
us
and
and
we're
very
excited
and
looking
forward
to
sharing
more
about
that
with
the
community
soon.
A
So
that
is
kind
of
that's
a
that's
a
brief
looking
to
into
where
we
are
and
where
we're
going.
We
have
a
really
awesome
community
at
community
about
in
Furio,
we've
got
developers
in
there
every
single
day
asking
questions
talking
about
ipfs.
Talking
about
that
aetherium
talking
about
how
they're
connecting
ipfs
and
aetherium
so
definitely
go.
There
can
contribute.
A
If
you
have
questions,
if
you
have
specific
features
that
you're
interested
in
or
functionality
or
or
if
you
have
a
use
case,
that
you're
just
like
man,
it
would
be
so
awesome
if
you
could
help
me
support
this.
Just
reach
out
to
us
were
we're.
We're
super
responsive
I
personally,
am
in
the
community
all
day
every
day
talking
to
people
so
definitely
reach
out
and
thanked.
C
A
B
Yeah
yeah
I
can
admit
cool,
hey
everybody,
yeah
one
thing
that's
been
interesting
is
the
the
very
yeast
cases
that
people
have
had
for
pinning
ipfs
data,
and
you
know
early
on.
We
didn't
support
different
things
right,
so
maybe
we
expected
people
to
be
deploying
static
sites
so
that
all
of
a
sudden
somebody
was
building
like
a
chat,
server
implementation
on
top
of
it
or
all
of
a
sudden.
B
Somebody
was
trying
to
build
distributed
database
on
top
of
it
and
the
things
that
that
pop
up,
when
you
realize
that
are
our
assumptions
with
how
people
were
going
to
be
consuming.
Data
from
this
API
didn't
really
hold
up
and
then
how
you
adjust
to
that
and
then
and
then
yeah,
just
just
the
different
scaling
issues
that
had
come
up
when
you
know
some
things
that
kind
of
stand.
The
other
is
because
we
didn't
have
authentication
on
our
API
early
on.
B
We
didn't
always
know
who
was
using
our
API
and
where
this
new
traffic
source
was
coming
from
so
I.
Remember,
specifically,
Wendy
Teebs
started
sending
us
a
bunch
of
traffic
and
we're
like.
Why
did
all
of
a
sudden
our
data
transfer
just
explode
right,
and
so
you
know
those
are
fun
problems
to
solve,
and
then
there
was
one
other
one.
I
disappoint,
yeah.
Those
are
the
first
couple.
They
come
to
mind.
C
That's
awesome.
Definitely
definitely
it's
a
good
sort
of
problem.
Like
whoo,
we
had
some
things
we
probably
would
have
fixed
before
before
we
hit
this
10x
increase
if
we'd
known
about
it
ahead
of
time.
So
one
of
the
exciting
challenges
about
working
in
distributed
distributed
systems.
Suddenly
you
get
a
lot
of
traffic
question
it
from
about
DMCA's
or
other
take
down.
B
Yeah,
we
have
only
gotten
a
couple:
I'm
surprised.
We
haven't
gotten
more.
My
my
wife
works
for
a
studio
in
in
deals
with
anti-piracy
and
things
like
that
and
knowing
the
types
of
things
that
the
types
of
tools
that
she
has
available
to
herself
or
you
know,
managing
these
types
of
relationships
with
content,
publishers
and
providers.
I
think
it's
something
that
we
as
a
community
can
try
to
get
ahead
of
and
provide
those
because
it's
it's
going
to
come
as
people
start
posting
more
and
more
content
to
to
this
network.
C
A
A
B
Nothing
that
things
could
spawn
off
the
top
of
my
head
in
terms
of
tooling,
though
I
really
feel,
has
been
lacking.
Definitely
the
developers
support
from
the
core
development
team
has
been
really
essential.
When
you
know
we
run
into
issues
with
you
know,
performance
on
the
DHT
side
or
strange
behavior
of
nodes
that
we're
seeing
in
production
just
really
having
that
communication
leave
with
what
the
core
development
team
has
been
really
valuable.
I'd
have
to
think
more
about
a
specific
tool.
B
A
Is
that
the
the
number
one
things
that
that
new
people
into
the
ecosystem
is
education
and,
and
so
really
kind
of
you
know
the
more
and
more
is
the
ecosystem
that
we
can
work
together
to
to
provide
learning
material
on
on
how
to
use
this
and
why
to
use
it.
An
interesting
use
cases
for
it
that
that
is
kind
of
where
we're
we're.
A
Shifting
a
ton
of
our
focus,
especially
on
the
marketing
side,
away
from
kind
of
traditional
marketing
and
and
and
much
more
towards
kind
of
top
of
the
funnel
education
really
teaching
people
that
the
power
of
these
tools
and
so
a
ecosystem.
Why
not?
Even
just
you
know
the
development
teams
at
protocol
labs,
but
just
as
it
as
an
entire
ecosystem
I
think
it's
going
to
be
our
our
responsibility
at
the
forefront
of
this
to
to
really
teach
people
the
breadth
of
these
tools.