Discussion: TIP-796 — Dual-Word + 4-Digit Username System for TRON Accounts

[alichatme]

This Issue opens the community discussion for TIP-796: Dual-Word + 4-Digit Username System for TRON Accounts.

Summary

TIP-796 proposes a decentralized, human-readable username format for TRON accounts consisting of two meaningful English words plus a 4-digit suffix (e.g., moonriver4821).

Key Benefits

• Reduces copy/paste mistakes and malware-induced address swaps
• Fully decentralized and non-transferable usernames
• Massive scalability (≈3.6 quadrillion combinations using 650,000 words)
• Enhances user confidence and transaction safety

Author

ali&chatgpt (GitHub: @alichatme)

---

Related PR: #1

Please share your feedback and suggestions below to help improve this proposal.

[alichatme]

Hello @Federico2014 @winni1115 @vivian1912 👋

Thank you for taking a moment to review TIP-796. I created this discussion issue to collect community feedback and improve the proposal.

Short summary:

• TIP-796 proposes a decentralized, human-readable username format for TRON accounts: two meaningful English words + a 4-digit suffix (e.g., moonriver4821).
• Non-transferable by design to preserve decentralization.
• Wallets should display both the username and the full destination address in the confirmation modal to prevent clipboard tampering or address-replacement malware.

PR link: alichatme#1

Author / Team: ali&chatgpt (@alichatme)

Could you please advise on the preferred review flow or any immediate concerns? Any guidance or pointers to community channels (if preferred) would be appreciated.

Thanks a lot for your time and help!

[laurenceja]

@alichatme TRON accounts can set account name freely, without strict rules. Do we really need to make it so restrictive?

[vivian1912]

Related issue of #797 . So to better understand the motivation and context of this feature, it might be better to continue the discussion under #797 .

[alichatme]

Thank you for your feedback 🙏 The goal of this proposal is *not to restrict* account naming freedom, but to *introduce an optional, standardized, and verifiable username format* that improves user safety. Today, TRON accounts can set any name freely — but that flexibility also allows *impersonation or misleading names*. With this system, wallets can display both the username and the full address before signing, helping users confirm they’re sending to the correct account. So the proposal doesn’t change the protocol logic — it simply *adds a reliable naming layer to prevent address-based fraud.* در تاریخ جمعه ۱۰ اکتبر ۲۰۲۵، ۱۲:۵۵ laurenceja ***@***.***> نوشت:

…

*laurenceja* left a comment (tronprotocol/tips#799) <#799 (comment)> @alichatme <https://github.com/alichatme> TRON accounts can set account name freely, without strict rules. Do we really need to make it so restrictive? — Reply to this email directly, view it on GitHub <#799 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BX4PW3BKY7NVBVLTJOYP2XD3W53PZAVCNFSM6AAAAACIY6F5LSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGOBZGA2DSMZXG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[lxcmyf]

@alichatme
Can the naming be repeated under the naming standard you provided? Is there a repetitive check?

[alichatme]

Thank you @lxcmyf for raising this point In this proposal, usernames are not created manually or through smart contracts. Instead, all ~3.6 quadrillion possible names are pre-generated and distributed randomly across accounts. That means: Each assigned username is unique, because once it’s used, it’s removed from the available pool. There’s no need for smart contract logic or fees, keeping the system lightweight and decentralized. Random assignment ensures fairness and prevents duplication or manipulation. When a user confirms a transaction, seeing the destination’s unique username (e.g. boymen4565) provides strong reassurance that the address is correct — boosting both user trust and TRON’s overall security model. در تاریخ جمعه ۱۰ اکتبر ۲۰۲۵، ۱۳:۳۱ lxcmyf ***@***.***> نوشت:

…

*lxcmyf* left a comment (tronprotocol/tips#799) <#799 (comment)> @alichatme <https://github.com/alichatme> Can the naming be repeated under the naming standard you provided? Is there a repetitive check? — Reply to this email directly, view it on GitHub <#799 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BX4PW3B35MJVZMDRAGUPGKL3W57ZHAVCNFSM6AAAAACIY6F5LSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGOBZGE3DEMRQGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[alichatme]

Thank you @laurenceja for your thoughtful follow-up You’re absolutely right — TRON already allows free naming. This proposal does not aim to replace or restrict that flexibility. Instead, it introduces an optional, standardized, and verifiable username format that can coexist with the current free naming system. The goal is to improve transaction safety by helping users visually confirm the correct recipient before signing — reducing address mix-ups or phishing-style fraud. So, freedom stays intact, but with an added layer of trust that benefits both users and the TRON ecosystem. در تاریخ جمعه ۱۰ اکتبر ۲۰۲۵، ۱۴:۲۲ ali aram ***@***.***> نوشت:

…

Thank you @lxcmyf for raising this point In this proposal, usernames are not created manually or through smart contracts. Instead, all ~3.6 quadrillion possible names are pre-generated and distributed randomly across accounts. That means: Each assigned username is unique, because once it’s used, it’s removed from the available pool. There’s no need for smart contract logic or fees, keeping the system lightweight and decentralized. Random assignment ensures fairness and prevents duplication or manipulation. When a user confirms a transaction, seeing the destination’s unique username (e.g. boymen4565) provides strong reassurance that the address is correct — boosting both user trust and TRON’s overall security model. در تاریخ جمعه ۱۰ اکتبر ۲۰۲۵، ۱۳:۳۱ lxcmyf ***@***.***> نوشت: > *lxcmyf* left a comment (tronprotocol/tips#799) > <#799 (comment)> > > @alichatme <https://github.com/alichatme> > Can the naming be repeated under the naming standard you provided? Is > there a repetitive check? > > — > Reply to this email directly, view it on GitHub > <#799 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BX4PW3B35MJVZMDRAGUPGKL3W57ZHAVCNFSM6AAAAACIY6F5LSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGOBZGE3DEMRQGU> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

[halibobo1205]

Are there similar solutions (such as Name Service) on other chains?

[alichatme]

Thank you for the great question Yes, several blockchains — such as Ethereum (ENS), Solana (SNS), and BNB Chain — have introduced name services with similar goals. However, our proposal is fundamentally different in both **design and purpose**. Most existing systems are **smart contract–based** and operate as **layer-two solutions**, meaning: - Names are registered and managed through a contract, not the native account layer. - Each operation (register, renew, or transfer) requires a **gas fee**. - Ownership of the name is stored within the contract, not within the blockchain’s core account system. In contrast, our proposal integrates the naming system **directly into TRON’s native account layer**, not as a smart contract or an external protocol. That means: - **No gas fee** for assigning or using a name. - **No central contract** controlling registration. - **No duplicate names**, as they are generated and linked algorithmically. - **Complete decentralization**, since the network itself handles name allocation. - And, most importantly, **enhanced user safety** — users can confirm a receiver’s identity right inside the wallet before signing a transaction. Beyond the technical aspect, this proposal also addresses one of the biggest barriers to blockchain adoption — **trust and usability**. People **simply cannot remember or manually type** long, unreadable wallet addresses. This complexity has been one of the main causes of user errors and fraud, such as address replacement malware. With this system, wallets can display the verified username tied to each address, so users can instantly confirm they’re sending funds to the right person. TRON, with over **400 million active accounts**, is in the perfect position to lead this change — bringing simplicity, safety, and human-centered design to decentralized systems, without compromising their core principles. **In short:** While other chains rely on smart contracts and layer-two services, TRON can deliver a **native, gas-free, and fully decentralized** naming system — turning complex blockchain addresses into something every user can trust and understand. در تاریخ دوشنبه ۱۳ اکتبر ۲۰۲۵، ۶:۳۷ halibobo1205 ***@***.***> نوشت:

…

*halibobo1205* left a comment (tronprotocol/tips#799) <#799 (comment)> Are there similar solutions (such as Name Service) on other chains? — Reply to this email directly, view it on GitHub <#799 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BX4PW3DJQGFWKKSTNGB2SXD3XMJOTAVCNFSM6AAAAACIY6F5LSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGOJVG4YTCNZSHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[GrothenDI]

@alichatme Hello, could you please briefly explain how these usernames are generated and how they are matched and bound to addresses?

[alichatme]

Thank you for your time and for asking such a great question. In the English language, there are approximately one million meaningful words. We use around 650,000 meaningful words after filtering out inappropriate or overly technical terms. Each username is generated by combining two random words and four random digits. Here’s the calculation for the total possible combinations: - First word: 650,000 options - Second word: 650,000 options - Four-digit number: 10,000 options (from 0000 to 9999) Therefore: 650,000 × 650,000 × 10,000 = 4,225,000,000,000,000 ≈ about 4.2 quadrillion unique usernames. Even after filtering, this number is extremely large, providing a secure and vast namespace for simple, human-readable, and decentralized usernames. Whenever a new account is created or activated on the TRON network, the system — according to the TRON development team’s configuration — randomly assigns one of the available names from the repository to that account. To prevent duplication, the assigned name is then removed from the available pool. Once a name has been assigned to an account, it remains permanently bound to that address and cannot be changed. This process does not require any smart contracts or secondary layers — it operates entirely at the **Account Layer**, ensuring that the core structure and protocols of the TRON network remain completely unchanged. As a result: - All usernames are unique and non-repetitive. - The assignment process is decentralized and trustless. - Users can visually confirm transaction destinations, effectively eliminating the risk of errors or phishing attacks. در تاریخ چهارشنبه ۱۵ اکتبر ۲۰۲۵، ۹:۰۶ GrothenDI ***@***.***> نوشت:

…

*GrothenDI* left a comment (tronprotocol/tips#799) <#799 (comment)> @alichatme <https://github.com/alichatme> Hello, could you please briefly explain how these usernames are generated and how they are matched and bound to addresses? — Reply to this email directly, view it on GitHub <#799 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BX4PW3ELDHQBWKXUJOIB6ZT3XXMNTAVCNFSM6AAAAACIY6F5LSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIMBUGU4TENZUGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[GrothenDI]

Thank you for your time and for asking such a great question.

In the English language, there are approximately one million meaningful
words.
We use around 650,000 meaningful words after filtering out inappropriate or
overly technical terms.
Each username is generated by combining two random words and four random
digits.

Here’s the calculation for the total possible combinations:

• First word: 650,000 options
• Second word: 650,000 options
• Four-digit number: 10,000 options (from 0000 to 9999)

Therefore:
650,000 × 650,000 × 10,000 = 4,225,000,000,000,000 ≈ about 4.2 quadrillion
unique usernames.

Even after filtering, this number is extremely large, providing a secure
and vast namespace for simple, human-readable, and decentralized usernames.

Whenever a new account is created or activated on the TRON network, the
system — according to the TRON development team’s configuration — randomly
assigns one of the available names from the repository to that account.
To prevent duplication, the assigned name is then removed from the
available pool.

Once a name has been assigned to an account, it remains permanently bound
to that address and cannot be changed.
This process does not require any smart contracts or secondary layers — it
operates entirely at the Account Layer, ensuring that the core
structure and protocols of the TRON network remain completely unchanged.

As a result:

• All usernames are unique and non-repetitive.
• The assignment process is decentralized and trustless.
• Users can visually confirm transaction destinations, effectively
  eliminating the risk of errors or phishing attacks.

در تاریخ چهارشنبه ۱۵ اکتبر ۲۰۲۵، ۹:۰۶ GrothenDI @.***>
نوشت:
…

What about the large number of addresses that already exist?

[alichatme]

Thank you very much for your insightful comment and excellent question. Yes, the allocation of usernames to existing TRON accounts can be done gradually or all at once, depending on the TRON development team’s implementation strategy. Wallets will also need to be updated so that each user can view and copy their assigned username alongside their account address. Importantly, since usernames do not affect TRON’s transaction validation protocols, accounts and wallets that have not yet been updated will continue to function normally until full integration is complete. Once all accounts have received their usernames and wallet updates are deployed, transactions will include a visual verification step: when a sender enters the destination address, the wallet will automatically display the corresponding username before final confirmation. This allows users to verify the destination account visually, effectively preventing transfer mistakes — one of the most common user concerns in crypto transactions. This approach strengthens trust, security, and usability across the TRON ecosystem without modifying the core protocol. در تاریخ چهارشنبه ۱۵ اکتبر ۲۰۲۵، ۱۰:۵۰ GrothenDI ***@***.***> نوشت:

…

*GrothenDI* left a comment (tronprotocol/tips#799) <#799 (comment)> Thank you for your time and for asking such a great question. In the English language, there are approximately one million meaningful words. We use around 650,000 meaningful words after filtering out inappropriate or overly technical terms. Each username is generated by combining two random words and four random digits. Here’s the calculation for the total possible combinations: - First word: 650,000 options - Second word: 650,000 options - Four-digit number: 10,000 options (from 0000 to 9999) Therefore: 650,000 × 650,000 × 10,000 = 4,225,000,000,000,000 ≈ about 4.2 quadrillion unique usernames. Even after filtering, this number is extremely large, providing a secure and vast namespace for simple, human-readable, and decentralized usernames. Whenever a new account is created or activated on the TRON network, the system — according to the TRON development team’s configuration — randomly assigns one of the available names from the repository to that account. To prevent duplication, the assigned name is then removed from the available pool. Once a name has been assigned to an account, it remains permanently bound to that address and cannot be changed. This process does not require any smart contracts or secondary layers — it operates entirely at the *Account Layer*, ensuring that the core structure and protocols of the TRON network remain completely unchanged. As a result: - All usernames are unique and non-repetitive. - The assignment process is decentralized and trustless. - Users can visually confirm transaction destinations, effectively eliminating the risk of errors or phishing attacks. در تاریخ چهارشنبه ۱۵ اکتبر ۲۰۲۵، ۹:۰۶ GrothenDI *@*.***> نوشت: … <#m_2055877865347725824_> What about the large number of addresses that already exist? — Reply to this email directly, view it on GitHub <#799 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BX4PW3ELS24AIWT2M5SDXQ33XXYUTAVCNFSM6AAAAACIY6F5LSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIMBUHEZTMNZZGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Jamq513]

This Issue opens the community discussion for TIP-796: Dual-Word + 4-Digit Username System for TRON Accounts.

Summary

TIP-796 proposes a decentralized, human-readable username format for TRON accounts consisting of two meaningful English words plus a 4-digit suffix (e.g., moonriver4821).

Key Benefits

• Reduces copy/paste mistakes and malware-induced address swaps
• Fully decentralized and non-transferable usernames
• Massive scalability (≈3.6 quadrillion combinations using 650,000 words)
• Enhances user confidence and transaction safety

Author

ali&chatgpt (GitHub: @alichatme)

Related PR: #1

Please share your feedback and suggestions below to help improve this proposal.