Trinity has published an article on how it intends to integrate its generalized state channel solution directly into NEO. The article documents the next steps for development and provides a timeline for the implementation, building on the previous announcement made at NEO DevCon.
Generalized state channels are a Layer 2 scaling solution, allowing transactions between peers without needing to interact with the main blockchain layer outside of settlement. With a large amount of transaction volume moved off-chain, the network’s scalability is increased multiplicatively based on the main layer TPS.
Trinity intends to integrate its state channel model directly into the neo-gui full node software, in a new version called trinity-neo-gui. This implementation will allow neo-gui users to decide whether to use state channels within the wallet, or whether to switch to the Trinity wallet for additional functionality.
By using NEO’s native interface, Trinity expects the development process to be more reliable and easier for end users to adopt. The team has also confirmed that it will implement its state channel model into neo-cli, potentially allowing light wallet clients such as the Neon, O3, or Aphelion wallets to provide state channel support.
The development of trinity-neo-gui is expected to take six to eight months, though trinity-neo nodes are already available for deployment. Users that wish to run Trinity nodes to access or support state channels without waiting for trinity-neo-gui may follow the instructions found here.
Trinity has also noted that its solution is designed for the existing NEO 2.x infrastructure, though continued development will aim to ensure a smooth integration into NEO 3.0.
Trinity has reiterated that it will use a large part of its remaining TNC token fund to reward any software contributors or Trinity node runners, whether they are running trinity-neo, trinity-neo-gui or trinity-eth nodes.