|Scope Type||Scope Name|
|web_application||1) economically-feasible way to DDoS the TRON network|
|web_application||2) disrupt the integrity of blockchain by sending malicious data to the network|
|web_application||3) slow down network performance by sending crafted API requests to network nodes. Unless approved by a TRON team member, no proof-of-concepts should be carried out directly on the mainnet. Hacking machines that host TRON nodes is not a valid form of attack on the blockchain. Local PoC and mainnet attack estimation should be enough information for most reports.|
Out of Scope
|Scope Type||Scope Name|
The Tron Bug Bounty Program is aimed at discovering potential technical vulnerabilities in the mainnet with the help of TRON’s community members, especially those who specialize in global network security, to sustain TRON mainnet as the most secure public blockchain in the industry and to provide secure and stable infrastructure and services to DApps deployed on the mainnet. We take the security of TRON mainnet very seriously. If you have made an important discovery of potential bugs, please contact us and join the TRON Bug Bounty Program as soon as possible and we will surely offer generous rewards!
April 10, 2019
(#2045)Refactor of sync & adv module, increase code readability and system scalability.
(#2028)RocksDB will be an option for the storage engine in the java-tron. The detail of the Rocksdb is described in this document. (https://github.com/tronprotocol/documentation/blob/master/TRX_CN/Tron-doc.md#471-rocksdb __)
You can use RocksDB as storage engine when you want to back up the database without the node application stopped, you can check the usage of Rocksdb engine in the document. It has more tuning parameters for faster-synchronizing block and takes up less disk space when compared with the LevelDB.
The database needs to be reset if the DB engine has been changed, but a tool can be used for converting Leveldb data to Rocksdb data, the instructions about this tool can be found here: https://github.com/tronprotocol/documentation/blob/master/TRX_CN/Tron-doc.md#4714-leveldb-database-convert-to-rocksdb-database-english-verison __
Add fast-forward feature and the miss rate of the block can be decreased by setting the forward node.
February 28, 2019
(#1873) Solved the Compatibility Problem between Backup and DUP_WITNESS
(#1907) Optimize duplicate check of transaction, Increase processing speed
(#1893) Transfertoken function security improvement
(#1893) ADDRESS and ORIGIN instruction security improvements
(#1929) Improve the partial UNKNOWN execution results of the smart contract to a more detailed error type
(#2009) remove txid in response of triggersmartcontract
(#1903) Multiple signatures support and different permissions support in accout
(#1905) Develop a new mechanism to listen event message from a queue
What it does : Java-tron is the main TRON protocol implementation and the only TRON network client capable of mining and verifying transactions through a 27-node dPoS (delegated proof-of-stake) mechanism. Vulnerabilities found from java-tron may impact the TRON blockchain network integrity, especially if valid against a Super Representative node - a node capable of producing blocks and collecting mining rewards.
What to look for: The best way to look for vulnerabilities is running a java-tron node locally and starting experimenting with the APIs it exposes. There are multiple guides on https://github.com/tronprotocol/java-tron __and https://developers.tron.network/docs __that can help with the initial setup and API usage. We value these types of issues (but not limited to) with high priority:
What it runs on: Anywhere an Oracle JVM (1.8) can run. However, we recommend an environment with at least 16 CPU cores for best results of syncing and communicating with the network.
Tron Foundation will make a best effort to meet the following SLAs for hackers participating in our program:
We’ll try to keep you informed about our progress throughout the process.
Please review our bounty table. Rewards are at the discretion of Tron, and we will not be awarding significant bounties for low severity bugs.
Please test the latest released versions of each project available. Hackers
should only look for bugs under the latest release version commit.
java-tron: https://github.com/tronprotocol/java-tron/releases __
You may use the source code of both projects to help you discover bugs.
Additionally, please use our documentation to assist you in your testing.
These following locations are considered out of scope for the bug bounty rewards. If you find issues with these projects, PLEASE file issues on the respective repositories if possible.
All rights of interpretation of the Bug Bounty are reserved to TRON. TRON Foundations decides whether to reward a bug disclosure and how much will be rewarded. Any individual or team participant should not violate any laws and regulations during testing.
Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.
Thank you for helping keep Tron Foundation and our users safe!