SIGERROR: TRON rejected the transaction signature
SIGERROR means the node checked the signature and it does not prove the sending address authorised the transaction: most often it was signed with a different private key, or the address uses multi-signature permissions that this signature does not satisfy.
Nothing was broadcast and nothing was charged. Sign again with the key that controls the sending address, under the permission that allows this kind of transaction.
Why a signature is refused
| Cause | Fix |
|---|---|
| Signed with another address's key | Sign with the key of the address in owner_address |
| Multi-signature account, not enough signatures | Collect signatures up to the permission's threshold |
| The permission does not allow this contract type | Use a permission id whose operations include it |
| The transaction was changed after signing | Rebuild and sign again; any change invalidates the signature |
TRON network rules as of 2026-10-01.
FAQ
Was anything charged?
No. A transaction with an invalid signature is refused before it runs.