Proposal: Decrease getUpdateAccountPermissionFee fees

Open
#915 16 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
blockchain
Domain
blockchain

Research direction

Start with the Specification and the referenced TRON chain-parameter proposal process, then review the linked java-tron#6793 PQ migration issue for related context. Done means community consensus on the final values and an on-chain proposal submitted by an eligible Super Representative, partner, or candidate; no implementation files are named.

Written by the indexing model from the issue text.

Description

Simple Summary

Since the Account Permission Update inception (main-net launch) no fees adjustments has been done to cope with increasing TRX price appreciation for getUpdateAccountPermissionFee parameter

This proposal goal is to adjust fees as follows:

  • getUpdateAccountPermissionFee: 100 TRX → 8 TRX

Expected impact: lowers the economic barrier to harden account security, 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 their original intent:

  • Updating account permissions: ~$2.20 → ~$33 today

This pricing now discourages users and developers from enhancing their accounts security, 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.

Account permissions let 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.

Post-quantum migration is a further, higher-stakes motivating case. The recommended in-place PQ migration path (java-tron#6793) adds a PQ key via AccountPermissionUpdateContract. This makes UpdateAccountPermissionFee the one-time, per-account cost of becoming quantum-resistant . A ~$33 gate on the single action that makes an existing account quantum-safe works against TRON PQ roadmap.

Specification

This proposal aims to reduce both parameter fees as follows:

  • parameter ID 22 (getUpdateAccountPermissionFee): From 100,000,000 sun (100 TRX) to 8,000,000 sun (8 TRX).

Timeline

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

Suggested timeline:

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

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:

getUpdateAccountPermissionFee -> 8,000,000 sun   (8 TRX)

(Values subject to the outcome of community discussion)

Background and Analysis

Background

Original vs. current cost basis

  • getUpdateAccountPermissionFee = 100 TRX (~$2.20 at ~$0.022/TRX) was fixed since mainnet launch
  • At current TRX price (~$0.33), the same fee in TRX is ~$33 , a ~15x real-cost increase with no corresponding change to the parameters.
Analysis

On-chain Data Indexing limitations and considerations:

  • Removed TRX spam txns to reduce data size: TransferContract < 0.0001 are excluded
  • FAILED txns are not accounted ( this is a substreams foundational package design limitation).

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

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

Chart: AccountPermissionUpdate (contract_type: 46) volume & burn plateaued around Q3 2023 with an average of 15.4k transactions and 1.54M TRX burned per quarter (Q1 2025 being a notable exception) signaling a capped utilization rate (potentially derived from a perceived high cost for retail users)

Image
Quarter Total Burn accountPermissionUpdate
2024-Q1 1,028,722,746.45 2,602,970.28
2024-Q2 989,064,882.76 1,499,173.17
2024-Q3 1,046,203,547.15 1,523,267.76
2024-Q4 875,310,223.45 1,560,276.59
2025-Q1 654,024,245.57 1,246,547.25
2025-Q2 627,094,717.25 1,435,063.54
2025-Q3 481,228,637.88 1,404,538.69
2025-Q4 324,295,447.67 1,438,281.60
2026-Q1 273,984,626.11 1,283,522.08

Table: AccountPermissionUpdate attributable burn accounts for a negligible share of total burned TRX (~0.47% in 2026-Q1; 0.25% on average, 2024-Q1 to 2026-Q1), indicating a minimal impact on TRON inflation if the proposal is approved.

Impact analysis conclusion

  • Positive: lowers the barrier to account hardening, including Post Quantum future upgrades, and encourages broader agentic payment use cases, which may itself increase net TRX burn if usage grows.

  • Neutral: The TRX burn attributable to AccountPermissionUpdate is minimal, and reducing this fee does not constitute a higher inflation risk for TRON.

  • Negative: a cheaper UpdateAccountPermissionFee could marginally ease "blind-signing" ownership-permission attacks against inexperienced users.

  • Mitigations discussed: wallet-level UI warnings (e.g., already adopted by TronLink), community security-education content. It was also noted that most ownership-permission scams pre-fund victim accounts with 100 TRX, so this specific fee change is unlikely to materially change attacker economics.

  • Security boundary: the fee is an anti-spam / burn mechanism, not the security boundary. The boundary is the owner-key / multisig-threshold authorization required to sign the update itself, so lowering the fee does not make it easier to alter permissions on an account the attacker does not control.

Edit (Oct 5th 2026): This proposal tip was adjusted to cover getUpdateAccountPermissionFee parameter only.

Dominant language
No language data
Stars
341
Forks
347
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tronprotocol/tips

All issues in tronprotocol/tips

Similar issues

More Blockchain issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.