Release 5tratSmack 0.11.13 wallet recovery checks to DEV - #43
Merged
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.
Users can now run a quarterly recovery check for both wallets: test the saved wallet password, download an encrypted or explicitly acknowledged unencrypted recovery file, and read the saved file back without replacing a wallet or moving funds. Encryption is selected by default. The check records success only after the password and saved backup have been tested.
Pin app 0.11.13 to source
53f0415e517952a98d21f02b11009976a16a1d20and multi-platform digestsha256:70d007cf7a65fcdbee82d50c70d48aacb63af66b4cd9985e919bd99387401a42. Portable backups also preserve inactive private descriptors and address indices above 1,000. The app redacts backup tokens from logs and updates cryptography to 50.0.1.Validation: private application checks and AMD64/ARM64 builds passed. The exact candidate image passed real Core encrypted and unencrypted export, read-back, restore, ownership, balance, and replacement-password tests on an isolated regtest node at 10.10.10.235. Store metadata validation passed; non-app image pins are unchanged.