Trinity Biweekly Report — Early July
Technological progress
1. Completion of the Trinity state channel that supports NEP-5 assets; When user add NEP-5 assets through NEO_GUI interface, and the Trinity state channel will automatically identify that asset types. Thus, channels can be later established based on this asset type.
2. Construction of a unified structure of the transaction interface; In order for the Trinity service module to support various asset types, including but not limited to NEO / GAS / NEP-5 assets, Trinity provides an interface to adapt to different asset types and reduce coupling between business modules.
We have now completed the pre-released version of trinity-neo-gui (V0.1.0), where all NEP-5 assets can be transferred through the Trinity state channel. This version is currently available for download and use on Windows systems. However, many functions and interfaces have yet to be optimized, such as the time span of the HTLC transaction from its start to the end as well as the language support on the interface. Trinity-neo-gui is still on the way. Stay tuned.
Pre-V0.1.0 download here https://github.com/trinity-project/trinity-neo-gui/releases/tag/Prerelease-V0.1.0
