Track and Introduce ERC-6909 Minimal Multi-Token Interface to TRON
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- solidity
- Domain
- blockchain
Research direction
Start by comparing ERC-6909 with TIP-165, TIP-1155, and TIP-20 using the linked references. Define a TRC-6909 proposal covering the minimal interface, TIP-165 detection, optional extensions, and TRON-specific wallet, address, Energy/Bandwidth, and indexing guidance. Done means the proposal resolves the listed compatibility topics and documents the reference implementation requirements.
Written by the indexing model from the issue text.
Description
Background
ERC-6909 defines a minimal multi-token interface for managing multiple token IDs in a single smart contract. It is positioned as a simpler alternative to ERC-1155: it removes required receiver callbacks and batching from the core interface, while keeping a hybrid permission model with per-token allowances and all-token operator approvals.
TRON already supports token standards such as TIP-20 and TIP-1155. However, projects that need multiple fungible-like token IDs inside one contract may not always need the heavier TRC-1155 receiver and batch-transfer model. A minimal TRC-6909 interface would provide a small, EVM-compatible, Solidity-friendly contract standard for reward points, protocol accounting balances, gaming currencies, vault shares, coupons, credits, and other multi-token use cases on TRON.
The goal is to track ERC-6909 and introduce it to TRON as a TIP, proposed as TRC-6909, while preserving compatibility with TRON's TVM, TIP-165 interface detection, address representation, wallets, explorers, and indexers.
Scope
- Define a TRC-6909 minimal multi-token interface for TVM smart contracts.
- Keep function names, event names, argument order, and ABI types aligned with ERC-6909 as closely as possible.
- Require TIP-165 support so contracts can expose the TRC-6909 interface ID.
- Preserve ERC-6909-style per-token allowances and full-operator approvals.
- Include optional metadata, content URI, and token supply extensions for projects that need them.
- Provide TRON-specific guidance only where TVM, address display, Energy/Bandwidth, wallets, explorers, or indexers require clarification.
Compatibility Topics for Discussion
- Positioning with TRC-20 and TRC-1155. TRC-6909 should not replace TRC-20 or TRC-1155. It should be recommended when a project wants multiple fungible-like token IDs in one contract without required safe receiver callbacks or required batch methods.
- TIP-165 interface detection. Because the core function selectors are intended to match ERC-6909, the proposed base interface ID is 0x0f632fb3. - TRON address handling. Solidity ABI addresses are 20-byte values, while wallets and users commonly display TRON Base58 Check addresses. Tooling should display user-friendly TRON addresses but preserve ABI-level compatibility for signatures, logs, and contract calls.
- Wallet and explorer display. TronLink, Tronscan, TronGrid, and indexers would need to recognize balances by (contract, owner, token id), not only by contract address. Transfer, Approval, and OperatorSet events should be indexed with token id awareness.
- Operator approval risk. setOperator grants unlimited transfer permission across all token IDs owned by the caller. Wallets should clearly warn users that this is stronger than approving one token ID.
- Removal of required callbacks. TRC-6909 intentionally does not require receiver callbacks. This reduces interface complexity and avoids mandatory external calls, but it also means tokens can be transferred to contracts that do not know how to handle them. This should be documented clearly.
- Batching. Batch transfers are intentionally outside the minimal core interface. Projects may add implementation-specific batch methods, but they should preserve balance/event consistency.
- Energy/Bandwidth impact. The minimal interface may reduce contract code size and transfer-path complexity compared with TRC-1155 for use cases that do not need callbacks or required batching. Actual Energy usage should be measured in a reference implementation.
- Metadata. name(id), symbol(id), decimals(id), contractURI(), tokenURI(id), and totalSupply(id) should remain optional extensions so the core remains minimal.
- Existing contracts. Already-deployed contracts cannot become TRC-6909 unless they were designed to be upgraded. Adoption is expected for new contracts or upgradeable systems.
References
- 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tronprotocol/tips
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
tronprotocol/tips#950 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
tronprotocol/tips#945 · 8 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
tronprotocol/tips#944 · 6 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
tronprotocol/tips#941 · 5 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
tronprotocol/tips#938 · 15 comments ·
All issues in tronprotocol/tips
Similar issues
-
bug Medium security smart-contract Stellar Wave validation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Web3Novalabs/Nevo#1749 · 2 comments ·
Maintainers usually reply within 1 day
-
contract good first issue testing
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Emmyt24/nova-launch#2436 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
status-im/nimbus-eth1#5181 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
erigontech/erigon#26523 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
lambdaclass/ethrex#7550 ·
Maintainers usually reply within 2 days