> For the complete documentation index, see [llms.txt](https://tron-energy.gitbook.io/tronzap/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tron-energy.gitbook.io/tronzap/learning-hub/staking-trx.md). # Staking TRX Staking on TRON refers to locking TRX tokens to obtain network resources (Bandwidth and Energy) and participate in governance. By staking TRX, you contribute to network security, gain access to resources needed for transactions and smart contract execution, and receive voting power to influence protocol decisions. ## Stake 2.0 (Current Mechanism) Stake 2.0 is the current staking mechanism on TRON, introduced in 2023. It replaces the legacy Stake 1.0 system and provides greater flexibility, including the ability to delegate resources to other accounts. ### How Stake 2.0 Works Users lock TRX via the `freezebalancev2` system contract. When staking, you choose which resource to receive: **BANDWIDTH** or **ENERGY**. The amount of resource obtained is proportional to the amount of TRX staked relative to the total network stake. Staked TRX also grants voting power (TRON Power): **1 staked TRX = 1 vote**. You can use this voting power to vote for Super Representatives or delegate it to others. A key feature of Stake 2.0 is **resource delegation**. Staked TRX can be delegated to other accounts. This enables services like TronZap, which stake large amounts of TRX, accumulate Energy, and delegate that Energy to users who pay a rental fee. ### Unstaking To unstake TRX, call the `unfreezebalancev2` system contract to begin the unstaking process. A **14-day waiting period** applies before TRX can be withdrawn. After the waiting period expires, call `withdrawexpireunfreeze` to reclaim your TRX. ## Stake 1.0 (Deprecated) Stake 1.0 was the original staking mechanism on TRON. It is now fully deprecated and should not be used for new positions. Stake 1.0 used the `freezebalance` and `unfreezebalance` system contracts. Unlike Stake 2.0, it did not support resource delegation to other accounts. All Stake 1.0 positions should be migrated to Stake 2.0. ## Why Staking Matters for TronZap TronZap and similar services stake large amounts of TRX to accumulate Energy, then delegate that Energy to users who pay a rental fee. This model is more cost-effective than each user staking individually, because: * **Economies of scale**: A single large stake yields better resource efficiency than many small stakes. * **No lock-up for users**: Users can rent Energy on demand without locking their own TRX for 14 days. * **Flexibility**: Users pay only for the Energy they need, when they need it. If you stake TRX yourself, you receive resources and voting power directly. If you use TronZap, you rent delegated Energy without staking, which is often more practical for occasional or variable usage. ## Related Pages * [Voting for Super Representatives](/tronzap/learning-hub/voting-for-super-representatives.md) * [TRON Resource Model](/tronzap/learning-hub/tron-resource-model.md) * [Resource Delegation](/tronzap/learning-hub/resource-delegation.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://tron-energy.gitbook.io/tronzap/learning-hub/staking-trx.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.