►
From YouTube: Go-IPFS 0.7 Release - Adin Schmahmann
Description
Lead go-IPFS maintainer Adin Schmahmann joined us to give an overview of what’s to come in the next major release for IPFS: go-IPFS 0.7!
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
A
Go
ipfs
0.7
is
going
to
be
coming
out
very
soon,
so
let's
go
into
a
little
bit
of
what's
going
to
be
in
there
all
right.
So,
first
off
we
are
disabling
secio
support
by
default.
A
So
secio
is
a
security
protocol
that
we've
been
using
for
a
long
time
to
make
sure
that
peers
can
securely
communicate
with
each
other
in
general.
It's
good.
It's
good
practice
to
try
and
use
protocols
that
are
are
sort
of
widely
supported
in
the
cryptographic
space,
and
so
we've
started
to
move.
We've
moved
towards
other
protocols
like
tls
and
noise,
and
now
is
the
time
for
us
to
discontinue
support
for
for
sec,
il
there
is
a
blog
post.
A
That
goes
into
a
lot
more
detail
here,
which
I
encourage
you
to
check
out,
but
the
short
version
is
that
if
you
are
running
go
ipfs
earlier
than
0.4.21
or
jsipfs
below
0.47
you,
you
should
definitely
upgrade
because
otherwise
you
will
not
be
able
to
talk
to
other
peers
on
the
network.
A
This
has
a
nice
benefit
if
you
upgrade
to
the
latest
version,
where
things
dht
dht
nodes,
greater
than
go.
Ipvs
0.5
just
perform
a
lot
better,
and
we
have
we've
had
a
number
of
really
nice
features
in
0.5
and
0.6
and
some
coming
in
0.7.
So
we
encourage
upgrading.
A
All
right
and
keys,
so
we
are
switching
to
using
elliptic
curve
keys,
edt5519
keys
by
default.
A
These
are
smaller
and
more
performant
than
than
rsa
keys
and
are
going
to
help
us
going
forward
in
terms
of
making
content
like
content
faster,
to
discover
and
and
basically
anything
that
we
want
that
is
going
to
involve
some
sort
of
user-based.
Signature
is
now
going
to
be
much
faster
and
easier
for
us
to
do
to
help
with
this
we've
also
added
some
commands
for
key
rotation
and
importing
and
exporting
them
so
changing
what
the
peer
id
key
is.
A
So,
for
example,
you
may
have
had
your
key
previously.
That
was
some
rsa
key
with
a
peer
id
that
looks
like
this.
You
know
qm
something
and
then
you'll
rotate
it
to
an
elliptic
curve
key.
This
is
actually.
This
is
the
default.
If
you
don't
specify
the
type
flag,
this
will
just
work
and
it
will
save
your
pre-existing
key
because
you
may
have
been
using
your
pre-existing
key
as
an
ipns
key
as
a
publishing
key.
So
we
keep
that
around
and
you'll
see
the
formats
change.
A
So
instead
of
you
know,
qm
something
it's
starts
with
one
two
and
that's
because
it's
actually
the
key
is
now
small
enough
that
we
don't
need
to
refer
to
some
some
hash
of
the
rsa
public
key
like
we
did
before.
We
can
actually
refer
to
the
entire
elliptic
curve
key,
and
so
this
is
the
elliptic
republic.
Key
is
in
here.
A
This
is
particularly
helpful
for
the
http
over
lupita
p
feature
that
is
in
copy
of
s
importing
exporting
keys
sort
of
works.
As
you
would
expect
you
just
decide.
You
say
I
want
to
export
the
key
here's
the
file.
This
is
the
name
of
the
key
and
when
you
import,
you
just
say,
here's
the
name
of
the
file,
and
this
is
what
I
want
to
call
it
once
I
import
it
base
36.
A
So
we
have
now
switched
the
default
representation
of
all
ips
keys
to
be
base,
36
cidv
ones,
by
default,
and
this
is
good
because
when
you
have
when
you
have
sub
domains,
so
if
you
want
to
have
you
know,
key.ips.localhost
or
or
you
know,
dot
ips.dlink.web?
A
That
needs
to
be
both
all
in
a
single
case
and
it
needs
to
be
small
enough
to
fit
within
the
dns
label.
Size
and
base36
allows
us
to
do
this,
whereas
base
58
did
not
with
with
this
a
whole
uppercase
lowercase
thing.
So
now
things
should
look
the
same
when
you
use
subdomains
and
when
you
use
you
know
outputs
from
the
ipfs
command
line.
A
Additionally
we're
getting
prepared
for
having
peer,
ids
being
represented
in
base
36.
For
similar
reasons,
there
are
still
a
number
of
laptp
implementations
that
do
not
have
support
for
rep
for
representing
multi
addresses
in
base
36.
So
that's
not
the
default
yet,
but
we're
looking
forward
to
doing
that
in
the
future.
A
This
has
been
a
feature.
It's
been
requested
for
a
little
while
being
able
to
get
some
basic
stats
out
of
a
dag.
In
particular.
Let's
say
you
just
want
to
get
the
size
of
a
dag,
not
a
unix
fs
object,
but
the
entire
dag
itself.
A
We
now
have
a
command
for
that.
This
is
also
good
for
unix
fs,
because
there
are
some
shortcuts
in
unix
fs
that
allow
you
to
understand
the
size
of
an
object
without
actually
reading
the
whole
thing,
but
but
sometimes
you
actually
don't
want
the
shortcutted.
You
know
size
but
the
full
size.
You
know
the
full
size
of
the
data
structure
and,
finally,
don't
forget
to
upgrade
on
you
know,
disc.ipfest.io
and
we
will
have
go
ipfs.
Is
it
go?