<aside> 🛠 This section is about the issues tackled by the development team for this week, and that the changes which won't be included in the next release right away.
</aside>
The next version (v100100), which will be released soon, will contain a core patch to stabilize block synchronization. this patch solves the structural problem of Libplanet, where block sync did not work smoothly as the number of nodes in the network increased. The level of parallelism by separating the part that receives blocks from the network and the part that evaluates blocks to calculate the next state By dividing , it is possible to catch up with the block state more quickly.
Also, before releasing v100100, we first applied the above patched version to our RPC server nodes. This has the effect of reducing more than 30% of the total network timeout, and we are closely watching for any other side effects before the full deployment.
Key fixes for block / transaction synchronization are scheduled for v100100 and later releases, and we plan to release all of them up to v100101 and conduct a 2nd community mining test at the same time. This is currently scheduled for early February, and the format will be tested by applicants only on a separate testnet, similar to the first community mining test.
We have a dev office hour every Thursday at 8PM(KST). Along with the #sugestion-voting channel, it's a place where we can know your suggestions and thoughts.
Providing a variety of convenience features to further increase usability is always one of the challenges of the game. In particular, there have been continuous inquiries about the item lock function. It is very important to protect valuable items. Moreover, the damage will be enormous if valuable items are lost due to incorrect manipulation.
We are thinking about various directions for implementing this.
Both directions have the same purpose, but the UI configuration and flow will be quite different. The team is thinking about which direction will be better suited to the pattern we play.