Scope: TRON account permissions
An Active permission combines signer keys, their weights, a threshold and an operations bitmap. The bitmap controls allowed transaction types; it is not simply a spending limit. Review the account's Owner permission and every Active permission together, rather than judging the account from a multisig badge.
A four-part review
Record the permission ID and name. Check every full signer address against the people or devices you expect. Add the weights of the keys that can actually sign and compare that total with the threshold. Finally, decode the allowed operations, paying particular attention to whether an Active permission can update account permissions.
Before changing anything
TRON's documented permission-update operation replaces the complete permission configuration. An apparently small edit can therefore affect other signing paths. Verify key control and rehearse a planned change on a test network before using a valuable account. This checklist is for inspection; it does not supply a ready-to-sign update. A legitimate multisig arrangement may intentionally require several parties. Conversely, a recognizable permission name says nothing about who controls its keys. Preserve the current configuration before discussing a suspected unauthorized change with verified support.
Source and review date
TRON Developer Documentation — original source. Original publication date not verified in this review. Source checked: 2026-10-23.
This is an original Wallet Beep editorial summary. Consult the linked source for its full context and any later updates.