Route transaction submissions across managed providers - #464
Draft
czarcas7ic wants to merge 2 commits into
Draft
Conversation
|
Codex Review: Didn't find any major issues. More of your lovely PRs please. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
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.
Route all transaction submission independently from wallet sync for explicit mainnet presets. Provider order is transaction-ID deterministic, all regions for one provider are attempted concurrently, and provider groups fall back sequentially with the configured provider last. Custom, legacy, testnet, regtest, and masquerade endpoints remain current-endpoint-only.
All software, PCZT, migration, native iOS outbox, and sync resubmission paths share one Rust dispatcher. Active migrations persist the endpoint and routing mode together, while ambiguous submission outcomes preserve conservative local recovery state. Sync, transaction enhancement, and block download continue using the configured endpoint.
The scope deliberately excludes provider health history or persistent route selection. Current-endpoint-only paths stay pinned to the configured endpoint, although the shared dispatcher may open a fresh submission channel rather than reuse a sync channel.