Add the doc of resource reclamation upon undelegation #524
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Benson0224
approved these changes
Dec 30, 2025
GordonLtron
reviewed
Dec 30, 2025
docs/mechanism-algorithm/resource.md
Outdated
| **Note**: In the TRON network, the amount of resources an account receives depends on the proportion of its TRX staked relative to the total TRX staked across the entire network. When a delegator delegates resources to a recipient, it essentially lends a portion of its own staked TRX to the recipient. In resource quota calculations, the system does not distinguish between the sources of TRX. TRX staked by the account itself and TRX delegated from other accounts are aggregated and treated uniformly as the weighting basis for resource allocation. So, unless otherwise specified, the term “staked amount” in this chapter refers to the total staked TRX of an account, including both self-staked TRX and TRX delegated from other accounts, without distinguishing their sources. | ||
| When a Delegator initiates resource delegation, a certain amount of staked TRX is lent to the Recipient, granting them the corresponding resources usage right. When the Delegator cancels the resource delegation, the system not only reclaims the corresponding staked TRX, but also reclaims a proportional amount of the Recipient’s unrecovered resources. |
Contributor
There was a problem hiding this comment.
granting them the corresponding resources usage right. > granting them the right to use the corresponding resources.
GordonLtron
reviewed
Dec 30, 2025
docs/mechanism-algorithm/resource.md
Outdated
| × Recipient’s unrecovered resource amount | ||
| ``` | ||
| **Note**: The reclaimed unrecovered resources **must not exceed** the maximum resource capacity corresponding to the undelegated TRX amount, calculated in real time based on current network-wide staking. |
Contributor
There was a problem hiding this comment.
based on current network-wide staking. > based on the total network staking.
GordonLtron
reviewed
Dec 30, 2025
| * **Recipient's Total Staked TRX Amount for that resource**: The total staked TRX used by the recipient to obtain a specific resource (Energy or Bandwidth), including self-staked TRX (Stake 1.0 and Stake 2.0) and delegated TRX from others. This can be queried via the [wallet/getaccount](https://developers.tron.network/reference/account-getaccount#/) API. | ||
| * **Recipient's Unrecovered Resource Amount**: The amount of resources that have already been consumed and are currently in the recovery period on the recipient’s account. This can be queried via [wallet/getaccount](https://developers.tron.network/reference/account-getaccount#/) or [wallet/getaccountresource](https://developers.tron.network/reference/getaccountresource#/). | ||
| ##### 2. Account State Changes |
Contributor
There was a problem hiding this comment.
Account State Changes > Account State Updates
Contributor
Author
There was a problem hiding this comment.
This actually describes the changes in data for both accounts, rather than an update.
GordonLtron
reviewed
Dec 30, 2025
docs/mechanism-algorithm/resource.md
Outdated
| ``` | ||
| Reclaimed unrecovered resources | ||
| = (Canceled delegated TRX amount / Recipient’s total staked TRX amount for that resource) | ||
| × Recipient’s unrecovered resource amount |
Contributor
There was a problem hiding this comment.
"×" Recipient’s unrecovered resource amount >
"*" Recipient’s unrecovered resource amount
GordonLtron
reviewed
Dec 31, 2025
docs/mechanism-algorithm/resource.md
Outdated
| Unrecovered resource amount = Original unrecovered resource amount - Reclaimed unrecovered resource amount | ||
| ``` | ||
| **Note on Recovery:** Resources recover linearly over a **24-hour period**. If an account uses resources again or reclaims delegated resources during this period, the system performs a weighted merger of the existing recovery progress and the new recovery cycle. Consequently, the actual time remaining for resources to fully recover is usually less than 24 hours. |
Contributor
There was a problem hiding this comment.
Delete "Consequently, the actual time remaining for resources to fully recover is usually less than 24 hours."
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.