libp2p / libp2p/notes

Improve offline IPNS (record) support

Open
#16 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
No language data
Stars
38
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Libp2p should have better offline/disconnected-network record support:

  • On resolve, IPNS records should be cached locally. This will:
    • Help with streaming resolve. Peers searching for popular records will get back "best effort" results along the way. We still won't be able to stop the search early as these "best effort" copies of the records won't be updated but it can help.
    • Help with offline situations. If a node resolves a record while online, they'll continue to have a copy of that record when offline. It may not be up-to-date but it's better than nothing.
    • Help with resolving on a disconnected network. If a subset of nodes "become" the entire DHT, they'll have all the records they've resolved recently.
  • Users should be allowed to publish DHT records while offline (or in a disconnected network). DHT rebalancing (to be implemented) should take care of moving these records to the right place at the end of the day.

Dependencies:

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the dependency in go-libp2p-kad-dht PR 291 and the current IPNS resolve and publish flows. Define how locally cached records, streaming best-effort results, offline publishing, and disconnected-network behavior should interact. Done means the behavior works offline and online without breaking IPNS resolution.

Written by the indexing model from the issue text.

Assessment

Domain
distributed-systems, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.