Improve offline IPNS (record) support
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- distributed-systems, networking
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.
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:
- https://github.com/libp2p/go-libp2p-kad-dht/pull/291. Introducing this would break IPNS at the moment as we don't properly complete the query.
- Dominant language
- No language data
- Stars
- 38
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from libp2p/notes
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
DHT
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
HarperFast/harper-pro#926 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
check_program_status() ignores errors on ranks other than 0, and calls Abort() with errorcode 0Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
NCAR/WrfHydroForcing#132 ·
-
bug P2 reliability workers
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
afreidah/s3-orchestrator#1563 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
ergoplatform/ergo#2579 ·
Maintainers usually reply within 2 days