release of a decentralized file system (InterPlanetary File System), creating a global versioned file storage deployed in the form of a P2P network formed by participant systems. IPFS combines ideas previously implemented in systems like Git, BitTorrent, Kademlia, SFS, and the Web, resembling a unified “swarm” of BitTorrent (peers participating in distribution), exchanging Git objects. IPFS is characterized by content-based addressing rather than location and arbitrary names. The code of the reference implementation is written in Go and licensed under Apache 2.0 and MIT.
In the new version, transport is disabled by default , which was replaced in the last release with a transport , the protocol and developed within a modular network stack for P2P applications . TLSv1.3 has been retained as a fallback transport. Node administrators using older versions of IPFS (Go IPFS < 0.5 or JS IPFS < 0.47) are advised to update the software to avoid performance degradation.
The new version has also transitioned to the default use of ed25519 keys instead of RSA. Support for old RSA keys has been maintained, but new keys will now be generated using the ed25519 algorithm. The use of built-in ed25519 public keys addresses the issue of storing public keys, for example, to verify signed data; when using ed25519, only PeerId information is required. Key names in IPNS paths are now encoded using the base36 CIDv1 algorithm instead of base58btc.
In addition to changing the default key type in IPFS 0.7, the ability to rotate identity keys has been added. To change a node's key, the command "ipfs key rotate" can now be executed. Moreover, new commands for importing and exporting keys ("ipfs key import" and "ipfs key export") have been added for backup purposes, as well as the command "ipfs dag stat" to output statistics about the DAG (Distributed Acyclic Graphs).
Recall that in IPFS, the link to access a file is directly tied to its content and includes a cryptographic hash of that content. The file address cannot be renamed arbitrarily; it can only change if the content changes. Similarly, it is not possible to make a change to the file without altering the address (the old version will remain at the same address, while the new one will be accessible via a different address, as the hash of the file's content will change). Considering that the file identifier changes with each modification, services are provided to bind permanent addresses that account for different versions of the file.), or to anchor a pseudonym similar to traditional FS and DNS ( (Mutable File System) and ).
Similar to BitTorrent, data is directly stored on participant systems, which exchange information in a P2P manner, without relying on centralized nodes. When a file with specific content is needed, the system locates participants who have that file and delivers it from their systems in parts over multiple streams. After downloading the file to their system, a participant automatically becomes one of the points for its distribution. To identify network participants that have the desired content a distributed hash table (To access the global filesystem, IPFS can utilize the HTTP protocol or mount a virtual filesystem /ipfs using the FUSE module.
IPFS helps to address issues such as storage reliability (if the original storage fails, the file can be downloaded from other users' systems), resistance to content censorship (to block it, all user systems with a copy of the data would need to be blocked), and enabling access when there is no direct internet connection or when the quality of the connection is poor (data can be downloaded through the nearest peers in the local network). In addition to file storage and data sharing, IPFS can be used as a foundation for creating new services, such as organizing the operation of websites that are not tied to servers or developing distributed applications. .
Source: opennet.ru
