Mention record owner optimisation #350
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rinzler100
approved these changes
Nov 27, 2022
|
That an intresting thought to do, but does an implementation actually does this ? I don't belive Kubo is that smart. |
|
And you would need to write an IPIP because there are side effects of such things that we need to discuss (multiple nodes using the same peerid): |
|
Closing as this needs an IPIP |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related: #274
Changes IPNS.md to mention that the owner of a record is implicitly trusted to hold the most recent record, and implementations MAY skip the sequence value comparison in the case where the provider of the record is the record owner.