Becoming a Super Representative

📘
Prerequisites

Super Representatives

Consensus and DPoS

Accounts and keys

Becoming a Super Representative (SR) takes one transaction to register, a few optional transactions to configure your candidate profile, and a running TRON node to participate in block production once you reach the active 27. This guide walks through each phase using wallet-cli as the reference client.

Overview

Phase	What you do	Cost	Outcome
Apply	Submit `WitnessCreateContract` with your SR URL	9,999 TRX (burned)	Account becomes an SR Candidate (`is_witness: true`)
Configure	Optionally set brokerage and SR account name	Network fee only	Profile shown to voters
Operate	Run a TRON node with the `--witness` flag	Hardware + uptime	Eligible to produce blocks once in the top 27
Govern	Submit proposals; active SRs also vote on them	Network fee only	Influence chain parameters

Apply for SR candidacy

Submitting a WitnessCreateContract registers your account as an SR Candidate. The 9,999 TRX application fee is burned and cannot be reclaimed, even if you later stop being an SR. We recommend depositing roughly 10,100 TRX so subsequent transactions (updating your URL, name, or brokerage) still have Bandwidth headroom.

The transaction takes one parameter — the SR's website URL. Replace it with your own.

wallet> CreateWitness https://example-sr.com
...
txid is e58cbd7f8ef280c3e53c36c43e9ae5ad852af6735e439b37f65f9e0744625789
CreateWitness successful !!

After the transaction is included in a block (~3 seconds), confirm the candidate status with getaccount:

wallet> getaccount TBRmnXKMEVfQ8XeQA2NroC9cGi77TvPbNb
{
    "address": "TBRmnXKMEVfQ8XeQA2NroC9cGi77TvPbNb",
    ...
    "is_witness": true,
    ...
}

If is_witness is missing, the transaction was not accepted on-chain — check the wallet-cli error and retry.

Configure brokerage (optional)

Brokerage is the percentage of total reward (block + voter rewards) the SR keeps before passing the rest to voters. The default is 20% — SR keeps 20%, voters share 80%. Valid range is 0–100; setting 100 means the SR keeps everything and voters earn nothing.

wallet> updateBrokerage TBRmnXKMEVfQ8XeQA2NroC9cGi77TvPbNb 100
...
UpdateBrokerage successful !!!

A brokerage change takes effect at the next Maintenance Period boundary.

Set the SR account name (optional)

Setting a human-readable account name helps voters identify you on TronScan and in wallets.

⚠️
Account names are immutable
An account name can be set only once per account under the current Mainnet configuration. Once set, it cannot be changed or cleared. Test the exact name on Testnet before running UpdateAccount on Mainnet.
The set-once rule is gated by chain parameter #14 (ALLOW_UPDATE_ACCOUNT_NAME). When this parameter is 0 — the current Mainnet value — names are immutable after first set. If a future proposal flips it to 1, accounts will be able to rename freely.

wallet> UpdateAccount SR-Name
...
Update Account successful !!!!

Verify with getaccount; the account_name field will show the new value.

Run an SR node

An SR Candidate becomes an active block producer only when its vote count is in the top 27 at a Maintenance Period boundary. Until then, the node still needs to be running and synced — voters check node liveness on TronScan before voting.

Download the latest data snapshot to skip multi-day cold sync.
Deploy a full node and start it with the --witness flag (see SR node configuration for key delegation).
Verify sync by comparing your node's height to TRONSCAN. Use wallet/getnowblock and wallet/getnodeinfo.

The active set is recomputed by votes at each Maintenance Period boundary (every 6 hours by default). See Consensus and DPoS for how the 27-SR election interacts with block production timing.

Participate in proposals

Any SR, SR Partner, or SR Candidate can submit a ProposalCreateContract to change a network parameter; only active SRs' approvals are counted at proposal expiry (≥ 18 of 27).

For the full proposal lifecycle, voting rules, and committee rotation effects, see Committee & proposals.
For a copy-paste TronWeb walkthrough — build, sign, broadcast, and track approvals — see the Create a Governance Proposal recipe.
For the full list of modifiable parameters and their current values, see Network parameters.

Related resources

SR node configuration — Separate block-production keys from owner keys with witness permission.
SR best practices — Availability, security, monitoring, and community guidelines for production SRs.
Consensus and DPoS — How the 27-SR active set is elected, how blocks become irreversible, and how rewards are paid.
Committee & proposals — Full proposal lifecycle: submit, vote, expire.
Create a Governance Proposal — TronWeb recipe to submit a proposal end-to-end.