Export both Casa pairing keys by QR and microSD - #665
Draft
Jacksper13 wants to merge 3 commits into
Draft
Conversation
Jacksper13
force-pushed
the
casa-crypto-account-export
branch
2 times, most recently
from
August 12, 2026 22:01
3b114e4 to
93d88af
Compare
Jacksper13
marked this pull request as ready for review
August 12, 2026 22:06
Jacksper13
changed the title
mjg-foundation
force-pushed
the
casa-crypto-account-export
branch
from
August 27, 2026 20:33
cc9abc1 to
af41e63
Compare
mjg-foundation
marked this pull request as draft
August 27, 2026 22:14
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.
Summary
Casa is moving Passport pairing to provide both the root public key used by existing vaults and the hardened
m/45'public key used by new vaults. Casa can select the correct key without asking the user to choose a compatibility mode, whether the user pairs by QR or microSD.What changed
crypto-accountQR payload.m/45'block.sh(wpkh(hdkey)), matching Casa's nested-SegWit vault format.Safety and compatibility
Only public keys and chain codes are exported. The legacy root-key section remains unchanged for existing file importers. The
m/45'node stays inside Passport's sensitive-values scope and is wiped with the other derived key material when the export completes.The complete 226-byte CBOR payload is pinned by the same deterministic fixture used by Passport Prime, so accidental wire-format changes fail CI.
Validation