**[blocker]** The supplied `payload.primaryType` does not affect this signature or the digest: both calls receive only `domain`, the complete `types` map, and `message`; `primaryType` is merely echoed on line 35. With a payload that explicitly selects a declared type other than TronWeb’s inferred root, the command can therefore sign one type while reporting another. Please derive the type set rooted at the selected `primaryType` (or reject an incompatible selection) and use that same selection for signing

[blocker] The supplied payload.primaryType does not affect this signature or the digest: both calls receive only domain, the complete types map, and message; primaryType is merely echoed on line 35. With a payload that explicitly selects a declared type other than TronWeb’s inferred root, the command can therefore sign one type while reporting another. Please derive the type set rooted at the selected primaryType (or reject an incompatible selection) and use that same selection for signing, digesting, and reporting.

Originally posted by @matrix-agent116 in https://github.com/tronprotocol/wallet-cli/pull/957#discussion_r3642830827

Start by tracing the command implementation and the two signing or digest calls described in the issue, including the line where primaryType is echoed. Compare TronWeb’s inferred root with an explicitly selected declared type. Done means signing, digesting, and reporting consistently use the selected compatible root, or reject an incompatible selection, with focused tests for both cases.