TIPs

TRON Improvement Proposals (TIPs) describe standards for the TRON platform, including core protocol specifications, client APIs, and contract standards.

Contents

TIPs

TIPs Guide

ID	Title	Author	Type	Category	Hard fork	Status
TIP 10	TRON Token Standard	zhaohong229@gmail.com	Standards Track	Core	false	Final
TIP 12	TRON Event Subscription Model	jiangyangyang@tron.network	Informational	TRC	false	Final
TIP 13	Design of TRON account	justin@tron.network	Standards Track	Core	false	Final
TIP 16	TRON Account Multi-Signature	zhaohong229@gmail.com	Standards Track	Core	true	Final
TIP 17	TRON Adaptive Energy Limit Model	nanfengpo@hotmail.com	Standards Track	Core	true	Final
TIP 19	TRC-19 Deferred transaction	jiangyangyang@tron.network	Standards Track	Core	true	Deferred
TIP 20	TRC-20 Token Standard	zhaohong2292@gmail.com	Standards Track	TRC	true	Final
TIP 23	Add the account world status tree root to the block header	liangzhiyan@tron.network	Standards Track	Core	true	Accepted
TIP 24	Implement of DB storage with RocksDB	shydesky@gmail.com	Standards Track	Core	false	Final
TIP 26	Create2	jiangxinjian@tron.network	Standards Track	VM	false	Final
TIP 28	Built-in Message Queue in Event Subscription Model	jiangyangyang@tron.network	Informational		false	Final
TIP 29	Bitwise shifting instructions in Tron	jiangxinjian@tron.network	Standards Track	VM	true	Final
TIP 30	Code hash instructions	llwslc@gmail.com	Standards Track	VM	true	Final
TIP 31	Trigger constant contract	llwslc@gmail.com	Standards Track	VM	true	Final
TIP 32	Clear the ABI of contract	llwslc@gmail.com	Standards Track	VM	true	Final
TIP 37	Forbid using TransferContract & TransferAssetContract for contract account	taihao.fu@gmail.com	Standards Track	VM	true	Final
TIP 41	Optimize transactionHistoryStore occupancy space	wubin1@tron.network	Standards Track	Core	false	Final
TIP 43	Precompiled contract function for signature parallel verification	ksl2945@gmail.com	Standards Track	VM	true	Final
TIP 44	Address.isContract instructions	llwslc@gmail.com	Standards Track	VM	true	Final
TIP 51	Rate limit of API traffic	shydesky@gmail.com	Standards Track	Interface	false	Final
TIP 53	Optimize the current TRON delegation mechanism	liangzhiyan@tron.network	Standards Track	Core	true	Final
TIP 54	Automatically active non-existent account when transferring TRX/TRC10 asset in a smart contract	jiangxinjian@tron.network	Standards Track	VM	true	Final
TIP 60	Precompiled contract function for multi-signature verification	ksl2945@gmail.com	Standards Track	VM	true	Accepted
TIP 62	Tron consensus algorithm introduction	xing@tron.network	Standards Track	Core	false	Final
TIP 64	Tron tron mix consensus Analytics	xing@tron.network	Standards Track	Core	false	Draft
TIP 101	Wallet Keystore Specification	federico.zhen@tron.network	Standards Track	TRC	false	Last Call
TIP 102	Hierarchical Deterministic Wallet	federico.zhen@tron.network	Standards Track	TRC	false	Last Call
TIP 104	Data Signing Specification	federico.zhen@tron.network	Standards Track	TRC	false	Last Call
TIP 105	Multi-signature Permission Operation	federico.zhen@tron.network	Standards Track	TRC	true	Final
TIP 120	ECDSA Signature Encoding Specification	federico.zhen@tron.network	Standards Track	TRC	false	Final
TIP 127	Support Tron-DEX based on system contracts	liu.sean@tron.network	Standards Track	CORE	false	Draft
TIP 128	TIP128 Lite Fullnode support	ray.wu@tron.network	Standards Track	CORE	false	Draft
TIP 135	Shielded TRC-20 Contract	federico.zhen@tron.network	Standards Track	TRC	false	Final
TIP 137	Zero-knowledge Proof Verification functions	federico.zhen@tron.network	Standards Track	VM	true	Final
TIP 138	Pedersen hash function	federico.zhen@tron.network	Standards Track	VM	true	Final
TIP 156	Vote instructions in TVM	taihao.fu@gmail.com	Standards Track	VM	true	Withdrawn
TIP 157	Freeze instructions in TVM	taihao.fu@gmail.com	Standards Track	VM	true	Final
TIP 165	TRC-165 Standard Interface Detection In Contract	timothychungkitwai@gmail.com	Standards Track	TRC	true	Final
TIP 171	STAKE instructions in TVM	taihao.fu@gmail.com	Standards Track	VM	true	Withdrawn
TIP 174	CHAINID instructions in TVM	taihao.fu@gmail.com	Standards Track	VM	true	Final
TIP 175	SELFBALANCE instructions in TVM	taihao.fu@gmail.com	Standards Track	VM	true	Final
TIP 176	altbn128 operation energy reduction in TVM	taihao.fu@gmail.com	Standards Track	VM	true	Final
TIP 178	TOKENISSUE and UPDATEASSET Instruction in TVM	taihao.fu@gmail.com	Standards Track	VM	true	Withdrawn
TIP 191	Signed Data Standard	yanghang8612@163.com	Standards Track	TRC	false	Final
TIP 196	Reward SRs with the transaction fees charged for bandwidth and Energy	liu.sean@tron.network	Standards Track	Core	true	Final
TIP 204	Make MAX_FEE_LIMIT configurable as a chain property	yanghang8612@163.com	Standards Track	VM	false	Final
TIP 207	A proposal to improve network resources model	liu.sean@tron.network	Standards Track	Core	true	Draft
TIP 209	Adapt to Solidity 0.6.0	neo.hong@tron.network	Standards Track	VM	false	Final
TIP 222	Improve transaction execution speed	kiven.liang@tron.network	Standards Track	TRC	true	Final
TIP 250	Include transaction results on the chain	andy.zhang@tron.network	Standards Track	Core	true	Final
TIP 268	SmartContract ABI optimization	yanghang8612@163.com	Standards Track	VM	false	Final
TIP 269	Optimize the performance of block processing	forfreeday@163.com	Standards Track	Core	false	Final
TIP 271	Vote for SR in Smart Contract	yanghang8612@163.com	Standards Track	VM	true	Final
TIP 272	Compatible with EVM	yanghang8612@163.com	Standards Track	VM	true	Final
TIP 276	Optimize block verification logic	lucas.wu@tron.network	Standards Track	Core	false	Final
TIP 281	Optimize the query of database	forfreeday@163.com	Standards Track	Core	false	Final
TIP 285	Node startup optimization	lucas.wu@tron.network	Standards Track	Core	false	Final
TIP 289	Block Broadcast Optimization	lucas.wu@tron.network	Standards Track	Core	true	Final
TIP 290	Dynamic store optimization	lucas.wu@tron.network	Standards Track	Core	true	Final
TIP 292	Add a proposal to adjust the free net limit in an account	federico.zhen@tron.network	Standards Track	TRC	true	Final
TIP 293	Add a proposal to adjust the total net limit	federico.zhen@tron.network	Standards Track	TRC	true	Final
TIP 295	Optimize assets of account	forfreeday@163.com	Standards Track	Core	false	Final
TIP 298	Reformat manifest	halibobo1205@gmail.com	Standards Track	Core	false	Final
TIP 306	Adapt to solidity_0.8.4	neo.hong@tron.network	Standards Track	VM	false	Final
TIP 318	Adapt to Ethereum London Upgrade	neo.hong@tron.network	Standards Track	VM	false	Final
TIP 343	DB params optimization	halibobo1205@gmail.com	Standards Track	Core	false	Draft
TIP 344	Optimize instruction execution for TVM	yanghang8612@163.com	Standards Track	VM	false	Final
TIP 362	Optimized node broadcast data caching	forfreeday@163.com	Standards Track	Core	false	Final
TIP 366	Node startup optimization	halibobo1205@gmail.com	Standards Track	Core	false	Final
TIP 369	Node support prometheus metrics	halibobo1205@gmail.com	Standards Track	Core	false	Final
TIP 370	Node support conditionalized stop	halibobo1205@gmail.com	Standards Track	Core	false	Final
TIP 382	TIP-382: Optimize the data structure of account assets	wb_bupt@163.com	Standards Track	Core	false	Final
TIP 383	TIP-383: Optimize transaction cache loading	wb_bupt@163.com	Standards Track	Core	false	Final
TIP 387	TIP-387: Transaction memo fee	jell7@163.com	Standards Track	Core	false	Final
TIP 388	TIP-388: Optimize light node synchronization logic	wb_bupt@163.com	Standards Track	Core	false	Final
TIP 391	TIP-391: Optimize fetch block process	vikingzzu@163.com	Standards Track	Core	false	Final
TIP 397	Raise limit of the 13th network parameter	yanghang8612@163.com	Standards Track	VM	true	Final
TIP 425	TIP-425: Speed up TCP connection establishment	wb_bupt@163.com	Standards Track	Net	false	Final
TIP 428	TIP-428: Increase the probability that the block processing thread acquires the lock	wb_bupt@163.com	Standards Track	Core	false	Final
TIP 440	Transaction cache optimization	jell7@163.com	Standards Track	Core	false	Final
TIP 461	Optimize data consistency for system abnormals	ray.wu@tron.network	Standards Track	Core	false	Final
TIP 465	New reward calculation algorithm	bladehan@163.com	Standards Track	Core	true	Final
TIP 467	Stake 2.0 - A new TRON stake model	lxcmyf@gmail.com	Standards Track	Core	false	Final
TIP 474	Optimize the return value of chainid opcode	yanghang8612@163.com	Standards Track	VM	true	Final
TIP 476	Delegate Data Structure Optimization	lxcmyf@gmail.com	Standards Track	Core	false	Final
TIP 491	Dynamic Energy Model	daniel.cao@tron.network	Standards Track	VM	true	Final
TIP 712	TRON typed structured data hashing and signing	yanghang8612@163.com	Standards Track	Interface	false	Final
TIP 721	TRC-721 Non-Fungible Token Standard	timothychungkitwai@gmail.com	Standards Track	TRC	true	Final
TIP 1102	TIP-1102: Opt-in account exposure	aaronluotron@gmail.com	Standards Track	Interface	false	Final
TIP 1155	Multi Token Standard	yanghang8612@163.com	Standards Track	TRC	false	Final
TIP 1193	TIP-1193: TRON Provider JavaScript API	aaronluotron@gmail.com	Standards Track	Interface	false	Final
TIP 3326	TIP-3326: Wallet Switch TRON Chain Method	aaronluotron@gmail.com	Standards Track	Interface	false	Final
TIP 534	Remove Vulnerable APIs	halibobo1205@gmail.com	Standards Track	Core	false	Draft

To Submit a TIP

Before you submit a TIP, you need to create an issue for comment and add the issue URL to your TIP header.

1. Fork the repository by clicking "Fork" in the top right.

2. Add your TIP to your fork of the repository. There is a TIP template here.

3. Submit a Pull Request to TRON's TIPs repository.

Your first PR should be a first draft of the final TIP. It must meet the formatting criteria enforced by the build (largely, correct metadata in the header). An editor will manually review the first PR for a new TIP and assign it a number before merging it.

Make sure you include a discussions-to header with the URL to a discussion forum or open GitHub issue where people can discuss the TIP as a whole. If a TIP is about the feature development of java-tron, and a PR of the development exists, in your TIP and your java-tron's PR you need to refer each other's github link.

When you believe your TIP is mature and ready to progress past the draft phase, you should do one of two things:

For a Standards Track TIP of type Core, ask to have your issue added to the agenda of an upcoming All Core Devs meeting, where it can be discussed for inclusion in a future hard fork. If implementers agree to include it, the TIP editors will update the state of your TIP to 'Accepted'.
For all other TIPs, open a PR changing the state of your TIP to 'Final'. An editor will review your draft and ask if anyone objects to its being finalized. If the editor decides there is no rough consensus, they may close the PR and request you fix the issues in the draft before trying again.

TIP Status

TIPs are separated into several statuses.

Draft: A TIP that is undergoing rapid iteration and changes.
Last Call: A TIP that is done with its initial iteration and ready for review by a wide audience.
Accepted: A core TIP that has been in the Last Call for at least 2 weeks and any technical changes that were requested have been addressed by the author. The process for Core Devs to decide whether to encode a TIP into their clients as part of a hard fork is not part of the TIP process. If such a decision is made, the TIP will move to the final.
Final (non-Core): A TIP that has been in the Last Call for at least 2 weeks and any technical changes that were requested have been addressed by the author.
Final (Core): A TIP that the Core Devs have decided to implement and release in a future version or has already been released.
Active: If the TIPs are never meant to be completed, the TIPs may have a status of “Active”.
Abandoned: If a TIP is no longer pursued by the original authors or it may not be a (technically) preferred option anymore.
Rejected: A TIP that is fundamentally broken or a Core TIP that was rejected by the Core Devs and will not be implemented.
Superseded: A TIP which was previously Final but is no longer considered state-of-the-art. Another TIP will be in the Final status and cite the Superseded TIP.
Deferred: A TIP which isn't accepted now, it may be accepted in the future.

TIP Types

TIPs are separated into several types, and each has its list of TIPs.

Standard Track: Describes any change that affects most or all TRON implementations, such as a change in block or transaction validity rules, proposed application standards/conventions, or any change or addition that affects the interoperability of applications using TRON. Furthermore, Standard TIPs can be broken down into the following categories.

1.Core: Improvements requiring a consensus fork, as well as changes that are not necessarily consensus critical but may be relevant to "core dev" discussions.

2.Networking: Includes improvements around network protocol.

3.Interface: Includes improvements around client API/RPC specifications and standards.

4.TRC: Application-level standards and conventions, including contract standards such as token standards (TRC-20).

5.VM: Includes improvements around TRON Virtual Machine.
Informational: Describes a TRON design issue, or provides general guidelines or information to the TRON community, but does not propose a new feature.

For further discussion, please enter Telegram

hanijon1/tips

ErrorLooks like something went wrong!

About

Resources

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Error
Looks like something went wrong!

Packages