fix(protob): remove wrong message annotation
What the developer wrote
Authored by Ioan Bizău
fix(protob): remove wrong message annotation
[no changelog]
What changed, and why it matters
This commit removes a single incorrect documentation comment ('@next TxRequest') from a protocol buffer definition file. It is a documentation-only cleanup with no change to executable code, message structure, or device behavior. There is no security relevance.
No action required. This is a non-functional documentation cleanup.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff deletes the ‘@next TxRequest’ annotation in the comment block preceding the PaymentRequest message in common/protob/messages-common.proto. ‘@next’ annotations are used by Trezor’s protocol documentation generator to indicate the expected following message in a workflow. The annotation was apparently wrong because PaymentRequest is not followed by TxRequest in the actual protocol flow. This is purely a metadata/documentation fix; the generated protobuf code and firmware logic are unchanged.
Changed components
common/protob/messages-common.protoInspect captured patch +0 / −1
diff --git a/common/protob/messages-common.proto b/common/protob/messages-common.proto
index 8086c1e20..ea0beb517 100644
--- a/common/protob/messages-common.proto
+++ b/common/protob/messages-common.proto
@@ -176,7 +176,6 @@ message HDNodeType {
/**
* Structure representing a SLIP-0024 payment request.
- * @next TxRequest
* @embed
*/
message PaymentRequest {
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.