feat: route OneKey desktop channel via HWI sidecar#97
Draft
wabicai wants to merge 10 commits intoKeeperCommunity:mainfrom
Draft
feat: route OneKey desktop channel via HWI sidecar#97wabicai wants to merge 10 commits intoKeeperCommunity:mainfrom
wabicai wants to merge 10 commits intoKeeperCommunity:mainfrom
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
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.
Background
This PR routes OneKey through the unified desktop chain:
bitcoin-keeper -> keeper-desktop -> HWI sidecar -> OneKeyand aligns OneKey behavior with Trezor-style capability boundaries.
What changed
PIN interaction split by OneKey model (new)
To align with real OneKey device behavior and hardware-js-sdk model grouping:
classic / classic1s / classicpure=> host PIN matrix flow (promptpin+sendpin) via modal input.pro / touch=> on-device PIN flow (desktop shows waiting modal, user unlocks on device, then continue).Implementation details:
OneKeyPinModalfor on-device PIN confirmation flow.trezorfetch/set-client path aftersendpin).Dependency
Validation
Local project checks:
npm run lintnpm run buildcd src-tauri && cargo checkUpstream HWI real-device validation (documented in HWI PR #826):
Desktop manual regression checklist (real devices):