Community

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

Project Updates

OmniExplorer & OmniAPI

We’re currently working on some performance optimizations and layout improvements for the Explorer homepage and transaction lists.

 Omniwallet

Minor performance updates and bug fixes.

Omni Core

Documentation updates and planning for the next release.

OmniJ

OmniJ 0.5.6 was released (CHANGELOG)  This version updates many dependencies and supports the latest Omni Core release. It also requires Java 8 or later.

Roadmap

State of the Layer: All Hands – Sep 20 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

Community

There have been recent reports of scam sites starting to popup which aim to imitate Omniwallet in an attempt scam people out of their wallet information. Please remember Omniwallet’s official url is https://www.omniwallet.org . To prevent loss, always double check the url of the page you are visiting before attempting to login to your wallet. Additionally we urge users to ensure they have setup/enabled a compatible MFA device on their wallet.  As a final note/recap, we recently released the updated Omni Core Integration Guide . If you are looking to integrate Omni Core into your platform this should be your first stop for information.

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

Project Updates

OmniExplorer/OmniAPI

General backend stability improvements and bug fixes.

 Omniwallet

Minor performance / ui updates and bug fixes.

Omnicore

Version 0.3.1 is in final release prep. We are finalizing release notes and verifying builds. We expect to announce the general release within the next 2 weeks. In addition to some general stability and performance improvements this release adds some new rpc calls which support local wallet balances and funded sending.  Funded sending (a more in depth article to follow) allows the use of an additional address to help cover the extra BTC needed when sending an Omni Protocol transaction. In order to validate with the bitcoin blockchain the original sending address will still need at least one utxo to contribute to the transaction but now the bulk of the network/mining fee’s can be paid from a separate address.

Roadmap

State of the Layer: All Hands – July 12 2018

Community

We recently release an intro guide for Integrating Omni Core to receive payments.  This was in response to community messages over an exchange that had unfortunately integrated and implemented the client without taking into account the full details of a transactions validity before processing it on their platform. Over the next few weeks we will be working on a more indepth version of this guide which will be usable by any integrator wishing to add support for the Omni Protocol. It will also be encouraged for  project developers to reference this guide when having their project added to new exchanges/platforms.

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

Project Updates

OmniExplorer

The next UI update for OmniExplorer is now live. This brings additional usability updates and tweaks to data presentation/interaction. More uniform layout between pages with similar data and of note added support for active crowdsales information.

OmniAPI

Released in the past few days we now have the initial API documentation  published and available.  As new calls are added/tested they will be published/updated as well.

 Omniwallet

Maintenance updates to the code and some cleanup/removal of older deprecated calls. Updated readme to more accurately document setup procedures.

OmniEngine

All backend updates and changes have been updated and incorporated into the project. Additionally we’ve pushed a few bug fixes and optimizations to the parsing engine

Omnicore

Version 0.3.1 is going through some final testing. Eager early adopters can pull the develop branch from the github repo to test out the pending updates. We welcome testing feedback in the repo as well. This upcoming release will include some rpc interface bug fixes and some new rpc calls aimed at trying to simplify some of the integration paths/use cases of the client. Full details will be available upon final release.

Roadmap

State of the Layer: All Hands – June 14 2018

Community

Our previous announced Planned Maintenance is now completed. This update has allowed us to add several new optimizations to our backend which has resulted in  significant performance improvements for our frontend applications.

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

Project Updates

OmniExplorer/OmniAPI/Omniwallet

Benefiting from the backend updates OmniAPI interactions and as such all OmniExplorer and Omniwallet experiences should be significantly quicker to respond now. The next update which includes some additional informational menu items and optimizations should be ready for release next month.

OmniEngine

All backend updates and changes have been updated and incorporated into the project. Additionally we’ve pushed a few bug fixes and optimizations to the parsing engine

Omnicore

Version 0.3.1 is going through some final testing. Eager early adopters can pull the develop branch from the github repo to test out the pending updates. We welcome testing feedback in the repo as well. This upcoming release will include some rpc interface bug fixes and some new rpc calls aimed at trying to simplify some of the integration paths/use cases of the client. Full details will be available upon final release.

Roadmap

State of the Layer: All Hands – May 23 2018

Planned Maintenance:

On Tuesday June 5th we will be performing our previously mentioned planned maintenance to upgrade several backend components.

The Maintenance will start at approx 14:00 UTC June 5th, and we expect it to last around 8 hours. During this maintenance window all Omniwallet and OmniExplorer services will be temporarily unavailable. We strongly encourage any users who expect to need access to their wallets during this time attempt to perform any movements before the maintenance window begins or to take the proper preparatory steps necessary to have any needed funds available in alternate locations.

This Maintenance will not affect any Omnicore users or any integrations using the Omnicore client. Any services which are directly utilizing Omniwallet or OmniExplorer will be unavailable during this time.

Community

Upcoming Planned Maintenance affecting Omniwallet/OmniExplorer: June 5th.

Within the next 2 weeks we will be announcing a maintenance window which will require downtime for both Omniwallet and Omniexplorer. During this maintenance window we will be upgrading the backend database. These upgrades will allow us to add some additional database indexes which should result in some query performance improvements overall.

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

Project Updates

OmniExplorer/OmniAPI

We are currently testing the next release for OmniExplorer which includes support for crowdsale listings and information as well as numerous other fixes/updates/tweaks. As mentioned above there will be an upcoming maintenance window (TBD) which will require downtime of OmniExplorer and OmniAPI. Part of this maintenance window will allow us to add additional indexes which should allow us to develop more robust api queries in the future.

Omniwallet/OmniEngine

A mentioned above there will be an upcoming maintenance window (TBD) which will require downtime of Omniwallet. During the maintenance window all Omniwallet services will be unavailable however any funds received by users during this time will be unaffected. Once the maintenance window is complete all wallets and funds will be accessible again.

Omnicore

A big kudos to dexx for working on and starting the new Omnicore wiki over the past few weeks. Going forward it will become the defacto reference point for information regarding Omnicore, expanding and pulling new information from topics/issues as they are identified.

Roadmap

State of the Layer: All Hands – April 13 2018