Information IPFS
This commit is contained in:
parent
e744a4334b
commit
b080645826
22
README.md
22
README.md
|
@ -74,3 +74,25 @@ Also, consider spreading the word about the existence of the "Rustbook" in Rust
|
||||||
|
|
||||||
Remember that the key to creating a successful "Rustbook" is accuracy, clarity, and good documentation. Make sure to keep the project up-to-date as the DECA Protocol evolves and consider accepting contributions from the community to improve the content and quality of the "Rustbook." Good luck with your project!
|
Remember that the key to creating a successful "Rustbook" is accuracy, clarity, and good documentation. Make sure to keep the project up-to-date as the DECA Protocol evolves and consider accepting contributions from the community to improve the content and quality of the "Rustbook." Good luck with your project!
|
||||||
|
|
||||||
|
|
||||||
|
# IPFS
|
||||||
|
|
||||||
|
IPFS, which stands for InterPlanetary File System, is a protocol and decentralized network designed to change the way content is stored, distributed, and accessed on the Internet. It was created by Juan Benet in 2014 and aims to address some of the key challenges facing data storage and distribution technologies in the current web.
|
||||||
|
|
||||||
|
The central feature of IPFS is its focus on content-based distribution rather than location-based. Instead of relying on IP addresses or domain names to access files, IPFS uses a system of unique addresses based on the content's hash. This means that each file or set of data has a unique hash that serves as its address, allowing for a more efficient and redundant way of storing and distributing information.
|
||||||
|
|
||||||
|
The main features of IPFS include:
|
||||||
|
|
||||||
|
1. **Decentralized distribution:** IPFS operates on a decentralized network, meaning files are stored and distributed across a network of interconnected nodes, rather than relying on a central server. This can enhance resistance to censorship and availability of content.
|
||||||
|
|
||||||
|
2. **Peer-to-peer (P2P) network:** Each node in the IPFS network can act as both a client and a server, enabling direct content distribution between nodes without the need for a central server. This reduces the load on individual servers and enables greater performance and scalability.
|
||||||
|
|
||||||
|
3. **Hashing and unique addresses:** Each file or set of data in IPFS is identified by a unique hash that is calculated from the content itself. This allows for precise and unique referencing of any file, regardless of its physical location in the network.
|
||||||
|
|
||||||
|
4. **Redundant storage:** Since files are distributed across multiple nodes, the inherent redundancy in the IPFS network can improve the availability and speed of content access. If one node is unavailable, other nodes can provide the same content.
|
||||||
|
|
||||||
|
5. **Caching and speed:** IPFS includes a caching system that helps speed up access to files. If a node already has a copy of a file, it can serve it directly.
|
||||||
|
|
||||||
|
6. **Resistance to censorship:** Due to its decentralized nature and lack of a single point of control, IPFS is more resistant to censorship and content removal.
|
||||||
|
|
||||||
|
IPFS has applications in various areas, including content distribution, software version management, website publishing, and the creation of decentralized applications (dApps). However, it also presents challenges in terms of widespread adoption and compatibility with existing web infrastructure.
|
||||||
|
|
Loading…
Reference in New Issue