Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

more language and formatting tweaks for state network specification #261

Conversation

pipermerriam
Copy link
Member

Another round of language and formatting tweaks for state network specification.


A bridge should compute the content-id values for all of this new state data
and sort the data by proximity to its own node-id. Beginning with the content
that is *closest* to its own node-id it should proceed to GOSSIP each
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should the content ordering by the bridge only apply to the leaves of account trie, storage trie, and contract code, considering the intermediate trie nodes will be gossiped by other nodes in the recursive gossip?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can re-word to make this explicit.

@pipermerriam pipermerriam merged commit 2c46d69 into ethereum:new-statenetwork-boogie Jan 17, 2024
2 checks passed
@pipermerriam pipermerriam deleted the piper/more-language-refinements-to-state-network branch January 17, 2024 03:29
pipermerriam added a commit that referenced this pull request Jan 29, 2024
* delete removed sections

* remove old data types

* Allow Offer and Request data types to differ

* define nibble types

* Add Function definitions

* Define `Account Trie Node` data type

* Define `Contract Trie Node` data type

* Add section to define `Contract Code` data type

* commit todos

* WIP: STATE SPECS V2

* some disperate changes

* some language updates

* Add language describing the path aware content-id scheme (#250)

* Remove path-aware content-id generation (#252)

* Add definition of recursive gossip (#254)

* initial definition of recursive gossip

* Update state-network.md

Co-authored-by: Kim De Mey <[email protected]>

* Update state-network.md

Co-authored-by: Kim De Mey <[email protected]>

* Update state-network.md

Co-authored-by: Kim De Mey <[email protected]>

* Update state-network.md

Co-authored-by: Kim De Mey <[email protected]>

* Update state-network.md

Co-authored-by: Kim De Mey <[email protected]>

* Update state-network.md

Co-authored-by: Kim De Mey <[email protected]>

---------

Co-authored-by: Kim De Mey <[email protected]>

* Better define serialization formats (#255)

* Better define serialization formats

* more updates to witness formats

* Additional validity requirements and spec fixes for state witnesses (#257)

* Additional validity requirements and spec fixes for state witnesses

* add TODO

* More cleanup of validity language for proofs and formatting (#260)

* More cleanup of validity language for proofs and formatting

* use MUST NOT instead of MAY NOT

* more language and formatting tweaks for state network specification (#261)

* More specificity around bridge node gossip priority ordering for content (#263)

* offer/retrieval union content types splitted into separate types/subsections (#262)

* language clarification for the use of different data types

* remove content_id definition from types + lang fix for content_id

* clarify nibbles packing (align it with MPT) and provide examples (#266)

* update the gossip spec and clarify what proof actually contains (#267)

* update the gossip spec and clarify what proof actually contains

* clarify that recursive gossip doesn't happen for bytecode

---------

Co-authored-by: Piper Merriam <[email protected]>
Co-authored-by: Kim De Mey <[email protected]>
Co-authored-by: Daniel Sobol <[email protected]>
Co-authored-by: Milos Stankovic <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants