Bucharest Blockchain and DPoS is safe !

A few days ago I received the following message via e-mail from the Meetup Site.

save_meetup

Save Bucharest Blockchain and DPoS

The Meetup group that I’ve attended and got inspired to run for TRON SR was going to disappear in a couple of days, if no one would step up and save it.
Knowing that it might be an issue with the payment or just some glitch, I told myself to be patient and wait for a couple of days. I’ve waited until the 2nd of March at 10 PM. No renewal and no one else stepped up so I had to act.

Now our Meetup group is safe. I plan to continue what Crypto Girls have started and help our community to succeed. I plan for both in person meetings as well as for virtual ones.

Stay tuned for more.. good things are coming our way.

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 !

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 18012019

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 fundTXgbWCjqoM7QKSntXW9t1d9eoA3j9JUhCG 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.

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.