The Insolar Core development team is working on the Private TestNet for it to be launched on January 22, 2019, as well as developing other system components for later releases.
Testing the system using the benchmark utility. Some components have been optimized and the number of requests processed per second has been increased.
The system status contains information on the number of active nodes in the network. This will reveal inaccuracies in the synchronization of node state.
Removal of fund transfer mutual blocking. Fund transfer requests do not block both wallets anymore, meaning deadlock can be avoided.
A public key index has been created for registered nodes. The registration of nodes with the same public keys is limited.
Business Services / Block Explorer
BlockExplorer FrontEnd has been integrated with the Insolar platform. An end-to-end integration test stand has been deployed and a Long data load bug has been fixed.
The Loader from the Insolar platform to BlockExplorer DB has been updated. Integration with Insolar network statistic API released.
BlockExplorer DB structure has been updated. The structure for network statistic information storage has been updated.
The Unloader to BlockExplorer front-end has been updated. Socket usage has been excluded and changed to HTTP REST API. Requests for GetObject+GetRequest have been unified into one webpage.
Shared Business Processes
Creation of smart contracts on Insolar v1. Main smart contract structure for documents and processes has been developed.
Creation of smart contracts on Corda v1. Smart contracts for document and process integration with the business foundation layer have been developed.
Fair asynchronous contract calling implemented. The full async calling model allows to fire and forget requests with guaranteed execution. Calling contracts without awaiting for results will now not lead to deadlock.
Smooth execution transfer from node to node. The algorithm of transferring execution of an object to another node at the end of each Pulse now works correctly in a multi-node environment.
Redesigned node role calculation algorithm. Several complicated corner cases have been fixed.
Informing Virtual Executors about pending requests for a given object. When a Virtual Executor (VE) requests a state of object to execute a new request for it, a list of pending requests for that object is passed on, meaning the VE will wait for these requests to complete before executing any new request.