Discussion: Adjust account permission update and multi-sign execution cost

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

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

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
説明が足りない
活発さ
活発
領域
blockchain

調査の方向性

Start by reviewing the discussion and feedback around getUpdateAccountPermissionFee and getMultiSignFee, including the stated security concerns and proposed values. The issue is complete only after the community reaches consensus on whether and how these multisign parameters should change; no implementation files or tests are identified.

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

説明

Summary

Since the Multi-sign feature was implemented on TRON (2019-03-21) no fees adjustments has been done to cope with increasing TRX price appreciation, I'd like to initiate a discussion on the matter and if approved by consensus adjust both:

getUpdateAccountPermissionFee from 100 TRX to 8 TRX
getMultiSignFee from 1 TRX to 0.1 TRX

(fees can be adjusted depending on discussion and feedback from community)

Motivation

Encourage TRON users to use the multi-sign feature to increase their accounts flexibility without compromising security.

Additionally, agentic commerce users might choose TRON over other blockchains if we provide their agents with cost effective solutions to enhance their EOA security, unlocked applications include the following:

  • Configure multi-sign threshold > 1 for high value / semi-automated wallet transactions flows
  • Limit agents automated actions to specific application like staking / delegation / vote
  • Prevent agents to execute non-desired operations like TRX transfer or Triggering Smart Contracts depending on use case.
Background

Considering initial dollar cost of multisign update was $2.2 USD (100 TRX * $0.022 USD = $2.2) and based on current TRX price now its $31 USD ( 100 TRX * $0.31 USD = $31 USD)

TRX growth factor = 14

I'd recommend to adjust multi-sign parameters so it is economically viable for users to enhance their TRON EOAs security.

TRON EOA Multi-sign feature is proven as an effective way to keep TRON accounts safe and flexible to use across different use cases like:

  • Institutional grade accounting security
  • TRON resources marketplaces (Delegation / Un-delegation / Vote automation)
  • Wallet as a Service
  • Large holders & Exchanges
  • Retail users willing to harden their accounts security

However, due to TRX price increases over time, the inherited cost of executing multisign transactions ($0.3 USD) as well as updating account permissions ($28.3 USD) is now considerably high, pushing users away from enhancing their accounts security and / or deterring their user experience while interacting with the TRON blockchain.

Analysis

While the current proposal improves user and dev experience there's also some potential security considerations we have to review.

Positive Impacts
  • Lower the economic barrier to strengthen TRON users accounts
  • Encourage users and developers to use multi-sign feature, enhancing security and security
Negative Impacts

Malicious actors can target unexperienced users to approve Ownership Account Permission , by reducing the cost the chances of users "blindly" signing a txn can increase.

Mitigations
  • Improve UI warning mechanisms on wallets like recently adopted by Tronlink and others.
  • Release education content amongst the community to increase awareness
  • Currently, most scammers automatically fund victim accounts with 100 TRX to execute an ownership permission attack, thus, reducing the fee most likely won't make a difference on it.

I thereby invite anyone to discuss on this matter. Thanks!

主要言語
言語のデータがありません
スター
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 を短くまとめたダイジェスト。