Repository navigation
Fix default-node failover and wallet loading after PIN - #484
Draft
takemiyamakoto wants to merge 2 commits into
Draft
takemiyamakoto wants to merge 2 commits into
takemiyamakoto 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.
A valid PIN could leave the wallet on its keypad when local chain or asset services were not ready. The only bundled SORA node was also a single point of failure, and the fallback socket could be replaced without being started. Authentication now opens a bounded startup screen that retries late services, then offers retry and node selection. Missing wallet verification still routes to a recheck; no signing material or recovery marker is changed.
SORA mainnet now has deterministic bundled defaults at
wss://ws.mof.sora.organdwss://mof2.sora.org. Both were checked through standard-TLS WebSocket RPC against the exact SORA mainnet genesis. Failover retains the subscribed engine, starts the replacement socket, and preserves the user's saved node choice. Cold boot saves local chain/defaults before fetching optional asset metadata, and refresh preserves saved custom nodes. Node failures use a status message instead of a blocking alert that incorrectly claims an account was created. Taira's canonical endpoint was checked and remains unchanged.Validation: Swift parsing, a focused semantic compiler check, diff checks, and eight publication-contract tests passed. The full 296-test Release regression run and signed archive are in progress. This includes the prior Google-import/PIN correction. Runtime
bd2641aa55c8081b457316ed19f4cccbc0257313; publication5a362b31a27003695d0d90c787e603bc5b33ad24; build2026091402. The build has not been uploaded or installed; recovery on the reporting iPhone remains unverified.