Share on Twitter
Share on Facebook
Share on Reddit
Share via Email
Share on LinkedIn
Share via RSS
Share on Google+

Trinity Protocol has issued a bi-weekly report for the first half of April 2019, which includes the achievement of various technical developments. In the previous month’s report, Trinity announced the addition of “user stories” to its GitHub repository.

User stories are tools that assist developers in understanding certain features of their software from the end-users perspective. Trinity has identified eight user stories for future trinity-neo-gui functionality. Currently, the development team is working on two user stories, which focus on entrances and routing functions.

Trinity reports progress on constructing channels for transactions, which incorporates a multi-signature contract address for parties on both sides of the state channel.

Additionally, Trinity now creates channels according to a selection of user-defined inputs, which determine the message processing. Such message inputs include detecting a channel’s balance, obtaining all signatures in a multi-sig contract, and broadcasting and monitoring messages on-chain.

Lastly, Trinity has added both English and Chinese support in the GUI’s status channel; with the potential to add more languages if necessary.

Looking forward, Trinity aims to “focus on optimizing user experience and modularization of [the] product structure.” In conjunction, the team seeks to explore a user-friendly client with the ability to set-up and run state channel nodes.

Developers interested in assisting Trinity in the development of its client are encouraged to pull a request on the Trinity GitHub or to email suggestions to support@trinity.tech.

The full bi-weekly report can be found at the link below:
https://medium.com/trinity-protocol/trinity-biweekly-report-early-april-560135d1a8d8