Skip to content

feat: expose trezor lock state#104

Open
ovitrif wants to merge 1 commit into
masterfrom
feat/trezor-lock-state
Open

feat: expose trezor lock state#104
ovitrif wants to merge 1 commit into
masterfrom
feat/trezor-lock-state

Conversation

@ovitrif

@ovitrif ovitrif commented Jun 19, 2026

Copy link
Copy Markdown
Collaborator

Related: synonymdev/bitkit-android#1030, synonymdev/bitkit-android#998

Description

  • Expose Trezor lock state via TrezorFeatures.unlocked so mobile clients can derive pinProtection == true && unlocked == false for locked devices.
  • Add trezor_refresh_features() as an explicit one-shot feature refresh that updates cached features without adding polling.
  • Surface busy transport state as TrezorError::DeviceBusy so clients can back off while the device is busy or awaiting user action.
  • Release: v0.3.1

QA Notes

  • cargo fmt --check
  • cargo test modules::trezor
  • cargo clippy
  • ./build.sh -r --patch all
  • Full cargo test attempted: 384 passed, 11 Blocktank staging HTTP integration tests failed due https://api.stag.blocktank.to request timeouts/client errors, 25 ignored.
  • Published release: v0.3.1
  • Release workflow started for v0.3.1: https://github.com/synonymdev/bitkit-core/actions/runs/27844624404

@ovitrif ovitrif changed the title Expose Trezor lock state feat: expose trezor lock state Jun 19, 2026
@ovitrif ovitrif self-assigned this Jun 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant