A Study on IPFS

Jan 28, 202466

AI Translation

This post is translated from Chinese into English through AI.View Original

AI-generated summary

This text discusses the concept of IPFS, which is similar to the concept of blockchain a few years ago. IPFS allows users to store files on a decentralized network and access them using hash values. IPNS is a DNS server within IPFS that can be used with DNSLink to access files. The text also mentions the use of CID (IPFS file ID) and the need to pin files to prevent them from being lost. It suggests using DNSLink to map IPFS files to regular domain names, but notes that this is not decentralized. It briefly mentions ENS (Ethereum Name Service) and its cost. The author plans to write more about this topic later.

IPFS is a concept that emerged during the hype of blockchain a few years ago. My understanding is that it allows you to store your files on the chain and access them using hash values. For example, a navigation page can be accessed using IPNS and IPFS.
IPNS can be understood as the DNS server within IPFS, used in conjunction with DNSLink. For example, _dnslink.dgtea.site points to the CID QmaPqMkMm2gzjyWvfw2t73cPZsopr5BWb1tGSrh8uzhaVE, so it can be directly accessed through the gateway: https://ipfs.io/ipns/dgtea.site/
The CID (file ID in IPFS) is QmaPqMkMm2gzjyWvfw2t73cPZsopr5BWb1tGSrh8uzhaVE.
After uploading a file, it needs to be pinned; otherwise, it may be lost. Pinning is like having a node keep your file.
~~You can use DNSLink to map it to a regular domain name, but it's not decentralized, not libre.~~ My mistake, should it be used as a short link with an actual domain name?
And ENS (Ethereum Name Service) .eth domains cost $17 per year, which is too expensive for me.

That's all for now, I'll write the rest later.