►
From YouTube: NFT.Storage - NFTUp - Chris Anderson
Description
Upload files and directories with NFTUp!
A
Let's
see
my
team
at
dag
house,
we
built
a
bunch
of
developer
tools
and
then
the
nft
world
came
along
and
realized
that
the
verifiable
content
identifiers
that
are
built
into
ipfs
are
perfect
for
putting
nft
references
on
blockchains
and
basically
blessed
us
as
the
right
answer
for
nfts.
So
we
went
and
built
a
bunch
of
tools
around
that
which
I'll
show
you
at
the
end
of
my
talk,
and
we
took
what
we
learned
from
those
tools
and
you
built
a
platform,
web3
storage.
A
A
So
that's
what
I'm
going
to
be
showing
now
and
again
tomorrow
in
the
201
track
me
and
Alan
Shaw
are
going
to
be
giving
the
long
version
of
this
talk
where
you'll
actually
get
you
know,
run
npm,
install
and
saturate
the
network
and
all
that
good
stuff
and
so
I'm
going
to
go
over
instead
of
through
some
of
this
stuff.
But
you're
welcome
to
scan
QR
codes.
This
one
links
to
GitHub.
A
A
We're
going
to
focus
mostly
on
the
upload
API
in
the
workshop
tomorrow.
I'll
talk
about
the
various
apis
that
we've
got
so
W3
up
is
our
beta
upload
API.
If
you
go
on
our
website,
you're
not
going
to
see
this
stuff
listed,
this
is
all
beta,
so
W3
up
allows
you
to
upload
directly
from
the
browser
the
mobile
device,
with
the
verified
token
that
we
give
you
and
your
upload
goes
directly
to
the
cloud
without
Crossing.
Through
your
servers,
it's
verifiable.
A
A
So,
as
I
mentioned
before,
the
tools
that
we
build,
allow
you
to
write,
applications
that
can
run
on,
you
know
lots
of
different
vendors
and
the
reason
that's.
The
case
is
because
we
use
open
protocols
like
ipfs,
which
everyone
here
is
familiar
with,
but
also
like
dids,
which
are
a
web
standard
for
identity.
That
allows
you
to
work
with
the
cryptographic,
signing
capabilities
that
are
built
into
the
browser,
and
we
are
one
of
the
early
adopters
of
ucan,
which
is
pretty
sweet.
A
If
you
ask
me
and
that
it
allows
for
all
these
cool
features,
they
basically
fall
out
because
it
was
built
right
in
the
first
place.
So
if
we
like
play
the
history
game
for
a
second
at
the
beginning
of
the
web,
there
were
cookies
and
the
old
old
style.
Cookie
would
just
be
an
ID
that
when
you
hit
the
server
it
would
go.
Look
that
idea
up
in
a
database
and
be
like
oh
that's,
J,
Chris
Pro
account
and
then
that
got
to
be
tedious.
A
A
The
problem
is,
if
somebody
steals
that
cookie
now,
they
can
act
just
like
me
and
you
can't
fix
that
because,
rather
than
it
just
being
signed
by
the
service,
it's
also
signed
by
the
user
using
the
key
material
that
the
dids
manage.
So
if
your
ucan's
floating
around
no
one,
but
you
can
use
it
because
you
have
to
have
the
private
key
in
order
to
invoke
that
capability.
A
A
You
know,
storage
and
retrieval
service
what
it
unlocks
we
like
to
call
data
anywhere,
because
when
you're
looking
up
data
by
CID-
and
we
all
know
this-
you
don't
go
to
a
location
to
fetch
it.
You
ask
the
network
for
it
and
whoever
gives
it
to
you.
First,
you
can
know
it's
the
right
one,
because
it's
verifiable,
and
so
you
can
put
them
on
the
blockchain.
You
can
cache
them
because
they're
immutable.
A
Let
me
take
advantage
of
that
with
our
Global
CDN,
and
this
Universal
addressing
scheme
means
that
when
you
write
an
application,
the
compute
can
assume
that
it's
going
to
be
fetching
the
blocks
from
a
reasonably
nearby
ipfs
storage.
You
know
provider,
and
so
you
don't
have
to
write
your
code
in
a
location,
dependent
manner.
You
can
write
it
in
a
location,
independent
manner,
Beyond
just
data
when
we
start
talking
about
those
you
can
invocations
and
because
of
the
way
that
they
provide
like
a
framework
for
authorization
around
the
invocation.
A
A
So
I'll
show
off
the
W3
up
and
there's
a
part
where
we're
really
going
to
go
a
lot
faster
than
the
material,
because
I'm
previewing
for
tomorrow,
but
it's
a
w
threw
up,
is
a
client
library
in
JavaScript.
It
can
upload
files
of
any
size
streaming.
You've
got
verifiable
uploads
so
that
you
know
what
the
CID
is
going
to
be
before
the
data
leaves
your
machine.
A
Here's
a
quick
start,
don't
do
this
now,
unless
you
really
really
want
to
because
come
back
tomorrow
for
the
workshop.
But
what
we'll
do
is
we'll
get
you
set
up
with
a
cryptographic
identifier
on
your
terminal
that
you
can
use
to
run
uploads
and
then
later
on.
In
the
workshop,
we'll
show
you
how
you
can
link
accounts
together
using
that.
A
This
is
what
happens
when
you
do
an
upload,
so
those
signing
tokens
the
you
can
that
I
talked
about
earlier.
What
happens
when
you,
when
you
run
the
client?
Is
you
create
a
cryptographic
identifier?
You
register
that
with
web3
storage
and
now
you
start
uploading
and
we
do
it
using
a
car
transport
mechanism.
So
cars
are
content,
archives,
they're,
just
a
file
with
a
whole
bunch
of
ipfs
blocks
in
it,
and
it
can
be
any
size.
A
Elastic
ipfs,
which
there's
talks
in
the
implementations
track
about
then
indexes
those
car
files
and
makes
them
available
to
the
ipfs
network.
Oh,
and
the
last
thing
we
do
is
maybe
something
worth
knowing
about
car
files,
it's
kind
of
obvious,
but
until
you
bang
your
head
against
them,
you
don't
see
it
necessarily.
A
All
the
blocks
in
the
car
have
the
same
priority
right.
It's
a
flat
name
space,
there's
not
like
a
blessed
block.
That
means
it's
up
to
you,
the
application
author,
like,
which
is
the
entry
points
into
that
car.
If
you
uploaded
a
Unix
FS
directory,
there
would
just
be
the
one
entry
point
that
is
the
top
of
of
that
directory
tree,
but
you
could
have
an
upload
that
is
like
let's
say,
you've
got
multiple
ipld
data
structures
and
you
want
to
make
a
change
to
more
than
one
of
them.
A
A
I'll
skip
this
one,
it's
just.
Let's
look
at
the
code
of
somebody
who's
using
it
and
then
I'll
brag
about
this
part.
So
I
like
to
write,
you
know:
apps
I,
don't
like
to
spend
much
time
on
them.
I
like
to
just
create
react,
app
and
then
drop
some
components
in
don't
want
to
think
too
hard
about
it,
and
so
that's
what
we
built
with
W3
UI,
to
make
it
super
easy
for
developers
to
get
ipfs
uploads
going
on
in
their
application
with
just
a
couple
of
lines
of
code.
A
So
if
you
go
to
this
website,
beta.ui.web3.storage
and
we'll
have
time
in
tomorrow's
Workshop
to
really
investigate
it,
you'll
see
that
all
the
components
have
code
sandboxes,
you
can
click
to
see
them
live,
so
you
can,
you
know,
have
the
code
sandbox
and
the
one
in
your
app
and
look
at
you
know
what
you're
doing
with
that.
But
what
you'd
see
on
there,
as
you
drill
in,
is
that
it
looks
like
this.
A
If
you
were
the
kind
of
application
developer,
who
just
wanted
to
get
it
done
and
didn't
want
to
pay
bills,
then
you
can
give
people
this
user
experience
where,
when
they
come
to
your
app
to
upload
for
the
first
time
they
create
a
web,
3
storage
account
and
they
upload
to
that
account.
And
then
let
your
app
know
about
the
CID
and
that
works
great,
because
as
an
app
developer,
you
don't
have
any
bills
to
pay
and
your
users
can
own
their
data.
They
can
have
data
from
multiple
apps
all
show
up
in
their
web.
A
3
storage
account
and
they
have
more
control
over
their
data.
So
that
is
a
great
way
to
do
like
a
photo
gallery
where
it's
really
the
user's
data
and
you're
just
helping
them
work
with
it,
but
it
also.
Let's
say
you
wanted
you
had
an
existing
app,
a
recipe
app.
That
already
has
a
user
model,
and
you
know
it's
all
web
2
or
whatever
you
just
want
to
add
recipe
photo
uploads.
A
A
We
have
these
example
apps
that
let
you
upload
regular
files,
like
you,
saw
with
the
choose
file
button
on
the
screen
a
second
ago,
so
all
I
did,
and
what
we'll
do
tomorrow
in
the
workshop
is
modify
that
to
take
the
the
base
64
image
off
the
camera
and
upload
it
to
web3
storage.
So
if
the
Wi-Fi
is
cooperating,
it'll
pull
through
to
the
list
of
images
below.
A
A
And
here's
the
actual
Workshop
content
of
both
the
tracks
so
the
front
end
track.
I
just
showed
you
what
the
end
result
looks
like
the
back
end
track
is
maybe
a
little
bit
more
challenging,
but
it's
the
one
that
allows
you
to
give
your
end
users
access
to
your
web3
storage
account
to
upload.
If
you
want
to
do
it
in
a
way,
that's
transparent
to
the
user.
A
So
the
way
web3
storage
happened
as
I
mentioned,
the
nft
community,
blessed
ipfs
cids
is
the
right
way
to
reference
nft
images
from
the
blockchain,
and
that
was
before
we
had
any
tools
to
help
them,
but
we
saw
that
they
were
right
and
that
we
should
make
their
lives
easier.
So
we
built
nft
storage
as
a
website.
You
can
go
in
and
easily
upload
your
nft
images
and
metadata.