Network parameters
The list of TRON network parameters that the Committee can modify through proposals — resource pricing, rewards, TVM features, governance thresholds, 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 thresholds, and more. These parameters are not hard-coded in the protocol. They live on-chain and can be modified through the proposal process.
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.
When a proposal passes, the new parameter value takes effect at expiry, the same moment active-SR approvals are counted.
Where to find the full 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/getchainparametersagainst any TRON node — machine-readable JSON keyed by API name (e.g.getMaintenanceTimeInterval,getEnergyFee)Both sources are always in sync with the live Mainnet state.
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
| ID | Name | Current value | Notes |
|---|---|---|---|
| #0 | getMaintenanceTimeInterval | 6 hours | The cycle on which SR active-set rotation, vote counts, brokerage changes, and proposal tallies are processed |
| #1 | getAccountUpgradeCost | 9,999 TRX | Fee paid to apply as an SR Candidate. Burned to the black-hole address — not reclaimable, even if the account stops being an SR |
| #5 | getWitnessPayPerBlock | 8 TRX per block | Block production reward paid to the SR that produces the block |
| #31 | getWitness127PayPerBlock | 128 TRX per block | Voting reward pool shared by the top 127 SRs and SR Partners, weighted by votes received |
| #92 | getProposalExpireTime | 3 days | Base voting window for a new proposal; effective expiration rounds up to the next Maintenance Period boundary |
User-facing — fees and resources every developer plans against
| ID | Name | Current value | Notes |
|---|---|---|---|
| #11 | getEnergyFee | 100 sun (= 0.0001 TRX) per Energy | Sun price of one Energy unit when burning TRX to pay for a contract call |
| #47 | getMaxFeeLimit | 15,000 TRX | Per-transaction fee_limit ceiling for smart-contract calls. A transaction whose fee_limit exceeds this is rejected |
| #61 | getFreeNetLimit | 600 Bandwidth | Free Bandwidth allowance per account per day (~ 2 simple TRX transfers) |
| #70 | getUnfreezeDelayDays | 14 days | Wait time between unfreezebalancev2 and withdrawexpireunfreeze in Stake 2.0 |
Every value here is itself proposable — a committee proposal can change any of these, after which wallet/getchainparameters reflects the new value within one Maintenance Period.
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/getchainparametersThe response is a JSON object with a chainParameter array, each entry being {key, value}. The key matches the parameter number in the table above.
{
"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
- Committee & proposals — the 27 SRs that vote on proposals
- Create a Governance Proposal — TronWeb recipe to submit and track a proposal
- Super Representatives — chapter overview
wallet/getchainparameters— query current parameter valueswallet/proposalcreate— create a new proposal
Updated 7 days ago