Resource Delegation
Overview
Resource delegation allows one TRON account to provide Bandwidth or Energy to another account without transferring TRX. This is a core feature of Stake 2.0 and the mechanism that powers services like TronZap.
How Delegation Works
A staker locks TRX via Stake 2.0 to obtain resources
Instead of using those resources themselves, the staker can delegate them to any other TRON address
The recipient account can then use the delegated resources for transactions
The staker retains ownership of the staked TRX — only the resource usage rights are transferred
Delegation is performed via the
delegateresourcesystem contractTo reclaim delegated resources, the staker calls
undelegateresource
Delegation Parameters
Resource type: BANDWIDTH or ENERGY
Receiver address: the TRON address that will receive the resources
Amount: specified in TRX (the system converts this to the corresponding resource amount)
Lock period (optional): if set, the delegation cannot be revoked for the specified duration
When the lock period expires, the staker can undelegate at any time
Use Cases
Energy rental services (like TronZap): stake large pools of TRX, delegate Energy to paying users for a set duration, then reclaim it
Subsidizing user transactions: DApps can delegate resources to their users so they don't need to hold TRX
Team/organization resource sharing: a treasury account stakes TRX and delegates resources to operational wallets
How TronZap Uses Delegation
TronZap maintains a pool of staked TRX generating Energy
When a user pays for energy rental, TronZap automatically delegates the requested amount of Energy to the user's address
The delegation typically lasts for 1 hour (for direct recharge) or as specified by the subscription
After the period expires, the Energy is reclaimed and returned to the pool
This model is more cost-effective for users than staking TRX themselves, because: (a) no capital lock-up, (b) no 14-day unstaking wait, (c) pay only for what you need
Delegation Flow
Related Pages
Last updated