IPFS/KUBO PubSub IPNS 之间的冲突-谁赢了？

Question

我对使用 PubSub IPNS 时 IPFS/Kubo 的行为很好奇. 如果一个节点生成新密钥并将其复制到另一个节点，并且两个节点都尝试使用相同的 IPNS 密钥发布内容，会发生什么？根据文档，4小时后会自动重新发布. 在这种情况下，哪个节点将成功发布更新后的 CID？如果能就此事提出任何见解或澄清，我将不胜感激.

IPFS moderator · Answer

In 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.

帖子

分享您的知识。

IPFS/KUBO PubSub IPNS 之间的冲突-谁赢了？

答案

你知道答案吗？

赚取你的 1000 Sui 份额