Add GSOC page #718
Open
Add GSOC page #718
+324
−0
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
✅ Deploy Preview for test-twitter-preview-testing-3 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for bee-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Cafe137
reviewed
Feb 26, 2025
|
|
||
| The Graffiti Single Owner Chunk (GSOC) feature enables a single Bee *service* node to receive messages from multiple Bee *writer* nodes. It is based on a [Single Owner Chunk (SOC)](/docs/develop/tools-and-features/chunk-types/#single-owner-chunks), but unlike a standard SOC, which can be updated only by a single owner, GSOC allows multiple nodes to make updates. The GSOC address is derived so that it falls within the neighborhood of the service node, ensuring updates are automatically synced as part of the normal full node syncing process. | ||
|
|
||
| The service node determines the data used to derive the GSOC private key. Any node with access to this data can derive the same key and update the GSOC. The service node also defines a message format, filtering out non-conforming updates. Nodes which know both the GSOC key derivation data and the expected message format can send messages to the service node. Since only full nodes sync neighborhood chunks, the service node *must be a full node to receive GSOC updates*. |
There was a problem hiding this comment.
Defining the message format is not a hard requirement. You can subscribe (ws) to GSOC and receive every message. It is a requirement in @anythread/gsoc, but not in Bee API.
Cafe137
reviewed
Feb 26, 2025
| 1. A full Bee node and a second light Bee node | ||
| 2. A small amount of xBZZ and xDAI for postage stamp purchases and uploads | ||
| 3. NodeJS & NPM | ||
| 4. A mutable stamp batch (*set the* [`immutable` header parameter](/api/#tag/Postage-Stamps/paths/~1stamps~1%7Bamount%7D~1%7Bdepth%7D/post) *to `false` when* [buying a batch](/docs/develop/access-the-swarm/buy-a-stamp-batch#buying-a-stamp-batch)) |
There was a problem hiding this comment.
Recommended, not a hard requirement. For full clarity maybe explain in a footnote why it is beneficial?
Cafe137
reviewed
Feb 26, 2025
|
|
||
| To use GSOC, you need: | ||
|
|
||
| 1. A full Bee node and a second light Bee node |
There was a problem hiding this comment.
Maybe add parentheses: full Bee node (service node) and light Bee node (writer node) so it matches the previous sections
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.
No description provided.