AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 19 Bitcoin

feat(core): expose tap_to_wake in Features protobuf message

Public commit record

What the developer wrote

Authored by bleska

95/100 · Strong
feat(core): expose tap_to_wake in Features protobuf message

Add optional bool tap_to_wake (field 63) and Capability_TouchWakeup = 26
to the Features protobuf message. Populate both in GetFeatures when
USE_TOUCH_WAKEUP is enabled, consistent with how haptic_feedback and
Capability.Haptic are handled.
Update device_content() in click tests to use features.tap_to_wake is not None
instead of checking internal_model, and update UI test fixtures accordingly.

[no changelog]
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
The short version

What changed, and why it matters

This commit adds a new device-information field called tap_to_wake to the Trezor's Features message, which is the normal response to GetFeatures. It also adds a matching Capability_TouchWakeup flag. The change only reports whether the device supports and has 'tap to wake' enabled; it does not change how the device wakes, how it authorizes transactions, or how secrets are handled. There is no security fix or vulnerability visible in the diff.

Recommended action

No security action required. Treat as a normal feature commit. If reviewing the broader touch-wake feature, verify that the actual wake-from-sleep implementation does not allow unintended input injection or bypass of the lock screen, but that behavior is outside this commit.

Security signals we found

01

No memory-unsafe code added

02

No cryptographic or authorization logic changed

03

No new external input parsing beyond an optional bool field in an existing protobuf

04

No changelog security note; commit is tagged [no changelog]

05

Change is purely informational/capability exposure

Risk score

Why this scored 19/100

Our methodology →
Potential impact 0/30
Exploitability 0/25
Stealth signal 0/15
Affected reach 5/15
Confidence 9/10
Evidence quality 5/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.