chore: handle PaymentNotification messages
What changed, and why it matters
This commit simply adds a routing entry so that when the Trezor device receives a 'PaymentNotification' message, it knows which internal module to run. There is no visible security fix or vulnerability here—only a new message handler being wired up.
No security action required based on this commit alone. If reviewing for security, inspect the implementation of apps.misc.payment_notification to determine whether it handles untrusted input safely.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds one conditional branch in core/src/apps/workflow_handlers.py: when msg_type equals MessageType.PaymentNotification, the dispatcher returns ‘apps.misc.payment_notification’. This is a registration of a new message type handler. The actual implementation of apps.misc.payment_notification is not shown, and no security-relevant change is present in the supplied diff.
Changed components
core/src/apps/workflow_handlers.pyInspect captured patch +2 / −0
diff --git a/core/src/apps/workflow_handlers.py b/core/src/apps/workflow_handlers.py
index 4a8627390..270f46d0d 100644
--- a/core/src/apps/workflow_handlers.py
+++ b/core/src/apps/workflow_handlers.py
@@ -114,6 +114,8 @@ def _find_message_handler_module(msg_type: int) -> str:
return "apps.evolu.sign_registration_request"
if msg_type == MessageType.EvoluGetDelegatedIdentityKey:
return "apps.evolu.get_delegated_identity_key"
+ if msg_type == MessageType.PaymentNotification:
+ return "apps.misc.payment_notification"
if not utils.BITCOIN_ONLY:
# When promoting the Nostr app to production-level
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.