Transactional IPNS
Open
need/analysis
- Dominant language
- Go
- Stars
- 17.1k
- Forks
- 3.2k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 11
Description
#### Version information: v0.4.3
#### Type: feature
#### Priority: P4
#### Description:
It would be nice if multiple programs could maintain their own namespaced areas under a common single IPNS root object. Until there are multiple IPNS objects per node, this would need to be handled by some sort of locking.
There might be `--if-current-is=[hash]` optional parameter for updating the IPNS object. The command would fail if the current IPNS hash does not match the one provided.
Another way would be to add commands to lock the IPNS hash and unlock the hash.
I suspect that these two approaches are not mutually exclusive and may both be useful in different situations.
Contributor guide
Assessment
This issue has not been assessed yet.