Post
Share your knowledge.
Conflict between IPFS/Kubo PubSub IPNS - Who wins?
I am curious about the behavior of IPFS/Kubo when using PubSub IPNS. If one node generates a new key and copies it to another node, and both nodes attempt to publish content using the same IPNS key, what happens? According to the documentation, there is automatic republishing after 4 hours. In this scenario, which node will be successful in publishing the updated CID? I would appreciate any insights or clarifications on this matter.
- IPFS
- IPNS
- Kubo
Answers
1In a scenario where multiple nodes are involved, publishing the same key to IPNS can enhance redundancy and ensure continuous availability of the content. Although it is uncertain which node would emerge as the ultimate winner, this approach offers resilience by rebroadcasting the IPNS even if one of the nodes becomes unavailable. This redundancy can be achieved by following these steps:
- Generate a unique key for the content you want to publish using IPNS.
- Ensure that all the nodes involved in the network have access to this key.
- Publish the content using the generated key on each node.
- As a result, all the nodes will publish the same key to IPNS, creating redundancy.
By implementing this redundancy strategy, you can increase the chances of the content being accessible even if one of the nodes goes down.
Do you know the answer?
Please log in and share it.
The InterPlanetary File System (IPFS) is a protocol, hypermedia and file sharing peer-to-peer network for storing and sharing data in a distributed file system.
