Skip to content

docs(protocol): per-range merkle proofs on dig.fetchRange (#1437) - #46

Merged
MichaelTaylor3d merged 1 commit into
mainfrom
docs/1437-range-proofs
Jul 24, 2026
Merged

docs(protocol): per-range merkle proofs on dig.fetchRange (#1437)#46
MichaelTaylor3d merged 1 commit into
mainfrom
docs/1437-range-proofs

Conversation

@MichaelTaylor3d

Copy link
Copy Markdown
Contributor

Summary

Document the v0.4.0 additive fields range_proof and first_chunk_index on the peer RPC dig.fetchRange response frames, enabling clients to verify each range independently against the chain-anchored root without awaiting the whole resource.

Changes

  • Add per-range proof field documentation to §9 dig.fetchRange section
  • Update conformance table to reflect per-chunk proof capability
  • Bump version to 0.5.3

Source

  • modules/crates/00-foundation/dig-rpc-protocol/SPEC.md §6.1 (the authoritative range proof specification)

Test plan

  • Markdown formatting verified (no syntax errors)
  • Full build completes successfully (npm run build)
  • Prose follows existing peer-network.md voice and depth

🤖 Generated with Claude Code

@MichaelTaylor3d
MichaelTaylor3d marked this pull request as ready for review July 24, 2026 12:51
dig-rpc-protocol v0.4.0 adds two optional RangeFrame fields: range_proof
(one base64 merkle inclusion proof per chunk, ascending) and
first_chunk_index (absolute index of the frame's first chunk). Documented
on the peer-network page and added to the dig-spec.mjs source of truth so
the generated OpenRPC artifacts carry the schema, not just the prose.

Co-Authored-By: Claude <noreply@anthropic.com>
@MichaelTaylor3d
MichaelTaylor3d force-pushed the docs/1437-range-proofs branch from 00a1c1d to 39e123a Compare July 24, 2026 13:17
@MichaelTaylor3d
MichaelTaylor3d merged commit 67498d3 into main Jul 24, 2026
7 checks passed
@MichaelTaylor3d
MichaelTaylor3d deleted the docs/1437-range-proofs branch July 24, 2026 13:31
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.

1 participant