Merged
Conversation
danieljperry
temporarily deployed
to
Review 926
GitHub Actions
Inactive
BrandtH22
reviewed
Feb 27, 2026
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
2 participants
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.
Note
Low Risk
Low risk: documentation-only change that expands explanatory text; no runtime/code behavior is modified.
Overview
Clarifies and expands the
Recoverytooltip documentation by redefining recovery as vault rekeying (spend key, recovery key, and timelock) and splitting it into Instant Recovery vs Timelocked Recovery.Adds concrete instant-recovery scenarios (new device, emergency recovery after recovery-key exposure, and multisig member replacement) and explicitly states when a timelocked recovery is required.
Written by Cursor Bugbot for commit 02f7514. This will update automatically on new commits. Configure here.