Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce delegating resource usage right #671

Open
LuganBI opened this issue Aug 29, 2024 · 3 comments
Open

Introduce delegating resource usage right #671

LuganBI opened this issue Aug 29, 2024 · 3 comments

Comments

@LuganBI
Copy link

LuganBI commented Aug 29, 2024

Simple Summary

The resource usage right can be delegated.

Motivation

After Stake 2.0 is enabled, the resource delegations have been much more flexible on the TRON network. The volume of resource delegation and revoking resource delegation transactions has increased significantly. Especially in the case of asset aggregation of an account, it needs to repeatedly delegate resources to other addresses and then undelegate after the transfer transactions are done, which makes large amounts of transactions happen and the operations could be very cumbersome. In order to alleviate this situation, it is proposed to introduce a new transaction type to reduce the number of such large and frequent resource delegation and revoking resource delegation transactions.

After introducing the transaction type of delegating resource usage right, when an account has to regularly initiate large amounts of resource delegation transactions to help other addresses execute transactions, it only needs to delegate the resource usage right to every target address once and for all. It will greatly reduce the complexity of the operations.

Specifications

Adding a transaction type of resources usage right delegation, it allows account A to delegate X shares of specific resources to account B. After the transaction is completed, the X shares of resources are still in account A, and when account B needs to consume the specific type of resources, resources less than X share will be consumed directly from account A first. When the resources to be consumed are greater than X share or account A has insufficient resources, account B's own resources will then be consumed.

@GuipaiQigong111
Copy link

GuipaiQigong111 commented Aug 30, 2024

I am not sure about the specific functional division between it and the resource delegating, but I always feel that this move carries too much risk. Without the constraints of relevant rules, it may be abused, which will be detrimental to the healthy development of the Tron network.

@CarlChaoCarl
Copy link

CarlChaoCarl commented Aug 30, 2024

The implementation involves more details, such as how to be compatible with existing logic, and it may also bring the risk of abuse.

@toolsopen
Copy link

I prefer to use multiple addresses to sign transactions at the same time and specify one of the addresses as the resource payment address.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants