This article was first published on Loom Network - Medium
Loom Protocol — The Next Generation
Loom Network’s mainnet, Basechain, went live in December 2018, and since then, we’ve upgraded the protocol numerous times in order to fix bugs and add many new features. One of our primary goals has always been to ensure that our mainnet upgrades resulted in zero downtime for dapp developers and users. Barring a few brief chain halts in the early days, we’ve done a pretty good job of reaching that liveness goal.
Unfortunately, such live upgrades are not without a cost. Some core dependencies of the Loom protocol couldn’t be upgraded without incurring a significant amount of downtime, because backwards compatibility was not as high of a priority for the authors of those dependencies as it was for us. This lack of backward compatibility in our dependencies forced our blockchain development team to spend a significant amount of time carefully backporting important bug fixes and features. However, backporting has its limits, as the code eventually diverges too far for that approach to remain practical.
The Loom protocol code has also accumulated a lot of cruft since the mainnet went live. We’ve shipped a few features that turned out to be less useful than we envisioned, and we fixed many bugs in some non-ideal ways to ensure that the fixes could be deployed without any downtime.
So we need to address all that technical debt, upgrade core dependencies, and redesign some of the core systems — now that we have a much better understanding of how the initial designs performed in production. It’s time for us to build the next major version of the Loom protocol that will power Basechain and other blockchains we build for our enterprise clients. Let’s take a look at a non-exhaustive list of changes that will be going into the new version:
- Upgrade the consensus engine ...
To keep reading, please go to the original article at:
Loom Network - Medium