This week we announce the release of Omni Core v0.7.1.

Omni Core 0.7.1 paves the way for trading any asset on the Omni Layer for Bitcoin in a decentralized fashion and it adds new commands to accept and execute orders on the distributed exchange.

Please note, if you have not yet upgraded from 0.6 or earlier versions: Omni Core 0.7 changed the code base of Omni Core from Bitcoin Core 0.13.2 to Bitcoin Core 0.18.1. Once consensus affecting features are enabled, this version is no longer compatible with previous versions and an upgrade is required. Due to the upgrade from Bitcoin Core 0.13.2 to 0.18.1, this version incorporates many changes, so please take your time to read through all previous release notes carefully. The first time you upgrade from Omni Core 0.6 or older versions, the database is reconstructed, which can easily consume several hours. An upgrade from 0.7 to 0.7.1 is seamless.

To view the complete release notes in your browser and download the binaries, please visit: https://github.com/OmniLayer/omnicore/releases/tag/v0.7.1

State of the Layer: End of Year 2019

Community

Earlier last week we identified an edgecase issue in Omni Core which affected the client during startup. To recap from our tweet, when a client started it will fail to validate the cached freeze status and force the client to shutdown. The workaround was to start the client with `-startclean` which removed the cached files and forced a re-parse of the existing data, the downside is that this could be a very slow process.

We are happy to say the fix for this has been tested and will be included in the next release of Omni Core, v0.5.0, which is going through it’s final QA checks for publication shortly. A separate announcement post will follow with the details of the release when ready.

Want to engage more with Omni?
Check us out on Reddit , Telegram, and Twitter.

Project Updates

OmniExplorer & OmniAPI

Development continues on performance and functionality improvements.

 Omniwallet

Patched an issue in the wallet import function that could allow a user to import a manually modified wallet backup with a mismatched address/private key pair incorrectly.

Omni Core

Finalizing testing and release for version 0.5.0.

Roadmap

State of the Layer: All Hands – March 21 2019

Community

This is a reminder to the community that Omni is not and does not run any type of ‘Bonus’ events where you can ‘claim’ any sort of reward or token. Please be extra careful of any site that asks you to login to your Omniwallet or provide any sensitive information in exchange for free money. Remember If it’s too good to be true, then it probably is. Users should be suspicious of people or situations that offer any type of benefit and ask for very little in return.

Want to engage more with Omni?
Check us out on Reddit , Telegram, and Twitter.

Project Updates

OmniExplorer & OmniAPI

Our next update has been rolled out this morning. This update brings with it some ux improvements including partner explorer transaction links, automated banner messages if issue is detected on backend, additional tooltips/banners for transactions. Also now available is the Feature activation list in the misc menu and several minor bug fixes/layout tweaks.

 Omniwallet

Minor layout/message updates.

Omni Core

Reminder the newest release is out, please make sure you have upgraded to Omnicore 0.4.0 released

Roadmap

State of the Layer: All Hands – Feb 13 2019

Community

There have been a growing number of reports of users being scammed because they have been purchasing previously created wallets and don’t actually have control of the funds within those wallets. This is a very important reminder to never purchase a wallet or an address from anyone. If you did not create the wallet or the addresses within it, you can not confirm the security of anything given to you. Always insist that any transfers are sent directly to an address you created and you alone control.

Want to engage more with Omni?
Check us out on Reddit , Telegram, and Twitter.

Project Updates

OmniExplorer & OmniAPI

With the new year we have a significant update to our explorer which aims to improve reliability and performance of the platform. We have also simplified the ability to view transactions by presenting them on a per block basis now and moving unconfirmed transactions to a dedicated view. There are several other fixes and tweaks behind the scene for consistency. Updates to the api documentation will be following in the next few weeks.

 Omniwallet

Cleaned up Wallet Address display to present Spendable and Watch Only Addresses in a more clear fashion. Researching Hardware wallet support.

Omni Core

Planning for the next release. RPC Edge case fix added to develop branch.

Roadmap

We will be moving to a new Trello based roadmap over the next few weeks and once complete we will be opening it up for general review/monitor by the public

State of the Layer: All Hands – Nov 30 2018

Community

With the recent listing on Bitfinex we are curious to know where the community would like to see Omni next. For the next few weeks we will be collecting input from the community here. Please take a moment to share your preferences.

Want to engage more with Omni?
Check us out on Reddit , Telegram, and Twitter.

Project Updates

OmniExplorer & OmniAPI

Updated dependencies, add new api calls to support OE layout changes. Minor bug fixes and data presentation normalization. Finalizing new layout changes for OE to improve performance and data presentations

OmniEngine

Add new db fields and calculations to start tracking stats per block for api/explorer.

 Omniwallet

Updated dependencies, minor performance updates and bug fixes. New warning message for wallet export.

Omni Core

Planning for the next release.

Roadmap

State of the Layer: All Hands – Oct 26 2018

Community

Recent outage update:

We are still investigating the full details behind the issue that caused the recent outage of Omniwallet, OmniExplorer and downstream problems for services that relied on data from them. We want to share what we have found so far and what is being done to mitigate future issues.

What happened:

On Sep 17 at 10:46 UTC the backend process used by our parsing engine to pull Omni protocol data into the database was forcibly terminated by the system due to an unexpected memory violation. The restart & recovery process was delayed due to logistical issues. Once the restart & recovery process began, the data verification and resync took longer than expected.  

What’s next:

First, we are working to eliminate the logistical issues that delayed the restart. Second, we are investigating ways to improve availability, by speeding up the data verification and resync process as well as adding redundancy.

Want to engage more with Omni?
Check us out on Reddit , Telegram, and Twitter.

Project Updates

OmniExplorer

Our most recent update brought with it some significant behind the scenes updates aimed at improving overall performance, usability,  and reducing duplicate queries to the api.  On the frontend the homepage now has some new transaction stats and graphs and by default flagged properties are now hidden from view on balance displays to cleanup overall usability.

OmniAPI

General backend stability improvements, bug fixes and additional data consolidations to support OmniExplorer updates.

 Omniwallet

Minor performance / ui updates and bug fixes.

Omni Core

Version 0.3.1 was recently released. An important note about CVE-2018-17144. Omni Core is unaffected by the CVE-2018-17144 bug. If you are running v0.3.1 then no further action is necessary. If you haven’t upgraded yet we recommend you do so. See additional information about the release in the recent post here.

Roadmap

State of the Layer: All Hands – Aug 16 2018