A new release for Java Tron Odyssey-v3.5.0.1 was released 2 hours ago.
https://github.com/tronprotocol/java-tron/releases
Fixed an issue:
In a specific case, the CPU single core usage rate reached 90%, but had no effect on the overall performance.
Category Archives: blog
Java-tron node, new Odyssey-3.5 released
Yesterday (28.02.2019) a new release (v. 3.5) became available.
https://github.com/tronprotocol/java-tron/releases/
New features:
- Multiple signatures support and different permissions support in account
- The upper limit of energy can be adjusted automatically by the current state of the network
- Develop a new mechanism to listen event message from a queue
Changes:
- Solved the Compatibility Problem between Backup and DUP_WITNESS
- Optimize duplicate check of transaction, Increase processing speed
- Transfertoken function security improvement
- ADDRESS and ORIGIN instruction security improvements
- Improve the partial UNKNOWN execution results of the smart contract to a more detailed error type
- Log optimization improvements
- Http interface improvements
Important:
You will need to update the config.conf：
https://github.com/tronprotocol/tron-deployment/blob/master/main_net_config.conf
Please complete your upgrade to the new version before next Tuesday (March 05, 2019), otherwise it will affect the synchronization of the node !
Romania – 10 Nodes online
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:
TronLabs Romania has 10 Nodes Online on Tron MainNet on 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
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. 50+100 = 150 TRX
Transactions. This is the SUM of the amounts +50 -20 -10 +100 -10 -10 -10 = 90
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.
22nd of Jan 2019 – We have 8 nodes online
As of today we run 8 out of 9 Nodes present on the Romanian map.
22 January 2019
We run 8 nodes in Romania.
Dapps/Project funding
Good morning fellow Tron enthusiasts !
As you know we have some exciting projects that we are working on and these need money. Historically speaking now with almost 174K votes we earn too less (12 TRX/day as total vote rewards) to fund the Dapp fund, so I thought how I can accelerate this a bit.
Screenshot from Tronstation
Vote rewards 18.01.2019 (10:50 AM)
So how can we make the DAPP fund bigger ?
a) First contribution, of course, out of my own pocket.
The TronLabs Romania main SR account has 2000 Tron Power. This is because I’ve kept 2000 TRX frozen and have cast a vote for Cryptogirls till the end of year 2018. My first TRX that I ever received was 200 TRX (the bounty they promised) when I’ve attended their local meetup in Bucharest. When I later purchased my own in July, I’ve promised Irina that they will have 2000 Votes from me, till the end of the year. This promise I’ve kept till the 2nd of January 2019.
Since then, the same amount was used to vote for ourselves and according to what I’ve written above my plan is to pump this amount into the Dapp Fund as it’s first funding and to show that we are all in and need to lead by example. This is the HASH of the transfer. As details I’ve used “Project: TRLANY” (it can be used for any project).
b) though other contributions from fellow tron enthusiasts. If you wish to help, please donate into the Tron DAPP Development fund – TXgbWCjqoM7QKSntXW9t1d9eoA3j9JUhCG and remember to add the Project ID Code into the Transaction Details so we can differentiate what it is for. Please check each Project page for more details.
Update 25.05.2020
Today all the voting rewards that were accumulated by the SR Candidate until now (5636 TRX) will be claimed and sent to the Tron DAPP Development fund. Let’s face it, there were no donations made by anyone, in the last 18 month and the money did not multiply a lot. The 2000 TRX made 65 TRX 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 every cent.
6 Tron Nodes online
We have 6 Tron Main Network Nodes deployed online on 18.12.2018. Stay tuned for more.
Software Update to Odyssey-v3.2.2
We’ve updated yesterday to Odyssey-v3.2.2. This new release brings various Optimization of the Tron node software.
The most important for me are:
- that it provides the RPC and HTTP interface services of the SolidityNode on the FullNode.
- Asynchronous writing that significantly improves the performance of the FullNode and SolidityNode sync block.
For our dual nodes this greatly improve processing the block speed. We have also deployed one additional node in the network.
Quick Tron Nodes Sync
Version 2.0 – 04.03.2019
Hello fellow TRON enthusiasts. Dorian here with a new article about how to cheat a bit to speedup the tron sync time for your full nodes. As solodity functions are now provided by Full nodes the below guide has been updated. A full sync takes maybe close to a month for a Full node if you start from zero.
The good news are that the TRON foundation makes backups of the output directories every couple of hours publicly available [HERE].
The size has almost doubled in 5 month since the guide was first written.
You can follow Part 1 and Part 2 of our guide to compile the jar files that you need. Then as an intermediate step you will go to the backup directory and download the files.
The Guide has been updated as content and namic conventions have changed
Old Version naming
FullNode-latest-output-directory.tgz 24-Nov-2018 18:16 21G .. SolidityNode-latest-output-directory.tgz 24-Nov-2018 19:01 40G
New version naming
FullNode-7188305-3.2.4-output-directory.tgz 04-Mar-2019 04:12 93G .. FullNode-latest-output-directory.tgz 04-Mar-2019 10:13 93G
Instructions below:
You can use wget to get them, then untar, then move then into the proper folder (Ex. FullNode)
wget https://backups.trongrid.io/FullNode-latest-output-directory.tgz tar -xzvf FullNode-latest-output-directory.tgz mv output-directory FullNode
You can also do a chown just to make sure that the user has all needed rights on the files
sudo chown -R user:user /home/user/FullNode
Expected time for archive download and untar is around 30 Minutes – 2 hours (depends on your connection speed and peering).
Covered Scenarios:
1. You need to sync a single node.
Just download the archive, untar and start the node software.
2. You need to sync more than one node.
a) Download the archive on the first, untar and sync until it’s up to date.
b) Stop the Tron Java process and scp the entire directory to the other nodes.
c) edit/modify config files and start the java tron process. it will sync the delta’s since it was stopped.
TRON Disaster Recovery Orchestration
On the 27th of October 2018 I’ve held a product demo about Backing up a TRON Masternode at “Angajatori de Top”, one of the biggest job fairs in Romania. While announcing the event in the Tron Discord channel, I received requests for a presentation or white paper.
Today I’m happy to announce that the promised white paper is ready. You can get it as a PDF file from here:
TRON Disaster Recovery Orchestration whitepaper