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.

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.

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.

Disaster Recovery Orchestration

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

Hello world!

Hello and welcome to our community site.

It’s July 2018, the Tron Main Net has launched a couple of weeks ago. I see  a chance to bring my own contribution. Stay tuned for some exciting news as I plan to go “all in”.

The Virtual Data Center deployment has the highest priority. I checked the posts of other SR candidates and try to scrap all info I can find. Resource usage for the nodes is not much now, that the network has just launched and there are no transactions, however it will grow in the future.

I had to take a decision as I am at a crossroad that will define the future, either rent resources in the cloud, as everyone does, or build my own and invest gradually as needed. My choice if in favor of the second. On the long run I will be able to build easier and scale as needed. Even if it’s not cheap, it will also allow me to learn new exciting stuff and keep my skills sharp.