DPoS and the 27: How TRON's Super Representatives Work

The history article covers Delegated Proof of StakeA consensus design in which coin holders do not validate blocks themselves but vote — with weight proportional to their stake — to elect a small, fixed set of block producers. TRON runs a DPoS system in which the 27 top-voted candidates become the Super Representatives that produce blocks, re-elected at regular intervals, which trades some validator decentralization for fast, cheap blocks. in a paragraph — right for an overview. This goes deeper: how DPoS actually runs, who holds the 27 block-producer seats, how the election works, and why all of it shows up when you read TRON transactionA signed instruction ("tx" for short) that changes on-chain state — transferring value, calling a contract, or updating an account's settings. Once it is included in a block and that block reaches finality the record is permanent: later transactions can supersede its effects, but the entry itself can never be edited or deleted. Before finality, a freshly included transaction can still be reversed if its block is reorganized out. data.

The short version: TRON concentrates block production in a small, elected group, and that concentration is visible on-chain. Knowing who’s in the group, how they got there, and what their addresses look like in the transaction graph separates infrastructure noise from real user behavior.

Three ways to agree on a block

Public blockchainsA shared ledger maintained by many independent computers, in which transactions are grouped into blocks and each block cryptographically references the one before it. Because rewriting any past entry would break every link after it, the record is effectively append-only — new entries can be added, but history cannot be quietly altered. pick one of three consensus families, each trading throughput against decentralization.

• Proof of Work (Bitcoin) spends computation to compete for each block. Security comes from the cost of attacking it, but it’s slow — roughly a block every 10 minutes, with finality after several confirmations.
• Proof of Stake (Ethereum after the Merge) makes validators post staked collateral that gets destroyed — slashed — for cheating. Anyone with enough stake can validate, so the set runs to hundreds of thousands of validators. More decentralized, more coordination overhead.
• Delegated Proof of Stake doesn’t ask tokenA unit of value recorded inside a smart contract rather than in the chain's native ledger — the contract keeps the balance table, and moving tokens means asking the contract to update it. Not to be confused with a coin, which is the chain's built-in asset (TRX on TRON) used to pay for the network itself. holders to produce blocks at all. They elect a small committee to do it, with vote weight proportional to staked tokens. The committee rotates, and members who misbehave get voted out.

DPoS was formalized by Dan Larimer — it’s also behind BitShares and EOS — and it’s the consensus under TRON. The trade-offs fall out of the committee size. A small, known group coordinates fast, so TRON lands a block every three seconds, which PoW can’t touch. But 27 producers is far more concentrated than Ethereum’s validator set; supporters call that fair because the committee is elected, while critics point out that the same entities tend to hold seats indefinitely as votes accumulate. The upside on governance: because producers are known addresses with declared identities, protocol changes get voted on explicitly instead of signaled through miner behavior.

For TRON, the practical consequence is that block production isn’t permissionless. Running a node earns you nothing. You have to win the vote.

The 27 active Super Representatives

At any moment, exactly 27 addresses hold the Super RepresentativeOne of the 27 elected block producers on the TRON network, chosen every six hours from a wider candidate pool by TRON Power voting (one vote per staked TRX); candidates ranked 28th–127th, called SR partners, earn voting rewards without producing blocks. SRs collect block and vote rewards and pass a share to their voters after deducting a self-set commission. TRON's protocol code also calls these producers "witnesses" — a term other DPoS chains such as Steem and Hive use for the same role. (SR) title and produce every block on TRON mainnet. The number is fixed in the protocol.

Each three-second window is a slot, and the 27 active SRs cycle through them on a rotating schedule. If the SR assigned to a slot doesn’t produce — downtime, network trouble, or deliberate skipping — that slot is missed and the next SR takes the next one. The chain doesn’t stall.

With 28,800 slots in a day (86,400 seconds ÷ 3), an even split puts each SR around 1,067 blocks daily — exact counts drift a little with missed slots and rounding.

Block production pays out two ways:

• Block reward — currently 8 TRXThe native coin of the TRON network. TRX settles value directly (no contract call needed), is staked to obtain Energy, Bandwidth, and voting power, and is burned to pay fees when staked resources fall short. Its smallest unit is the sun: 1 TRX = 1,000,000 sun. per block, paid to the SR that produced it. Across a day’s ~28,800 blocks that’s roughly 230,400 TRX.
• Voting reward — currently 128 TRX per block, pooled across all SRs and SR Partners by vote share. That pool runs about 3,686,400 TRX a day, split across all 127 candidates (the 27 SRs plus 100 Partners) weighted by votes.

Both per-block figures are network parameters set by governance — an SR proposal can change either — so read them as current documented values, not fixed constants.

Each SR sets a brokerage rate (or commission rate) that splits rewards between its own addressA public identifier, derived from a key pair, at which an account receives funds and is looked up on-chain. Anyone can view an address's history, but only the matching private key can spend from it. TRON addresses are 34-character Base58Check strings beginning with "T". and its voters. A newly elected SR defaults to 20% — keep 20%, distribute 80% pro rata to voters — and can change it later. SRs courting voter support tend to run lower; SRs backed by entities that vote for themselves, like large exchanges, often sit at the default or higher.

That distribution is a batch on-chain operation: it lands as mass outbound transfers from the SR address. To tooling that doesn’t know TRON’s reward mechanics, an address firing dozens or hundreds of small TRX transfers each epoch can read as suspicious dispersion. It’s almost always an SR paying its voters.

SR Partners — the bench behind the 27

SR status isn’t binary. TRON keeps a ranked candidate list, and the eligible set runs from rank 1 to 127.

Partners are the promotion bench. As vote weight shifts, Partners get promoted into the active 27 and sitting SRs get displaced — the rank 27/28 boundary can move every election. Partner addresses sit in the same reward-distribution chain too, so an address running mass outbound TRX distributions every six hours could just as easily be a Partner as an active SR.

Getting onto the candidate list costs a registration fee of 9,999 TRX, paid on-chain as a WitnessCreateContract transaction. Finding that transaction in a wallet’sSoftware or hardware that stores private keys and uses them to sign transactions. A wallet holds keys, not coins — balances live on the ledger itself — so the same funds can be reached from any wallet loaded with the same keys, and losing the wallet loses nothing if the keys are backed up elsewhere. history is a real identity marker: the address registered as TRON infrastructure, or at least paid to look like it.

Voting runs on TRON Power

Elections never stop — they settle on a clock. Every six hours TRON runs a maintenance period: it tallies the votes, updates the SR rankings, and hands block production to the new top 27. Informally this window gets called an “epoch.”

Votes are denominated in TRON PowerTRON's voting weight: staking TRX grants TRON Power at one unit per TRX staked, spendable as votes for Super Representative candidates. It is non-transferable — it cannot be sent or sold, only earned by staking — and unstaking revokes it along with the votes it was backing. TRON Power is how holdings translate into governance influence under delegated proof-of-stake: block-producer elections are decided by staked, revocable votes rather than by one account, one vote. (TP). Under Stake 2.0, one TRX staked for votes yields one TP, which grants one vote. TP is non-transferable and non-tradeable — it lives on the stakingLocking TRX (historically called freezing) to obtain network resources instead of paying fees per transaction — a stake earns either Energy or Bandwidth, chosen at stake time. Staking also grants TRON Power for Super Representative voting, at one vote per staked TRX, making a wallet's stake both its fee budget and its governance weight. address, and unstaking the TRX removes the TP and its votes at the same time.

The voting act itself has no lock-in. A voter can reallocate votes any time between maintenance periods, and the change takes effect at the next election. Only the staked TRX faces the 14-day unstaking wait introduced by Stake 2.0 (TIP-467, activated April 2023); the voting direction moves freely. So an SR’s vote count can swing hard inside one six-hour window if a large holder shifts allocation.

Voters can also split TP across several candidates. Exchanges and staking services routinely spread votes to hold multiple seats at once, or to prop up Partners sitting near the rank 27 boundary.

Who actually holds the seats

Three kinds of entity dominate the active set.

Major exchanges. Exchanges custodyAn arrangement in which one party — the custodian — holds the private keys or reserves controlling assets that belong to others. On a blockchain, whoever holds the keys is the on-chain owner: custodied funds sit under the custodian's addresses, so the entity an analyst sees acting on-chain is the custodian, not the customer. large amounts of user-deposited TRX. Run an SR node, vote that custodied TRX for yourself, and you collect block and voting rewards on assets held for customers — economically rational, and explicitly permitted by the protocol. Binance Staking has historically ranked among the top vote-getters. The Block’s September 2019 report found Binance’s candidacy captured over 59% of all network votes — and that a single Binance cold wallet, one of roughly 650 addresses voting for it, supplied nearly 12 billion TRX, over 99.60% of the candidacy’s own vote total. Same report, two denominators: a majority of every vote cast on the network, and near-total concentration within Binance’s own supporters. OKX, HTX (formerly Huobi), and Poloniex have also held active seats. Exact rankings move with market conditions and custody volumes.

Dedicated staking services. Operators like P2P.org (elected as an SR in April 2025) exist to run professional node infrastructure. They typically offer voters a revenue share, and sometimes run lower brokerage rates to attract delegation.

Foundation- or Justin-Sun-affiliated entities. TRON’s early SR set included addresses tied to the Foundation. That share has fallen as the network grew, but anyone examining network control should read the current roster and address annotations rather than trust a static description.

Because large holders self-vote and exchanges hold the biggest TRX concentrations, the set leans toward institutional incumbency. Community nodes show up in the Partner tier, but holding an active seat takes vote weight that community operators rarely sustain against institutional competition. This isn’t a TRON quirk — concentration is a structural feature of every DPoS system. For the live roster with current vote counts, TronScan’s SR page is the authoritative source.

Governance: two tracks, one veto

Changing the TRON protocol runs through a spec track and an on-chain track.

TIPs (TRON Improvement Proposals) are the community spec layer. Anyone can author one, starting as a GitHub issue in tronprotocol/tips and moving to a formal pull request. TIPs progress through Draft, Last Call (at least two weeks of public review), and Accepted. An accepted TIP that needs a protocol change then goes on-chain as a network proposal.

Network proposals are the activation layer. Only SRs, SR Partners, and SR Candidates can submit one. If at least 18 of the 27 active SRs vote yes, it passes and takes effect automatically. That 18-of-27 bar — two-thirds plus one — means 10 SRs can block any change. Vote concentration and veto power are the same thing: whoever dominates the set by vote weight holds the off-switch.

Three TIPs show the pipeline in action:

• TIP-467 (Stake 2.0) separated resource delegationA TRON mechanism by which one account lends the Energy or Bandwidth derived from its own staked TRX to another account, without any TRX changing hands. Because it supplies a wallet's operating capacity rather than its funds, delegation marks an ongoing operational relationship — a fee-sponsorship link, not a funding-lineage link — and routine services such as exchanges do not delegate resources to customer wallets. from vote delegation and introduced the 14-day unstaking window. It’s the live staking model on mainnet.
• TIP-541 added the ability to cancel an in-progress unstake within that 14-day window, which required a new API endpoint.
• TIP-542 made the resource-delegation lock period customizable at delegation time, replacing the fixed three-day lock of Stake 2.0’s original boolean lock flag.

All of this is visible on-chain. Proposal creation and SR vote transactions cluster on SR addresses around upgrades. They’re ordinary artifacts of SR status rather than evidence of coordination.

Why it matters when you read the chain

The SR system throws off predictable patterns that anyone working TRON data will hit. Recognizing them kills false positives.

WitnessCreateContract transactions register an SR candidate. One in a wallet means the address self-registered — either it belongs to an entity running TRON infrastructure, or someone paid 9,999 TRX to look like one. Cross-reference TronScan’s SR history to see whether it was ever elected.

Periodic mass-outbound TRX transfers are voting rewards. SRs and Partners pay delegators every maintenance period, producing a rhythmic burst of dozens to hundreds of small TRX transfers, sized to each recipient’s vote share. A system that flags “mass outbound transfers” as suspicious will trip on this. The tells that clear it: six-hour periodicity, proportional amounts, and a sender that’s a registered SR or Partner.

Resource delegation from SR addresses is common — SRs delegate EnergyA TRON network resource that meters the computational cost of smart-contract execution, consumed whenever a transaction calls contract code — including TRC-20 token transfers such as USDT. An account obtains Energy by staking TRX or receiving a delegation from another account; if it holds too little, the shortfall is paid by burning TRX from its balance. or BandwidthA TRON network resource that covers the byte-size cost of putting a transaction on chain — one byte consumes one Bandwidth point. Every account receives a small free daily allowance (also called free bandwidth); heavier usage requires staking TRX, receiving a delegation, or burning TRX to cover the bytes. to their own operational wallets or partner addresses. An SR at the origin of a delegation chain doesn’t imply it controls the recipient; it usually reflects a service relationship, like subsidizing energy for a staking product’s users.

Vote and block-producer traffic. VoteWitnessContract transactions come from voting addresses; a high volume from one address points to an exchange, staking service, or large holder managing allocations — not manipulation. And the block-producing SR is recorded in every block header, so if you need to know which SR was active in a given window, the header answers directly.

This is why SR-affiliated addresses should be read as infrastructure when tracing a wallet’s funding history rather than treated as genuine sources of funds: their outbound transfers are protocol reward distributions, not deliberate funding relationships. Any funding-origin analysis on TRON has to apply that filter, or it will read routine SR reward payouts as real financial backing.

Sources

Primary documentation and data sources used for facts in this article:

• TRON Developer Hub. “Super Representatives” — 27 active SRs, SR Partners (ranks 28–127), block reward (8 TRX/block), voting reward (128 TRX/block), brokerage rate mechanics, WitnessCreateContract registration fee.
• TRON Developer Hub. “Consensus” — DPoS structure, slot-based block scheduling, 3-second block time.
• TRON Protocol documentation. “DPoS Consensus Mechanism” — Authoritative protocol-level description of the DPoS algorithm, maintenance period, and SR election mechanics.
• Larimer, Daniel (Steemit, 2017). “DPOS Consensus Algorithm: The Missing White Paper” — Larimer’s own account of the DPoS design he formalized (first described for BitShares in 2014) and its years of operation on BitShares and Steem.
• GitHub: EOSIO/Documentation. “EOS.IO Technical White Paper v2” — EOS.IO’s use of DPoS as its consensus algorithm (March 2018).
• TRON Protocol documentation. “Super Representative (java-tron)” — SR candidate registration, WitnessCreateContract, and reward distribution mechanics.
• TRON Protocol documentation. “TIPs Workflow” — TIP submission process, status lifecycle (Draft → Last Call → Accepted).
• TRON Protocol documentation. “Governance Workflow” — On-chain proposal creation, SR voting mechanics, 18-of-27 activation threshold.
• GitHub: tronprotocol/tips. “TIP-467: Stake 2.0 — A new TRON stake model” — Stake 2.0 design and 14-day unstaking period.
• GitHub: tronprotocol/tips. “Proposal: enable Stake 2.0” (issue #519) — the network proposal that enabled Stake 2.0 on TRON mainnet, effective April 7, 2023.
• GitHub: tronprotocol/tips. “TIP-541: Support canceling unstaking in Stake 2.0” — Cancel-unstake API.
• GitHub: tronprotocol/tips. “TIP-542 (tip-542.md)” — Customizable resource-delegation lock period.
• TronScan. “Super Representatives list” — Live SR rankings, vote counts, and brokerage rates. (Live data; values change every six hours.)
• P2P.org (Apr 29, 2025). “P2P.org Becomes TRON Super Representative Validator” — issuer announcement of P2P.org’s election as one of the 27 SR validators (April 2025 SR election example).
• The Block (Sept 30, 2019). “Binance adds staking support for TRON; becomes super representative with over 59% of votes” — Binance’s 2019 self-vote to the top SR seat: over 59% of all network votes, with a single Binance cold wallet supplying nearly 12 billion TRX — over 99.60% of the votes backing Binance’s own candidacy.
• TRON DAO Medium. “TRON Developer Guide — Super Representatives” — Developer-facing walkthrough of SR mechanics and reward structure.