Tag Archives: TRX

[Release] Java Tron GreatVoyage-v4.5.2 (Aurelius)

Posted on by

Official link: https://github.com/tronprotocol/java-tron/releases/tag/GreatVoyage-v4.5.2

Important note: This is a Non-mandatory upgrade
New Features
Core
API
Changes

  • Improve node link stability #4542 #4540

  • Improve fault-tolerance capabilities of API parameters #4556 #4560

  • Optimize the eth_estimateGas
    and eth_call
    JSON-RPC API #4570

The universe is change; our life is what our thoughts make it.

—Aurelius

[Release] Java Tron GreatVoyage-v4.4.6 (David)

Posted on by

Official Github Link: https://github.com/tronprotocol/java-tron/releases/tag/GreatVoyage-v4.4.6

Note: This is a Non-mandatory upgrade

Changes

  • Upgrade fastjson version

Beauty in things exists in the mind which contemplates them.

— David Hume

[Release] Java Tron GreatVoyage-v4.4.3(Pythagoras)

Posted on by

Official Link: https://github.com/tronprotocol/java-tron/releases/tag/GreatVoyage-v4.4.3

This is a Non-mandatory upgrade

New Features

Changes

  • As an additional precaution, in addition to upgrading to logback version 1.2.9
  • we also recommend that users set their logback.xml configuration file to read-only

logback official news

http://logback.qos.ch/news.html

Silence is better than unmeaning words.
—Pythagoras

[Release] Java Tron GreatVoyage-v4.4.0 (Rousseau)

Posted on by

Java Tron GreatVoyage-v4.4.0 (Rousseau) has been released today.

Note: This is a forced update!

Link: https://github.com/tronprotocol/java-tron/releases/tag/GreatVoyage-v4.4.0

New Features

Core

  • TIP-289 Block broadcast logic optimization. #3986
  • TIP-290 Dynamic database query optimization. #3993
  • Transaction broadcast interface optimization. #4000
  • Database parameter optimization. #3992 #4018

TVM

  • TIP-272 Add a proposal to provide compatibility with Ethereum Virtual Machine. #4032
  • TIP-318 Add a proposal to be adapt to Ethereum London Release. #4032
  • The energy limit supports customization and the default value is increased in constant mode. #4032

API

  • Support ETH compatible JSON-RPC APIs excluding filter APIs. #4046
  • Support to disable specific APIs via the configuration file. #4045
  • Optimize the TriggerConstantContract API. #4032

Changes

  • Upgrade event plugin to support BTTC data. #4067
  • Increase the upper limit of the MaxFeeLimit network parameter. #4032
  • Optimize the quick deployment script start.sh see detail

 

The world of reality has its limits; the world of imagination is boundless.

— Rousseau

[Release] Java Tron GreatVoyage-v4.2.2 (Lucretius)

Posted on by

Today Java Tron GreatVoyage-v4.2.2 (Lucretius) was released by the Tron foundation.
Official Link: https://github.com/tronprotocol/java-tron/releases/tag/GreatVoyage-v4.2.2

Note: This is forced Upgrade !

New Features
Core
Changes

  • Optimize the initialization of the pre-complie contract BatchValidateSign
    #3836

TronLabs Romania DAPPS Fund Report

Posted on by

TronLabsRomania-DAPPS-Fund
TXgbWCjqoM7QKSntXW9t1d9eoA3j9JUhCG

Update 25.05.2020
Today all the voting rewards that were accumulated by the SR Candidate since we started and until now (5636 TRX) were claimed and sent to the Tron DAPP Development fund. The initial 2000 TRX generated 65 TRX from voting rewards in the same time frame of 18 months. The DAPP Funds needs more, as the projects need to be worked on, and I will have to pump in every cent.

Update 06.07.2020
Today all the voting rewards that were accumulated by the SR Candidate in the timeframe from 25.05.2020 – 07.07.2020 (160 TRX) were claimed and sent to the Tron DAPP Development fund. An additional 9 TRX were claimed as voting rewards and added on top. The fund balance has been increased by 169 TRX.

Update 18.07.2020
Today all the voting rewards that were accumulated by the SR Candidate in the timeframe from 07.07.2020 – 18.07.2020 (160 TRX) were claimed and sent to the Tron DAPP Development fund. An additional 37 TRX were added on top for a total of 197 TRX. In addition to this, the Dapp Fund account also claimed 9 TRX, it’s rewards for voting.
The total fund balance has been increased by 206 TRX.

Update 27.07.2020
Today all the voting rewards that were accumulated by the SR Candidate in the timeframe from 18.07.2020 – 27.07.2020 (160 TRX) were claimed and sent to the Tron DAPP Development fund. In addition to this, the Dapp Fund account also claimed 8 TRX, it’s rewards for voting.
The total fund balance has been increased by 168 TRX.

Update 06.08.2020
Today all the voting rewards that were accumulated by the SR Candidate in the timeframe from 27.07.2020 – 06.08.2020 (163 TRX) were claimed and sent to the Tron DAPP Development fund. In addition to this, the Dapp Fund account also claimed 8 TRX, it’s rewards for voting.
The total fund balance has been increased by 172 TRX.

Update 18.08.2020
Today all the voting rewards that were accumulated by the SR Candidate in the timeframe from 06.08.2020 – 18.08.2020 (207 TRX) were claimed and sent to the Tron DAPP Development fund. In addition to this, the Dapp Fund account also claimed 10 TRX, it’s rewards for voting.
The total fund balance has been increased by 217 TRX.

Update 11.09.2020
Today all the voting rewards that were accumulated by the SR Candidate in the timeframe from 18.08.2020 – 11.09.2020 (454 TRX) were claimed and sent to the Tron DAPP Development fund. In addition to this, the Dapp Fund account also claimed 29 TRX, it’s rewards for voting.
The total fund balance has been increased by 483 TRX.

Update 10.10.2020
Today all the voting rewards that were accumulated by the SR Candidate in the timeframe from 11.09.2020 – 10.10.2020 (740 TRX) were claimed and sent to the Tron DAPP Development fund. In addition to this, the Dapp Fund account also claimed 49 TRX, it’s rewards for voting.
The total fund balance has been increased by 790 TRX.

Update 19.11.2020
Today all the voting rewards that were accumulated by the SR Candidate in the timeframe from 10.10.2020 – 19.11.2020 (601 TRX) were claimed and sent to the Tron DAPP Development fund. In addition to this, the Dapp Fund account also claimed 51 TRX, it’s rewards for voting.
The total fund balance has been increased by 652 TRX.

Update 17.12.2020
Today all the voting rewards that were accumulated by the SR Candidate in the timeframe from 19.11.2020 – 17.12.2020 (327 TRX) were claimed and sent to the Tron DAPP Development fund. In addition to this, the Dapp Fund account also claimed 31 TRX, it’s rewards for voting.
The total fund balance has been increased by 359 TRX.

Update 29.05.2021
Today all the voting rewards that were accumulated by the SR Candidate in the timeframe from 17.12.2020 – 29.05.2021 (1595 TRX) were claimed and sent to the Tron DAPP Development fund. In addition to this, the Dapp Fund account also claimed 169 TRX, it’s rewards for voting.
The total fund balance has been increased by 1764 TRX.

Update 07.10.2021
Today all the voting rewards that were accumulated by the SR Candidate in the timeframe from 29.05.2021 – 07.10.2021 (1372 TRX) were claimed and sent to the Tron DAPP Development fund. In addition to this, the Dapp Fund account also claimed 163 TRX, it’s rewards for voting.
The total fund balance has been increased by 1535 TRX.

Update 02.11.2021
Today all the voting rewards that were accumulated by the SR Candidate in the timeframe from 07.10.2021-02.11.2021 (306 TRX) were claimed and sent to the Tron DAPP Development fund. In addition to this, the Dapp Fund account also claimed 39 TRX, it’s rewards for voting.
The total fund balance has been increased by 345 TRX.

Update 15.11.2021
Today all the voting rewards that were accumulated by the SR Candidate in the timeframe from 02.11.2021-15.11.2021 (142 TRX) were claimed and sent to the Tron DAPP Development fund. In addition to this, the Dapp Fund account also claimed 18 TRX, it’s rewards for voting.
The total fund balance has been increased by 160 TRX.

Update 17.01.2022
Today all the voting rewards that were accumulated by the SR Candidate in the timeframe from 15.11.2021-17.01.2022 (753 TRX) were claimed and sent to the Tron DAPP Development fund. In addition to this, the Dapp Fund account also claimed 98 TRX, it’s rewards for voting.
The total fund balance has been increased by 851 TRX.

Update 05.02.2022
Today all the voting rewards that were accumulated by the SR Candidate in the timeframe from 17.01.2022-05.02.2022 (280 TRX) were claimed and sent to the Tron DAPP Development fund. In addition to this, the Dapp Fund account also claimed 38 TRX, it’s rewards for voting.
The total fund balance has been increased by 318 TRX.

Update 15.03.2022
Today all the voting rewards that were accumulated by the SR Candidate in the timeframe from 05.02.2022-15.03.2022 (541 TRX) were claimed and sent to the Tron DAPP Development fund. In addition to this, the Dapp Fund account also claimed 76 TRX, it’s rewards for voting.
The total fund balance has been increased by 617 TRX.

Update 16.04.2022
Today all the voting rewards that were accumulated by the SR Candidate in the timeframe from 15.03.2022-16.04.2022 (353 TRX) were claimed and sent to the Tron DAPP Development fund. In addition to this, the Dapp Fund account also claimed 51 TRX, it’s rewards for voting.
The total fund balance has been increased by 404 TRX.

Update 02.05.2022
Today all the voting rewards that were accumulated by the SR Candidate in the timeframe from 16.04.2022-02.05.2022 (170 TRX) were claimed and sent to the Tron DAPP Development fund. In addition to this, the Dapp Fund account also claimed 25 TRX, it’s rewards for voting.
The total fund balance has been increased by 195 TRX.

Update 30.07.2022
Today all the voting rewards that were accumulated by the SR Candidate in the timeframe from 02.05.2022-30.07.2022 (766 TRX) were claimed and sent to the Tron DAPP Development fund. In addition to this, the Dapp Fund account also claimed 113 TRX, it’s rewards for voting.
The total fund balance has been increased by 880 TRX.

Update 22.08.2022
Today all the voting rewards that were accumulated by the SR Candidate in the timeframe from 30.07.2022-22.08.2022 (178 TRX) were claimed and sent to the Tron DAPP Development fund. In addition to this, the Dapp Fund account also claimed 27 TRX, it’s rewards for voting.
The total fund balance has been increased by 205 TRX.

[How-to] Convert Block level DB to ROCKS DB

Posted on by

This guide is intended for those who wish to convert from one DB format to another. The benefits are:
– You can use RocksDB as storage engine when you want to back up the database without the node application stopped,
– The Rocksdb engine has more tuning parameters for faster-synchronizing block and takes up less disk space when compared with the Block LevelDB.

Note:
You must only use one db engine (leveldb or rocksdb) throughout the life cycle of node because rocksdb’s data structure is incompatible with the leveldb’s. A convert tool is provided within Java-Tron to convert the leveldb data to rocksdb data and the usage of tool is described below. Please be aware that the conversion take time and the node is not syncing any blocks while this operation is ongoing.

1. First we need to clone the git and build it

git clone https://github.com/tronprotocol/java-tron
cd java-tron/
./gradlew build

Just wait until it’s built and tested. Go grab a cup of tee or a coffee.

2. Then we need to stop the node
3. Now we need to use this Java converter package (DBConvert.jar) to perform the conversion. It is located here: /java-tron/build/libs/

Sample syntax looks like this

java -jar build/libs/DBConvert.jar  your_database_dir/database  output-directory-dst/database

Example syntax looks like this

java -jar /home/userdir/java-tron/build/libs/DBConvert.jar /home/userdir/FullNode/output-directory/database /home/userdir/FullNode/output-directory2/database

According to tron documentation it should take about 10 hours to finish the conversion. Well on my node it took about 67800 seconds. This translates to 18.8 hours. The process is not CPU or Memory bound, both my CPU and Memory usage never exceeded 10% or the allocated resources.

Romania – 10 Nodes online

Posted on by

Hello fellow Tron enthusiasts,

We did it ! As of this morning we have 10 Tron nodes online who are part of the Tron Main Net. This does translate to about 1% of the network. I am very proud to have put “Romania” officially on the Tronscan Nodes ranking map. This shows that we as a community SR, are all in !

Here are the screenshots:

10 Nodes Online on Tron MainNet 2nd of Febr. 2019

TronLabs Romania has 10 Nodes Online on Tron MainNet on 2nd of Febr. 2019

Tron Nodes Ranking 2nd of Febr. 2019

Tronscan Node Ranking shows 11 Nodes online. From this total number, 10 are ours (TronLabs Romania) and one belongs to another tron enthusiast.

If you want to help out, check our projects page and vote for us.

Case Study – The Missing TRX

Posted on by

A Reddit user found a Dapp called FomoSports and played it. He then saw that he was missing 80 TRX, that could not be justified in any way.

This is his address: TBhLhTP4Mscgj5gpMxfe6u1zsWQ3DzEGMi

How he explained it with his own words:
a) The deal is open a Tronlink wallet to receive 50 TRX to play, and after betting let person know to get another 100TRX.
b) My friend lost the 30TRX of the 50TRX then received another 100TRX. Then he played another 10×3 (30TRX) should have 90TRX left.
c) However, my friend told me that he only have 10TRX left in his Tronlink.

It is shown in these 3 screenshots below.

Transfers

 Transfers. 50+100 = 150 TRX

 

Transactions

Transactions. This is the SUM of the amounts +50 -20 -10 +100 -10 -10 -10 = 90

 

final amount

Final amount in the Tronlink Wallet = 10 TRX

 

This is what happened:

This is because of the energy fees.  The conversion values are listed below.

1 SUN = 0.000001 TRX
1 TRX = 1,000,000 SUN

Let’s break it down and look at the contract triggers on TronGrid.

Transaction 1: SUCCESSFUL(-20TRX) with Fee 2.869300 TRX

"energy_fee": 2869300

Transaction 2: SUCCESSFUL(-10TRX) with Fee 3.581450 TRX

"energy_fee": 3581450

Transaction 3: TIMED OUT with Fee 100TRX

"energy_fee": 100000000

Transaction 4: OUT OF ENERGY with Fee 3.549250 TRX

"energy_fee": 3549250

Transaction 5: OUT OF ENERGY with Fee 0TRX (no funds left)

"result": "OUT_OF_ENERGY"

Let’s sum it all up:
20 + 2.8693 + 10 + 3.58145 + 100 + 3.54925 = 140TRX

+10TRX still left in account = 150TRX (all accounted for)

The loss is mainly due to the 3rd contract trigger where the out of time exception occurred and this causes all the input energy to be spent as seen above. This seems very unfair because the actual running of said contract didn’t actually use that much energy (judging by the origin_energy_usage it should’ve been more like 4TRX charged).

The timed out with 100 TRX Fee was unexpected. This seems like a way for TRON to punish people for trying to run smart contracts that take too long to execute. Either that or it’s a bug in java-tron. You as a end user have no control over the smart contract and how it executes as it’s running on the Nodes of the super representatives.