Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

https://docs.ipfs.io/concepts/ipns/

Quoth:

IPFS uses content-based addressing; it creates an address of a file based on data contained within the file. If you were to share an IPFS address such as /ipfs/QmbezGequPwcsWo8UL4wDF6a8hYwM1hmbzYv2mnKkEWaUp with someone, you would need to give the person a new link every time you update the content.

The InterPlanetary Name System (IPNS) solves this issue by creating an address that can be updated.

A name in IPNS is the hash of a public key. It is associated with a record containing information about the hash it links to that is signed by the corresponding private key. New records can be signed and published at any time.

...

Alternatives to IPNS

IPNS is not the only way to create mutable addresses on IPFS. You can also use DNSLink, which is currently much faster than IPNS and also uses human-readable names. Other community members are exploring ways to use blockchains to store common name records.



This all sounds like reinventing ICANN and tld's

First you had a decentralized internet, anyone with a computer could put something online, but sharing IP's everywhere was not easy to remember, and some weren't static... So they created DNS and Top Level Domains...


IPNS is not DNS. It's just a fixed wrapper for mutable content. You are supposed to combine IPNS with something like ENS if you want human friendly names.


Last time I checked you had to have a server updating the IPNS entry daily or it would expire. Is this still the case?




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: