Add optional Tor routing to Bitwindow chat - #2277
Open
ekulkisnek wants to merge 2 commits into
Open
ekulkisnek wants to merge 2 commits into
ekulkisnek wants to merge 2 commits into
Conversation
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.
Adds optional Tor-only chat routing and checksum-pinned Tor bundle installation. Tor-only delivery fails closed without falling back to direct connections.
Depends on #2276; merge chat first. The Tor commit adds 1,050 lines and removes 46; this PR includes the chat diff until #2276 merges. Requires the backend changes from LayerTwo-Labs/plain-bitnames#47; live end-to-end validation remains outstanding.
Validation: Flutter analysis, all 499 Bitwindow tests, and orchestrator Go tests, including Tor routing, checksum, and bundle validation.