Progress

<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>

Bug fixes

--static-peer caused a lot of 26 error

Last week's hotfix, v100052, was a build that experimented with Libplanet's static peer setup, with block sync speed improvements. Static peers were developed as a minimal measure to defend against attacks, also known as eclipse attacks, but were also introduced on a trial basis to prevent recent network isolation.

The problem was that this hotfix had unintended consequences. The authentication miner set up as a static peer could not withstand a large number of connections and went down and restarted repeatedly. So far, this has been the expected result. But the real problem is, there was a bug in Libplanet that prevented the nodes from propagating their messages correctly when a static node went down. This led to a massive 26 timeouts.

The development team found the issue and rolled back the configuration, but didn't deploy it right away. First of all, the cause wasn't exactly known at the time, and there were concerns that the deployment could cause other problems. however, at the dawn of the 27th (Korean time), we decided that it was difficult to see the problem any longer, so we succeeded in reducing the number of errors by releasing v100053 that rolls back the settings.

Currently, the development team has reinforced exception handling so that it can handle correctly even when a static peer is down, which will be reflected in the next release.

Too many reorg, Too many timeouts (cont. )

Again this week, the team released v100054 as a hotfix to address this issue. The main expected effect of v100054 is improved node response time. (see also https://github.com/planetarium/libplanet/pull/1360)

We expected this patch to speed up node responsiveness, leading to smooth block synchronization. However, even after this patch, blocks that appear too late are still occasionally found. To solve this problem, we are also considering introducing a TCP proxy.

New features

Our short- and long-term economic model

<aside> 🎥 Check out our upcoming July 9th live stream for more details on this!

</aside>

The team is aware of the current NCG polarization issue in the game. It is difficult for new users to obtain gold through mining, and there are not enough other ways to obtain NCG. Because this polarization makes the whole transaction shrink, our team is thinking a lot about the economic cycle model.

We don't want to approach this problem only in a long-term way. By executing both short-term and long-term plans, we plan to address this issue sequentially. So you don't have to wait long for this problem to be solved.