• The IOTA team are rewriting the code of IOTACore to address issues with debugging processes and bugs linked to legacy code.
• The new code structure is designed to be more like a living organism, with interconnected blocks acting like “cells” that adapt their state by observing their environment.
• Lead developer Hans Moog noted that improving overall quality and maintainability of the codebase is key for creating a more efficient and sustainable approach to software development.
IOTA Rewrites Code for IOTACore
The IOTA team has decided to rewrite the code of IOTACore in order to address issues with time-consuming debugging processes and bugs linked to legacy code. This new approach enables the team to work simultaneously without waiting for bugs in the testnet environment, as well as re-examine and check every single line of code.
New Code Structure
The IOTACore’s new code structure is more like a living organism, where blocks resemble a network of interconnected “cells” that automatically adapt their state or metadata by observing their surroundings. This allows information to spread through references in the tangle, while each node merely observes these cells and form its view for consensus.
Improving Quality & Maintainability
Lead developer Hans Moog explained the need for building an efficient and sustainable approach when it comes to software development, focusing on improving quality and maintainability of their codebase. This will enable them to find and fix any potential bugs quickly in order to avoid further delays down the road.
Advancements Ahead of Launch
Over the last two months, the main focus has been on developments for IOTAcore ahead of its 2.0 launch, which is currently their major priority over GoShimmer prototype development. By rewriting components from scratch during mainnet transition period, they can ensure smooth operation when launching live networks on multiple nodes worldwide simultaneously.
Conclusion
In conclusion, rewriting IOTACore from scratch was an important decision taken by the development team due its time-consuming debugging process which resulted in numerous bugs linked to legacy code structures. By reimagining this structure into a living organism-like network with interconnecting cells that observe their surroundings, they aim at creating a more efficient and sustainable approach towards software development – focusing on improving overall quality and maintainability of the codebase before launching live networks worldwide concurrently upon release date of 2.0 version upgrade