Trinity Protocol, a developer of off-chain scaling solutions for the NEO and Ethereum blockchains, published two development reports in the month of January that focus on the development progress of its state channel networks. Trinity’s state channel network is designed to be a “second layer” solution for handling high transaction volumes with low fees.

Robust State Channels

Trinity’s January development work for its state channels has focused on network stability. Transaction verification for both counterparties has been added, which requires the parties to individually validate (digitally sign) the previous state channel transaction before the next transaction is processed. This regulatory step is designed to create a state channel that is more resistant to network outages, congestion, and other unexpected events, because the parties are forced to agree on the state of the ledger before more transactions are added.

Trinity Framework

Trinity also spent time in January developing the Ethereum-facing side of its project. According to Trinity, redundancies in its neo-trinity and eth-trinity code were generalized into a “lightweight Trinity framework.” In addition, improvements were made to transaction handling; a high-performance cache was implemented for the most recent transactions. This cache is designed to increase performance and efficiency by reducing calls to the full database of transactions.

Chinese New Year

Trinity is celebrating the Lunar New Year with a listing on MXC Exchange, previously covered by NEO News Today. Trinity has stated that 2019 will be a year in which its major development focus will be on the NEO blockchain. A “technical milestone” announcement is expected at February’s NEO DevCon; Trinity further states that “Trinity Foundation and NEO have made plans for in-depth technological cooperation” and that “Trinity will further the development for NEO” after the Chinese New Year.

Trinity Network’s development reports can be viewed in full at the following links:
https://medium.com/trinity-protocol/trinity-biweekly-report-early-january-4c6a6a079140
https://medium.com/trinity-protocol/trinity-biweekly-report-late-january-10c009154342