docs: cover protocol types and PeerDAS#181
Merged
Merged
Conversation
mattsse
force-pushed
the
mattsse/docs-signers-testing
branch
from
July 16, 2026 14:46
2296818 to
8df17bb
Compare
mattsse
force-pushed
the
mattsse/docs-protocol-reference
branch
from
July 16, 2026 14:48
bd5b4bd to
a40f25c
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Why
The site documents primitives and provider calls but does not explain the protocol and data-model crates that make up much of Alloy. Users must infer when to use consensus versus RPC types, how Network changes associated types, and where genesis, trie, and serialization helpers fit. The examples include EIP-7594, but the transaction guide omits it.
Impact
Infrastructure and library authors get a boundary-oriented type map instead of a crate-name inventory. Application developers can convert RPC responses without JSON round trips and select the correct network representation. PeerDAS users can find the existing runnable flow and its node, fork, and KZG requirements.