IPFS 0.6.0 is officially released. Learn about its new features in one article

Go IPFS 0.6.0 Highlights

MIGRATION: This release contains a small configuration migration to listen for QUIC transports in addition to TCP transports. This migration will:

• Multiple addresses in the canonical boot list use the /p2p/Qm... syntax instead of the /ipfs/Qm... syntax.

• Add QUIC addresses for the default bootloader as needed. If you have already removed the default bootloader from your boot configuration, the migration will not add them back.

• Add a QUIC listener address to mirror any TCP addresses present in your configuration. For example, if you listen on /ip4/0.0.0.0/tcp/1234, this migration will add a listen address for it at /ip4/0.0.0/udp/1234/quic.

QUIC is now enabled by default

This release enables the QUIC transport by default for both inbound and outbound connections. When connecting to a new peer, libp2p will continue to dial all advertised addresses (tcp+quic) in parallel, so if the quic connection fails for some reason, the connection should still succeed.

If you want to learn more about the benefits of QUIC, check out the release notes for more information.

NOTE: The QUIC transport included in this release is backwards-incompatible with the experimental QUIC transport included in previous releases. However, the QUIC protocol has undergone some major breaking changes, and supporting multiple versions is not an option. In practice, when dialing nodes with incompatible QUIC versions, ipfs will simply rely on the TCP transport, which can degrade performance.

Introducing Noise Safe Transmission

This go-ipfs release introduces a new secure transport: libp2p Noise (built from the Noise protocol framework). While TLS1.3 is still the default go-ipfs secure transport, Noise is simpler to implement from scratch and will become the standard cross-platform libp2p secure transport in the future.

This brings us one step closer to removing and deprecating support for SECIO.

When enabled by default, TLS1.3 and SECIO will still be negotiated before Noise is issued. Once the network has had time to upgrade, Noise will take precedence over SECIO. If you would like Noise to take precedence over other secure transports, you can change its priority in the configuration (Swarm.Transport.Security.Noise).

Gateway

This version provides two gateway-related features: custom 404 pages and base36 support.

Custom 404 Page

You can now customize your 404 Not Found error page by including an ipfs-404.html file somewhere in your request path.

If the requested file is not found, go ipfs will look for ipfs-404.html in the same directory and each parent directory as the requested file. If found, this file will be returned (with a 404 status code) instead of the usual error message.

Base36 support

This release adds support for a new multi-base encoding: base36. Base36 is a most efficient case-insensitive alphanumeric encoding. Case-insensitive alphanumeric encodings are important for subdomain gateways, since domain names are case-insensitive.

While base32 (the current default encoding used in subdomains) is simpler than base36, it is not optimally efficient, and base36 Ed25519 IPNS keys are 2 characters too large to fit the 63-character subdomain length limit. The additional efficiency of base36 gets us below this limit and allows Ed25519 IPNS keys to work with the subdomain gateway.

This release adds support for base36, but it is not used by default. If you want to re-encode an Ed25519 IPNS key to base36, you can use the ipfs cid format command:

$ipfs cid format -v 1--codec libp2p-key -b base36 bafzaajaiejca4syrpdu6gdx4wsdnokxkprgzxf44wrstuc34gxw5k5jrag2so5gk

#K51QZI5UQU5DJ16QYIQ0TAJOLKOJYL9QDK25492WXV7GHTUWCZ593TP69Z9M

Gossipsub upgraded to v1.1

This release brings a new Gossipsub protocol version: 1.1. You can see it on the blog.

Peer

This release introduces a new peer feature. The peer subsystem configures go-ipfs to connect, stay connected, and reconnect to a set of nodes. Nodes should use this subsystem to create "sticky" links between frequently useful nodes to improve reliability. You can read more about it and how to configure peers in the go-ipfs-config README.

Thanks to all who contributed!

A huge thank you to everyone who contributed patches and improvements in this release, all 46 of you! We couldn't have done this without everyone's help and feedback. ❤

Install, upgrade, and join us!

You can install go-ipfs, or upgrade to go-ipfs 0.6 to get started.

There are many ways to get involved with IPFS, depending on your skills, interests, and availability. Check out our contribution page on GitHub for guidance and next steps.

It’s an exciting time for IPFS and the web as a whole. Join us!

This article is translated from https://blog.ipfs.io/2020-06-26-go-ipfs-0-6-0/. If reproduced, please indicate the source.