feat: trezor hardware support#507
Merged
Merged
Conversation
Introduce BLE-based Trezor support including device discovery, connection management, PIN/passphrase/pairing flows, address generation, message signing, transaction creation/signing, and balance lookup. Gated behind dev settings.
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
# Conflicts: # Bitkit.xcodeproj/project.pbxproj # Bitkit.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved # Bitkit/AppScene.swift # Bitkit/Info.plist # Bitkit/MainNavView.swift # Bitkit/Views/Settings/Advanced/AdvancedSettingsView.swift
# Conflicts: # Bitkit.xcodeproj/project.pbxproj
This was referenced May 21, 2026
ovitrif
approved these changes
May 21, 2026
Collaborator
There was a problem hiding this comment.
LGTM 🙌🏻
Tests:
- Validated the Trezor dev settings dashboard flows end-to-end.
- Tested device discovery, connect, connected-device info, disconnect, reconnect, forget device, and credential reset.
- Tested recoverable unavailable-device/error state.
- Tested network selection.
- Tested address generation for Legacy, Nested SegWit, Native SegWit, and Taproot addresses, including QR rendering.
- Tested public key and xpub export.
- Tested message signing, valid signature verification, and tampered-message failure.
- Tested balance lookup by address, balance lookup by xpub, and UTXO/account result display.
- Tested transaction history lookup and transaction detail lookup.
- Tested compose, sign, broadcast, and txid result for an on-chain transaction.
- Tested PIN, passphrase, pairing-code prompt surfaces, cancel paths, and confirm-on-device overlay.
- Tested debug log behavior and redaction checks for mnemonic/passphrase leakage.
I've setup a Trezor emulator bridge and an automated testing suite to run the same validation flow in:
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.
Description
The intention of this Trezor dev dashboard is to serve as a place for developers to test and troubleshoot Trezor hardware features as they emerge. This is not meant to be user facing, but to serve as a reference for how to use and interact with Trezor hardware devices once work on user-facing Trezor features begin by the mobile team.
Settings->Advanced->Trezor