Proposal: Decrease getMultiSignFee fees

オープン
#938 コメント 15 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
blockchain
領域
blockchain

調査の方向性

Read the specification and impact analysis, focusing on parameter ID 23 (getMultiSignFee) and the proposed change from 1,000,000 to 500,000 sun. Review the cited on-chain data and related discussions in #850 and #915; this proposal is done when community consensus is reached and an authorized representative submits the on-chain parameter change.

索引モデルが issue の本文から書いたものです。

説明

Simple Summary

Since the Multi-sign feature was implemented on TRON (2019-03-21), no fee adjustment has been made to cope with TRX price appreciation.

This proposal's goal is to adjust the fee as follows:

  • getMultiSignFee: 1 TRX → 0.5 TRX

Expected impact: lowers the economic barrier to enabling and using multi-signature accounts, encouraging broader adoption of account security best practices (including agentic payments and wallet flows) while only modestly reducing TRX burn from this fee source.

Motivation

Since 2019, TRX price appreciation (~15x, from roughly $0.022 to ~$0.33) has pushed the real-dollar cost of this fee far above its original intent:

  • Executing a multi-signed transaction: ~$0.022 → ~$0.33 today

This pricing now discourages users and developers from adopting multi-sign, and compares unfavorably to security models on other chains (e.g., Bitcoin P2SH/Taproot multisig, Solana multisig, and EVM account abstraction), most of which carry little or no dedicated activation fee.

Multi-Sign lets users harden EOA security without sacrificing flexibility, supporting use cases such as institutional accounting controls, TRON resource marketplaces (delegation/un-delegation/vote automation), Wallet-as-a-Service providers, exchanges/large holders, and retail users.

This is also increasingly relevant to agentic commerce use cases: cost-effective multi-sig adds flexible, dynamic human authorization to agentic payment flows, replacing single-key trust with threshold-based approval.

Specification

This proposal aims to reduce the fee as follows:

  • parameter ID 23 (getMultiSignFee): From 1,000,000 sun (1 TRX) to 500,000 sun (0.5 TRX).

At ~$0.33/TRX, 0.5 TRX is roughly $0.165 per multi-signed transaction, half of today's ~$0.33.

A further decrease is not recommended due to current TRX burn ratio and Supply trends as discussed in https://github.com/tronprotocol/tips/issues/941

Timeline

Any opinions and discussions about this proposal are welcome before voting.

Suggested timeline:

Creation time of the voting request:
The effective time of voting request:

Final timeline to be confirmed

How to Initiate the Voting Request

To be submitted on-chain by a Super Representative, SR Partner, or SR Candidate once community consensus is reached, via a chain-parameter proposal setting:

getMultiSignFee -> 500,000 sun     (0.5 TRX)

(Values subject to the outcome of community discussion)

Background and Analysis

Background

Original vs. current cost basis

  • Multi-Sign (getMultiSignFee = 1 TRX) fees were fixed at feature launch (2019-03-21).
  • At current TRX price (~$0.33), the fee now costs ~$0.33, a ~15x real-cost increase with no corresponding change to the parameter.
Analysis
Methodology
Dataset scope and limitations
  • Spam filtering. Removed TRX spam txns to reduce data size: TransferContract < 0.0001 are excluded
  • Transaction result filtering. FAILED txns are not included in the current dataset. Implications: both the multisig surcharge burn and total burn omit payments from included failed transactions. The effect on their ratio depends on the relative amounts omitted and remains unaccounted in this analysis.
  • Contract types included in the Dataset for analysis. TriggerSmartContract , TransferContract, DelegateResourceContract, UnDelegateResourceContract, CreateSmartContract, TransferAssetContract, FreezeBalanceV2Contract, UnfreezeBalanceV2Contract
Dataset Labeling and terminology
  • Total burn. Total burn in the context of this dataset refers to TRX burn within the scope defined above.
  • Attributable Multisign burn. In the context of this dataset refers to multisig surcharge share of burn within the covered dataset
Data fetching procedure
  1. Fetch full block historical data trough a TRON firehose local pipeline and transformed into raw block files.
  2. Block data is sinked into a clickhouse DB for querying purposes using [substreams]((https://github.com/simbadMarino/estaTron).
  3. Dataset spreadsheet is created from query results

Executed query:

SELECT
  contract_type,
  count() AS txn_count,
  concat(
    toString(toYear(fromUnixTimestamp64Milli(block_timestamp, 'UTC'))),
    '-Q',
    toString(toQuarter(fromUnixTimestamp64Milli(block_timestamp, 'UTC')))
  ) AS quarter,
  sum(total_fee_burn / 1000000.0) AS burned_TRX,
  countIf(signature_count > 1) AS multisig_txns
FROM tron.transactions
GROUP BY contract_type, quarter
ORDER BY quarter, burned_TRX DESC

Resulting Spreadsheet:
Multisign.burn.Stats_v4_Q32026.xlsx

A series of on-chain historical data analyses were performed to better assess the impact of reducing the aforementioned parameter, focusing on the following:

  1. Transaction count fluctuation over time (user behavior)
  2. Deflationary impact
Image

(chart does not include Q2,Q3, can be updated if community feels its valuable)

Quarter Total Burn multisign
2024-Q1 1,028,722,746.45 268,379
2024-Q2 989,064,882.76 395,669
2024-Q3 1,046,203,547.15 468,319
2024-Q4 875,310,223.45 631,585
2025-Q1 654,024,245.57 1,103,384
2025-Q2 627,094,717.25 1,400,025
2025-Q3 481,228,637.88 1,439,657
2025-Q4 324,295,447.67 1,634,921
2026-Q1 273,984,626.11 1,629,461
2026-Q2 261,367,784.84 1,840,143
2026-Q3 227,033,943.68 1,591,100

Table: Multisign attributable burn accounts for a negligible share of total burned TRX (~0.59% in 2026-Q1 and ~0.70% in 2026-Q3), indicating a minimal impact on TRON inflation if the proposal is approved.

While multisign transactions show growth YoY (suggesting a significant fee reduction is not needed for this parameter), we must consider PQ migration (Path 1) account upgrade, which incentivizes multisign to be used for accounts that cannot follow path 2 and still need to follow Config 2 or Config 3 ( when NOT authorized by a single PQ signature) from the table below as well as agentic payment use cases. Because this fee cannot be covered by delegation (thus limiting gas abstraction patterns), we must be sensitive to the final fee number.

Note: Config 2 still incur in getMultiSignFee recurrent fees while Config 3 does only when ECDSA is used.

Configuration ECDSA-alone meets threshold? Safe?
Config 1 keys=[ECDSA w=1, PQ w=1], threshold=1 yes (either alone) No — same as today
Config 2 keys=[ECDSA w=1, PQ w=1], threshold=2 no (both required) Yes — both required
Config 3 keys=[ECDSA w=1, PQ w=2], threshold=2 no (ECDSA w=1 < 2) Yes — PQ alone still works
Config 4 keys=[PQ w=1], threshold=1 (ECDSA removed) n/a Yes — strongest

Table: PQ Account Permission Update Configuration examples

Impact analysis conclusion

  • Positive: lowers the barrier to Multi-Sign adoption, including Post Quantum future upgrades and broader agentic payment use cases, which may itself increase net TRX burn if usage grows.
  • Neutral: The TRX burn attributable to multisign is minimal, and reducing this fee does not constitute a higher inflation risk for TRON.
  • Security boundary: the fee is an anti-spam / burn mechanism, not the security boundary. The boundary is the multisig-threshold authorization, and the fee is deducted only after full signature/threshold validation, so lowering it does not weaken account security.
Post Activation Review

Placeholder section.

Note: This proposal was originally drafted as a single proposal in #915 and discussed in #850, now lives as a standalone tip.

主要言語
言語のデータがありません
スター
341
フォーク
347
PR マージ指標
30日以内にマージされた PR はありません

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

tronprotocol/tips のほかの issue

tronprotocol/tips の issue をすべて見る

似ている issue

Blockchain の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。