Introduce delegating resource usage right

未关闭
#671 33 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
领域
blockchain

调研方向

The issue names no files, tests, or implementation entry points. Start by reading the resource delegation specification and locating the existing resource delegation transaction handling; done means the proposed delegating resource usage right transaction is supported with the described fallback consumption behavior.

由索引模型根据 Issue 内容生成。

描述

enhancement

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.

主要语言
没有语言数据
星标
341
派生
347
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

tronprotocol/tips 的其他 Issue

查看 tronprotocol/tips 的全部 Issue

相似的 Issue

更多 Blockchain Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。