SWIP-22: feed wrapping (wrapping a CAC into a SOC) #57
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
7 tasks
|
to be reviewed, improved and merged when released |
zelig
changed the title
zelig
approved these changes
Sep 25, 2024
tamas6
changed the title
|
Implemented at ethersphere/bee#4677 |
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.
This SWIP proposes a modification to the existing feed payload structure to support wrapping entire content-addressed chunks (CAC) directly within feeds, eliminating the need for a separate JSON structure containing CAC references and timestamps. This change aims to streamline the retrieval process by allowing a single request to resolve SOC content, enhancing efficiency and compatibility with erasure coding techniques.