POST
/
95e61622bf6a8af293978377718e3b77
/
wallet
/
updateenergylimit
wallet/updateenergylimit
curl --request POST \
  --url https://tron-mainnet.core.chainstack.com/95e61622bf6a8af293978377718e3b77/wallet/updateenergylimit \
  --header 'Content-Type: application/json' \
  --data '{
  "owner_address": "TSNEe5Tf4rnc9zPMNXfaTF5fZfHDDH8oyW",
  "contract_address": "TG3XXyExBkPp9nzdajDZsozEu4BkaSJozs",
  "origin_energy_limit": 100000000,
  "visible": true
}'
{
  "visible": true,
  "txID": "<string>",
  "raw_data": {
    "contract": [
      "<any>"
    ],
    "ref_block_bytes": "<string>",
    "ref_block_hash": "<string>",
    "expiration": 123,
    "timestamp": 123
  },
  "raw_data_hex": "<string>"
}
TRON API method that updates the origin energy limit for a smart contract. This setting determines the maximum amount of energy the contract creator provides for contract execution, affecting how much energy users need to provide when calling the contract.
Get you own node endpoint todayStart for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.

​
Parameters

  • owner_address — address of the contract owner who can update the energy limit
  • contract_address — address of the smart contract to update energy limit for
  • origin_energy_limit — maximum energy amount the contract creator provides (in sun units)
  • visible — boolean indicating whether to use visible (Base58) address format instead of hex

​
Response

  • visible — boolean indicating whether addresses are in visible format
  • txID — unique transaction ID for the energy limit update transaction
  • raw_data — raw transaction data containing:
    • contract — array with contract update details
    • ref_block_bytes — reference block bytes for transaction validation
    • ref_block_hash — hash of the reference block
    • expiration — transaction expiration timestamp
    • timestamp — transaction creation timestamp
  • raw_data_hex — complete transaction data encoded in hexadecimal format

​
Use case

The wallet/updateenergylimit method is used for:
  • Setting energy subsidies for contract users to improve user experience.
  • Managing contract execution costs by controlling energy allocation.
  • Optimizing contract economics by adjusting energy provision strategies.
  • Implementing freemium models where basic operations are subsidized.
  • Balancing between contract owner costs and user accessibility.
  • Adjusting energy limits based on contract usage patterns and feedback.
Only the contract owner can update the origin energy limit. Higher limits mean the contract owner covers more execution costs, making the contract cheaper for users to interact with. The energy limit is specified in sun units (1 TRX = 1,000,000 sun).

Body

application/json

Response

200 - application/json

Contract energy limit update transaction

The response is of type object.