- Ontology officially announced the release of Ontology 1.8.0
- The update features support for Wasm, used by Google and Apple
- The update also reintroduces support for NeoVM, now faster than ever before
The Long-Awaited Release Is Out
On October 29, 2019, Ontology officially announced the release of Ontology 1.8.0 on their blog. According to the team, the highlight of the release is the inclusion of Wasm. However, other changes “under the hood” are present as well.
This version of Ontology has been running stably on TestNet for the past few months. After final testing and debugging, the team decided that the software is stable enough for the mainnet rollout. Here’s what’s new.
What is Wasm?
Wasm is a binary instruction format initiated by tech industry giants Google, Microsoft, Mozilla, and Apple. Wasm MVP is supported by the majority of popular modern web browsers.
The main advantage of Wasm is that applications written in several other languages, including C, C++, and Rust can be converted into Wasm byte code, thus making them cross-platform. As can be seen, this technology allows developers to save a significant amount of time.
Unfortunately, only a few dApp platforms support Wasm Virtual Machine currently. EOS, for example, is one of them.
With the introduction of Ontology 1.8.0, the project will join the ranks of EOS and other Wasm-supporting smart contract platforms by using a newly developed VM. It offers a wide range of advantages, including multi-language support and library support. What’s more, Ontology VM is a hybrid one, meaning that it supports two other types of contracts as well – Native and NeoVM. You can learn more about Ontology Wasm VM in this blog post.
Not Only Wasm
There is more to 1.8.0 update than just Wasm support though. The update reintroduces NeoVM, which now works faster than ever before.
So, the performance of its bytecode has grown almost three times, but the memory consumption is almost one third less. Even more impressively, the memory allocation has been reduced as well while maintaining and improving the node stability.
In the blog post, Ontology has stated that it will unveil more information in the near future, so stay tuned!