Guides
  1. Super Representatives and Governance

Network parameters

Common TRON network parameters and live query entry points — resource pricing, rewards, TVM features, proposal expiration, and more.

📘

Prerequisites

The TRON network exposes a set of dynamic parameters that govern how the chain behaves — resource pricing, block rewards, TVM features, proposal expiration, and more. Their current values live on-chain. Parameter IDs, permitted ranges, fork or version prerequisites, dependencies, and one-way activation rules are enforced by the java-tron protocol implementation. Committee proposals can change values only within those rules; not every value is arbitrary or reversible.

Any Super Representative, SR Partner, or SR candidate can create a proposal, but only approvals from Committee members (the 27 active Super Representatives) count toward the threshold. A proposal passes when at least 18 active SRs have approved it by the end of the validity window.

This page covers how to read parameter values, lists a handful of representative parameters for orientation, and points to the canonical sources for the full live list. For the mechanics of creating and voting on proposals, see Committee & proposals; for an end-to-end TronWeb walkthrough, see the Create a Governance Proposal recipe.

How parameters are read

Each parameter has a numeric ID. You can query the current value of every parameter via the wallet/getchainparameters API. Block explorers like TronScan also expose the current parameter values on their governance pages.

Before accepting a ProposalCreateContract, a node validates its parameter values against the ranges, fork prerequisites, dependencies, and activation rules implemented by its java-tron version. Once the proposal is on-chain, the first maintenance-triggering block at or after expiration tallies approvals from the active SR set in effect before that block's maintenance update. If the approval threshold is met, the proposed values are applied.

Where to query the complete live list

📘

This page does not maintain the full parameter list.

The TRON network has 70+ dynamic parameters today, and the set grows with each protocol upgrade. To avoid stale documentation, only a few representative examples are listed below. For the complete current list with live values, use either:

  • TRONSCAN governance page — tronscan.org/#/sr/parameter — human-readable table with descriptions and current values
  • Live API — POST wallet/getchainparameters against any TRON node — machine-readable JSON keyed by API name (e.g. getMaintenanceTimeInterval, getEnergyFee)

A synchronized Mainnet node returns its local chain state directly through wallet/getchainparameters. TRONSCAN is a near-real-time index and may lag briefly. If the two differ, use a confirmed-synchronized Mainnet node for the current value and the matching java-tron version for validation constraints.

Representative parameters

The examples below are illustrative — they are not an exhaustive list. They cover the parameters developers most often need when budgeting fees, planning staking timelines, or following SR governance. Values shown reflect Mainnet at the time of writing; query the API or TRONSCAN for the live state.

Network-level — governance, SR economy, protocol cadence

IDNameCurrent valueNotes
#0getMaintenanceTimeInterval6 hoursThe cycle on which SR active-set rotation, vote counts, brokerage changes, and proposal tallies are processed
#1getAccountUpgradeCost9,999 TRXFee paid to apply as an SR Candidate. With the current Mainnet setting getAllowOptimizeBlackHole=1, the protocol records this amount directly as burned and removes it from circulation; it is not credited to the black-hole account and cannot be reclaimed
#5getWitnessPayPerBlock8 TRX per blockBlock production reward paid to the SR that produces the block
#31getWitness127PayPerBlock128 TRX per blockVoting reward pool shared by the top 127 SRs and SR Partners, weighted by votes received
#92getProposalExpireTime3 daysBase voting window for a new proposal; effective expiration advances to the first scheduled maintenance time after the base window

User-facing — fees and resources every developer plans against

IDNameCurrent valueNotes
#11getEnergyFee100 sun (= 0.0001 TRX) per EnergySun price of one Energy unit when burning TRX to pay for a contract call
#47getMaxFeeLimit15,000 TRXPer-transaction fee_limit ceiling for smart-contract calls. A transaction whose fee_limit exceeds this is rejected
#61getFreeNetLimit600 BandwidthFree Bandwidth allowance per account per day (~ 2 simple TRX transfers)
#70getUnfreezeDelayDays14 daysWait time between unfreezebalancev2 and withdrawexpireunfreeze in Stake 2.0

Reading a parameter in code

Query all current parameter values with one call:

BASE_URL=https://api.trongrid.io   # example — replace with any TRON node (TronGrid, third-party, or self-hosted)
curl -X POST ${BASE_URL}/wallet/getchainparameters

The response is a JSON object with a chainParameter array, each entry being {key, value}. The key is the descriptive string shown in the Name column above, such as getEnergyFee. The numeric ID is used when creating a governance proposal; it is not returned as the API key.

{
  "chainParameter": [
    { "key": "getMaintenanceTimeInterval", "value": 21600000 },
    { "key": "getAccountUpgradeCost", "value": 9999000000 },
    { "key": "getCreateAccountFee", "value": 100000 }
  ]
}

Note that values returned by the API are in base units — TRX values come in SUN (1 TRX = 1,000,000 SUN), and interval values come in milliseconds.

Related resources

Updated 4 days ago