The new version of IPFS 0.6 has already been released and these are its news

Recently the release of the new version was announced decentralized file system IPFS 0.6 (InterPlanetary File System), which forms a global versioned file store deployed in the form of a P2P network made up of member systems. IPFS combines ideas previously implemented in systems such as Git, BitTorrent, Kademlia, SFS and Web and it resembles a single BitTorrent "pair" (peers participating in distribution) exchanging Git objects.

IPFS differs in addressing by content rather than location and arbitrary names. The reference implementation code is written in Go and is distributed under the Apache 2.0 and MIT licenses.

In IPFS, a link to access a file is directly related to its content and includes a cryptographic hash of the content. The file address cannot be arbitrarily renamed, it can only be changed after changing the content.

Similarly, it is impossible to make a change to the file without changing the address (the old version will remain at the old address, and the new one will be available through a different address, since the hash of the file's content will change).

Since the file identifier changes with each change, in order not to send new links each time, services are provided to link permanent addresses that take into account different versions of the file (IPNS), or to correct an alias similar to traditional FS and DNS ( MFS (Mutable File System) and DNSLink).

IPFS helps solve problems tales such as storage reliability (if the original storage is out of order, the file can be downloaded from other users' systems), opposition to content censorship (blocking will require blocking all user systems that have a copy of the data) and organizing access in the absence of direct access Internet connections or when the quality of the communication channel is poor (you can download data through the most nearby on the local network).

What's new in IPFS 0.6?

The new version is notable for the inclusion of a default transport based on the QUIC protocol, which is a plug-in on the UDP protocol that supports multiplexing of multiple connections and provides encryption methods equivalent to TLS / SSL.

In IPFS, a socket to receive UDP connections is automatically started on the same network address and port as the TCP-based transport controller. QUIC is used for inbound and outbound connections, and when connecting to new nodes, if QUIC is not available, it will revert to TCP.

The second innovation important was the sNOISE safe transport support, based on the Noise protocol and developed as part of libp2p, a modular network stack for P2P applications.

After the initial coordination of the connection, all subsequent data exchange between the participants is encrypted and protected against eavesdropping. NOISE replaced the SECIO transport, but TLS 1.3 continues to be used as the primary method of encrypting connections between nodes.

NOISE is quite simple to implement and is positioned as a cross-platform universal transport that can be implemented in various programming languages.

The new version also provides the opportunity to add your own "404 not found" pages and add optional support for Base36 encoding method, which is optimal for case-insensitive alphanumeric data such as domain names (when using Base32, Ed25519 IPNS keys are two bytes larger than the limit on subdomain size, and with Base36 it fits the limit).

In addition, the 'pairing' option has been added to the settings, which defines a list of nodes to connect, maintain a connection, and reconnect to determine "hard" connections between frequently used peers.

Finally, if you are interested in knowing more about this new version, you can check the details, by going to the following link. 

How to use IPFS on Linux?

For those who are interested in being able to implement IPFS in their system, they can do so by following the instructions that are detailed in this article.

IPFS: How to use the Interplanetary File System in GNU / Linux?
Related article:
IPFS: How to use the Interplanetary File System in GNU / Linux?

A comment, leave yours

Leave a Comment

Your email address will not be published. Required fields are marked with *

*

*

  1. Responsible for the data: Miguel Ángel Gatón
  2. Purpose of the data: Control SPAM, comment management.
  3. Legitimation: Your consent
  4. Communication of the data: The data will not be communicated to third parties except by legal obligation.
  5. Data storage: Database hosted by Occentus Networks (EU)
  6. Rights: At any time you can limit, recover and delete your information.

  1.   Kao said

    This is something that I have seen before, but I cannot understand what use it could be. I think there are services or applications that already use it for their things, but I haven't tried any yet.