docs(support): document PNA preflight fix + DIG_NETWORK_GENESIS override#31
Merged
Merged
Conversation
dig-node v0.13.0 now sends Access-Control-Allow-Private-Network on preflight (fixes Chrome PNA blocking the extension from reaching a local node) and honors DIG_NETWORK_GENESIS to bring gossip peer bring-up up under a chosen genesis id ahead of the real mainnet genesis. Document both in support/troubleshooting.md (+ audiences index teaser) and protocol/peer-network.md, and mirror the change across all 14 locale copies per the mechanical-duplicate i18n policy (this also catches audiences/troubleshooting.md and protocol/peer-network.md up on pre-existing drift from an earlier English-only update). Patch version bump (0.3.18 -> 0.3.19): docs-content-only change, no site behavior/feature change. Refs DIG-Network/dig_ecosystem#285 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.
Summary
dig-nodev0.13.0+ sendsAccess-Control-Allow-Private-Network: trueon preflight, fixing Chrome's Private Network Access blocking the browser extension from reaching a local node (new "Node & browser extension" section insupport/troubleshooting.md+ a matching teaser inaudiences/troubleshooting.md).DIG_NETWORK_GENESISenvironment-variable override for gossip peer bring-up (network_id) inprotocol/peer-network.md, stating plainly that the real mainnet genesis is not yet public/decided and is never hardcoded.support/troubleshooting.md,audiences/troubleshooting.md,protocol/peer-network.md) across all 14 locale copies underi18n/*, per this repo's mechanical-duplicate i18n policy. Verified every locale copy is byte-identical to its English source after the change.audiences/troubleshooting.mdandprotocol/peer-network.mdwere already stale in all 13 locales (behind an earlier English-only update) before this PR — the re-copy also catches them up, which is desired per the sync policy.support/troubleshooting.mdlocales were already in sync.Version bump
Patch:
0.3.18->0.3.19— docs-content-only change, no site behavior/feature change (fix-equivalent per SemVer rules for this repo).Verified
npm run typecheck— clean.npm run build— Docusaurus build succeeds foren+ all 13 locales, hreflang sitemap generation completes (117 URLs × 15 alternates). Pre-existingidlocale plural-form warnings are unrelated to this change.Refs DIG-Network/dig_ecosystem#285 (the primary dig-node fix lands in a separate PR that closes that issue).
🤖 Generated with Claude Code