IOST Mainnet Olympus v3.10.1 Upgrade Announcement: Enhancements and Optimizations
As a critical foundation within the realm of public blockchain ecosystems, the performance of a mainnet profoundly shapes its advancement. Since its official launch on February 25, 2019, the IOST Mainnet has demonstrated over four years of operational excellence. Throughout this period, the dedicated IOST development team has consistently pursued innovative methodologies, effecting multiple version updates and optimizations. The IOST Mainnet has notably undergone exponential expansion in terms of DApp proliferation, mainnet accounts, and transaction volume, firmly establishing itself as a globally renowned Top 4 DApp public blockchain platform.
We are thrilled to herald the inauguration of Mainnet Olympus v3.10.1 today, a pivotal non-compatible upgrade. All nodes participating in block production are requisite to execute this upgrade by September 10th. Furthermore, non-block-producing nodes are strongly advised to conduct the upgrade as well.
Highlighted Modifications
The crux of this version centers around a significant enhancement to the libp2p module, ushering in yamux support alongside the pre-existing mplex framework. Subsequent iterations will involve the removal of mplex support. For comprehensive insights into the intricacies of this upgrade, kindly refer to the release notes provided at https://github.com/iost-official/go-iost/releases.
Important Points
It is of paramount importance that all block-producing nodes conclude the upgrade by September 10th. In instances where manual upgrading is undertaken, should a docker panic manifest during image reconstruction, it is advised to inspect whether the “security-opt” is set to “seccomp:unconfined.” The specific command is outlined as follows (presuming that the iServer data directory remains at the default location /data/iserver): docker run -d — name iserver -v /data/iserver:/var/lib/iserver -p 30000–30003:30000–30003 — security-opt seccomp:unconfined iostio/iost-node. Further guidance on completing this upgrade can be sourced from the instructions presented in the IOST developer documentation.
Upon successful execution of the upgrade, scrutiny of the hash and version can be carried out through the following command:
docker exec -it iserver iwallet state | grep -E “codeVersion|gitHash” The anticipated outcome should be as follows:
“gitHash”: “d7fdfb3747677f82e148cb4a90cbab90c339b149”, “codeVersion”: “3.10.1”
About IOST
IOST remains steadfast in its commitment to erecting a developer-centric public chain platform. Looking forward, the trajectory of IOST involves an unceasing pursuit of innovation, enhancement, and optimization of the mainnet, thereby furnishing heightened support in terms of underlying infrastructure and an enriching developmental milieu for all denizens of the mainnet ecosystem.
At this juncture, we extend our heartfelt gratitude to the IOST development collective and the global community of developers for their unflagging endeavors.
1 Comment