Trinity is developing multi-dimensional trinity-neo-gui based on the ‘user story’. In the previous articles, we have listed eight user stories for the future trinity-neo-gui. Features #2 and #4 are currently under development, and the other features will be developed simultaneously after this.
- Construct channels for transactions. Construct a multi-sign contract address, which is used as the deposit address for both sides of the channel. Complete the construction of the three messages, namely Founding Transaction, Commitment Transaction, and Revocable Delivery Transaction, based on which a channel will be created.
- Processing messages of channel creation. According to the parameter of user’s input, the message processing of the channel creation will include the detection of the balance of the channel, construction of the message, obtaining signature of both sides of the message, broadcast of the message and monitoring of the message on the chain.
- Language support in the status channel GUI. The GUI will support both Chinese and English to meet different user needs. More languages could be added based on actual needs.
Trinity has now completed the development of a protocol layer based on Neo and ETH (see https://trinity.readthedocs.io/en/latest/en-EN/index.html for details).
After Trinity’s development returning to Neo, we will focus on optimizing user experience and modularization of product structure. At the same time, we will conduct more research and exploration on client that integrates the set-up and running of state channel nodes, and possibly design the subject from a user-friendly and secure perspective before diving into development. If you have good ideas, please pull your request on GitHub or email us at firstname.lastname@example.org, we’d love to hear from you.