docs(spec): record opcode-220 as base-bounded by design (accepted) (#1780) - #49
Merged
Merged
Conversation
…780) Salvage anchor: record that opcode 220 (DigMessage, directed envelope) rides the base rate-limit bound by design (it is the streaming transport; a tighter row would clip legit streaming), non-fail-open; inner-type limiting is dig-node. Co-Authored-By: Claude <noreply@anthropic.com>
Add normative note to SPEC.md §2.3.1 and CON-005.md explaining that opcode 220 (DigMessage, directed envelope) is deliberately base-bounded only by default_settings limits, with no dedicated dig_wire row, because dig-gossip performs no per-frame crypto and opcode 220's streaming nature requires high frame cadence. Recipient-side per-subtype limiting is defense-in-depth layered on top. Co-Authored-By: Claude <noreply@anthropic.com>
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.
Closes dig_ecosystem#1780.
Task
#1780 (evaluate a dedicated
dig_wirerate-limit row for opcode 220 / DigMessage) resolved by a decide-first as DOCUMENT-AS-ACCEPTED: opcode 220 rides the base rate-limit bound (100 frames/min · 1 MiB/frame · 100 MiB cumulative per connection) by design and must NOT get a tighter dedicated row, because (a) dig-gossip performs no per-frame crypto on a 220 frame (the envelope is opaque transport), and (b) 220 is the directed-message streaming transport —StreamFrameOPEN/DATA/CLOSE ride inside the opaque payload, so legit transfers fragment into many 220 frames and need high per-connection cadence; a tighter row would clip legit streaming for no security gain against any abuse the base per-connection bound doesn't already cover. The base bound is real + non-fail-open (handle_messageapplies it before the fail-opencheck_dig_extension). Inner-DigMessageTypelimiting is deferred to dig-node (post-decrypt).Change (doc-only)
docs/resources/SPEC.md§5.3 + the CON-005 spec — a normative note recording the accepted decision + the streaming-transport rationale (prevents a future "harden 220 with a tighter row" regression).Bump
0.17.19 → 0.17.20 (patch — docs, no code/API/wire/format change) — already set in the anchor.
WIP — draft anchor; doc note per the #1780 decider verdict.
Generated by Claude Code