Trinity Protocol Community Q&A — 27/08/2018


Last week the Trinity Telegram Community were invited to ask any questions they had for the core team, these questions were rounded up over the week and sent off. The Community will have another opportunity to ask further questions next month after the release of the Trinity-Ethereum state channels. Please find answers from the core team to the latest set of questions below:

Q1: I want to know if unlike the Neo nodes if the ethereum nodes will have the ability to backup your private key in the event that you have to restore your wallet if the server becomes corrupt.

ETH nodes do not back up your private key. If the server becomes corrupt, you need to restore the wallet after replacing the server. You can import the private key backed up by yourself in the wallet.

Q2: Can we have a video demonstration of how the user app works and its features.

Refer to Q4.

Q3: How do you seek to get enough Trinity-Ethereum nodes set up for the network to function properly?

After the simple node deployment platform is launched, users can experience one-click automation node construction through the platform, reducing the technical threshold for ordinary users to participate in the Trinity network construction and enabling more users to participate in the Trinity network construction. Some appropriate incentives will be introduced later, so stay tuned.

Q4: I’ve read the documentation that can be downloaded from the website (user app). I still have no idea what does what. Maybe if some examples were added it would help people understand what it is used for?

The new version of the app is still under development and improvement. The introduction of the app will have its functions and features after the new version is released.

Q5: Progressive whitepaper update?

Yes, it will be updated according to the latest research and development progress and direction, so stay tuned.

Q6: What are the ROI calculations for running a node?

The proportion of the node’s charging fee is set by the node holder. The return depends on the frequency of usage and the amount of charges.

Q7: “Optimization of the ETH full-node monitoring subscription service” Does this mean you can pay to have your node monitored?

It means that the team can monitor the nodes of the state channel, not the user.

Q8: “Completion of the development of the H transaction” what is the H transaction? Is it an atomic swap type capability?

HTLC transactions, which are transactions based on the “Hashed Timelock Contract” in the state channel technology.

Q9: “Deploy the USDT nodes, write the transfer of USDT, and query related interfaces such as transaction query” Does this mean they will be a built in stable coin/tether option?

We are still doing the research, so stay tuned.

Q10: Is the TNC routing algorithm optimized for shortest path or for path of least resistance. Or have they tried to balance the two? Its a bit of a comparison question between the different routing algorithms such as distributed balanced routing, flare and SpeedyMurmurs. David might say TNC will absorb what works best, but it would be good to understand what is being used for now and how modular this may be.

For the shortest path. Since the charges of the node is set by the node holder, the system cannot predict which path has the lowest charge. However, the user can choose which path to use according to his own needs.

Q11: About the fees. Is it that the node holder can set the fee rate, Or, is it that the fee rate and selection of node is not based on this, but based on the best possible route for the transaction to occur? Will the fees be automatically calculated and awarded...or can the user can manually set their own node fee and hope it is reasonable enough not to get rejected by the network to process transactions. I would imagine an automated solution would have been the method of transaction processIng with regards to selection of nodes and fee setting. Having persons set their own fee makes things to how does one set the best optimal fee so as to be selected on top of their nodes geo-location, hardware, etc…

The node’s charge fee is completely set by the node holders and can be calculated manually by users. Based on the above situation, stable operating conditions, reasonable rates, and shortest paths must be the key elements for users to select nodes.

Q12: What are the technical requirements for the Ether nodes?

Please refer to the upcoming technical document :)

The next upcoming milestone is the deployment of the Trinity-Ethereum state channels, so keep posted!

For a deeper dive into Trinity and to find out more about the project take a read of “Trinity: A universal Offchain Scaling Solution”




Telegram Announcement Channel: