Uh oh!
There was an error while loading. Please reload this page.
fix(dig-node): correct Discord invite (imposter link -> official) - #30
Merged
Conversation
The old vanity link https://discord.gg/dignetwork resolves to an imposter server. Replace with the official invite across README.md and USER_JOURNEY.md. Co-Authored-By: Claude <noreply@anthropic.com>
Uh oh!
There was an error while loading. Please reload this page.
MichaelTaylor3d pushed a commit
that referenced
this pull request
Aug 2, 2026
stream_module_range (the whole-capsule dig.fetchModuleRange serve — the largest transfer in the system) consulted only the FCFS serve_limiter and recorded outgoing bytes, but never consulted the operator-configured #30 egress budget the way stream_range does. So a configured egress cap was silently bypassed on exactly the path where it matters most. Check bandwidth_redirect once before the first frame, against the window this stream will actually serve: over budget with a known alternate holder, decline with the redirect frame (same {"error": …} shape the not-held answer already uses, which the puller handles by sourcing the window elsewhere); no alternate holder, serve anyway (never drop a request only this node can answer) — identical semantics to stream_range. Tests (mutation-verified): over-cap + a known provider declines/redirects; over-cap + no provider still streams the window. Closes #1616 Co-Authored-By: Claude <noreply@anthropic.com>
MichaelTaylor3d pushed a commit
that referenced
this pull request
Aug 2, 2026
stream_module_range (the whole-capsule dig.fetchModuleRange serve — the largest transfer in the system) consulted only the FCFS serve_limiter and recorded outgoing bytes, but never consulted the operator-configured #30 egress budget the way stream_range does. So a configured egress cap was silently bypassed on exactly the path where it matters most. Check bandwidth_redirect once before the first frame, against the window this stream will actually serve: over budget with a known alternate holder, decline with the redirect frame (same {"error": …} shape the not-held answer already uses, which the puller handles by sourcing the window elsewhere); no alternate holder, serve anyway (never drop a request only this node can answer) — identical semantics to stream_range. Tests (mutation-verified): over-cap + a known provider declines/redirects; over-cap + no provider still streams the window. Closes #1616 Co-Authored-By: Claude <noreply@anthropic.com>
MichaelTaylor3d added a commit
that referenced
this pull request
Aug 2, 2026
…th (#137) stream_module_range (the whole-capsule dig.fetchModuleRange serve — the largest transfer in the system) consulted only the FCFS serve_limiter and recorded outgoing bytes, but never consulted the operator-configured #30 egress budget the way stream_range does. So a configured egress cap was silently bypassed on exactly the path where it matters most. Check bandwidth_redirect once before the first frame, against the window this stream will actually serve: over budget with a known alternate holder, decline with the redirect frame (same {"error": …} shape the not-held answer already uses, which the puller handles by sourcing the window elsewhere); no alternate holder, serve anyway (never drop a request only this node can answer) — identical semantics to stream_range. Tests (mutation-verified): over-cap + a known provider declines/redirects; over-cap + no provider still streams the window. Closes #1616 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 freeto 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
https://discord.gg/dignetworkresolves to an imposter server, not the official DIG Network Discord.https://discord.gg/v78aygUZtin README.md and USER_JOURNEY.md (markdown-only change).[workspace.package].version0.25.0 -> 0.25.1 (patch — docs-only fix, no behavior change) and syncs the correspondingdig-node-serviceentry in Cargo.lock.Test plan
grep -rn "discord.gg/dignetwork"across the repo returns no matches.https://discord.gg/v78aygUZtpresent in README.md and USER_JOURNEY.md.Refs DIG-Network/dig_ecosystem#490
Co-Authored-By: Claude noreply@anthropic.com