Background Concepts and Definitions about go-ipns HOT 5 CLOSED

Hm. Unfortunately, I don't know of any good "what is IPNS" resources and this is not the first time I've needed one. I should probably write one...

from go-ipns.

Basically, it allows users to map a public key to some path (e.g., an IPFS path) by creating an IPNS record signed by the public key in question. The mapping is generally ephemeral and expires after a period of time to reduce the window for replay attacks.

An IPNS record has:

• A value: the current value of the IPNS entry.
• A validity data and type: Together, these describe under what conditions the IPNS record is valid. Currently, we only support an expiration time. (type = EOL, value = $someDate).
• A sequence number. IPNS records are orderd first by sequence number, then by EOL.
• A signature over the above fields.
• (optionally) An embedded public key so DHT nodes can verify the IPNS record without having to fetch it.

from go-ipns.

Yes, any information you could provide me will be extremely valuable, I know nothing about IPNS besides what I've seen in a presentation or two about being able to generate mutable content (in my head I think of it as the DNS of the IPFS world, although I'm aware that is not correct), but I have no idea about how it is technically implemented, and without that I don't think I can be of much use here.

from go-ipns.

I think it would also be helpful for anyone who is considering using IPFS to store name records, to understand the current, theoretical and expected performance limits, so they can answer questions about whether to use IPFS or eg BitTorrent DHT etc for their project.

My questions would be along the lines of

• How long does it currently typically take to store / retrieve a record?
• What is the theoretical minimum / average / maximum time?
• What is the expected minimum / average / maximum time (and when will IPNS be stable enough to consistently hit these benchmarks)?
• How much data can I store in a record?
• etc

Because IPFS / IPNS are improving rapidly it would be good to have a public roadmap and an indication of where we are on it, and where we expect to be in terms of performance

from go-ipns.

This repository is no longer maintained and has been copied over to Boxo. We are now in the process of reviewing issues and PRs and moving the ones that are still relevant. This issue has been moved to ipfs/boxo#335.

from go-ipns.