**[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.

[Mohammedsapry]

[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 tronprotocol/wallet-cli#957 (comment)

[Stan202310]

TronWeb derives the primaryType from types. Therefore, the types can only have one root and the corresponding sub types. You need to pass the correct types value.

[ramincsy]

This primaryType mismatch is a real correctness hazard for typed-data signing — especially when callers intentionally select a non-inferred root type.

I can work on a focused fix that (1) builds the type set rooted at the supplied primaryType or rejects an incompatible selection, and (2) uses that same selection for digest, sign, and reported primaryType, with a failing fixture that currently signs the wrong root.

If there's already preferred API behavior in mind from the wallet-cli discussion, point me at it and I'll follow that.