OMNI Now Available on Bitfinex

OMNI, the world’s second-largest digital asset platform and the premier application layer on Bitcoin is now available for trading on the Bitfinex (https://www.bitfinex.com) exchange platform under the ticker symbol OMN against the BTC and USD markets.

Bitfinex is a digital asset trading platform that was founded in 2012 and offers state-of-the-art services for digital currency traders and global liquidity providers.

The Omni Layer is an overlay protocol on top of Bitcoin and holds over $2 billion in digital assets. Its tokens are the most traded digital assets on the planet, with the leading stable coin Tether USD₮ as its primary tenant. The project, formerly called Mastercoin and launched in August of 2013, was the world’s first ICO crowdsale, first decentralized smart contract platform and first decentralized exchange. Omni is an innovative open-source, community-driven project that allows for the creation of managed digital assets, securities, currencies and smart contract functionality on top of Bitcoin and Bitcoin-derived cryptocurrencies.  The Omni Layer is one of the oldest and longest-running open source development projects in the crypto ecosystem, continuing to lead innovative development in this exciting and fast-moving space.

More info is available at http://omnilayer.org, where you can learn about the advanced protocol capabilities of the Omni Layer on Bitcoin and download software for digital asset issuance, security token issuance, non-fungible token issuance, decentralized ICOs, and the decentralized exchange. Contributors are welcome at https://github.com/OmniLayer.

We welcome the listing of OMNI and Omni Layer assets like USD₮ on wallets and exchanges, and the Omni Layer team is always available to assist with integration on the official telegram channel: http://t.me/OmniLayer.

OMNI Now Available on Bitfinex

State of the Layer: 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

State of the Layer: Sep 20 2018

Omni Core v0.3.1 Released: Recommended upgrade!

Dear Omni Layer integrators and developers,
we released Omni Core v0.3.1, which is a minor release and not consensus critical in terms of the Omni Layer protocol rules.
Besides other improvements, this release provides two new RPCs to create funded transactions and to pay fees from different sources (omni_funded_send and omni_funded_sendall), two new RPCs (omni_getwalletbalances and omni_getwalletaddressbalances) to query token wallet balances, and significant stability and performance gains of Omni Core.
An upgrade is highly recommended.
To download and view the release notes in your browser, please visit:
While most exchanges list USDT, we would like to ask you to also consider listing Omni, the native token of the Omni Layer protocol. We would be happy to guide or help with an integration.
Please feel free, to contact us for questions.
Omni Core v0.3.1 Released: Recommended upgrade!

State of the Layer: August 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

State of the Layer: August 16 2018

Omni Core Integration Guide Now Available

With the growing popularity and increasing use of the Omni Protocol and the asset/tokens created there within, we have put together the following Integration Guide.

The primary goal is to provide a starting point for service providers/exchanges/wallet operators looking to incorporate the Omni Protocol into their platform. While this will not cover every single use case or integration option it should cover the majority and provide a good starting point for platform operators/maintainers on where to get started.

The full guide is available here: https://github.com/OmniLayer/omnicore/wiki/Platform-Integration-of-Omni-Core with an excerpt of the Table of Contents Below

Table of Contents

Omni Core Integration Guide Now Available

State of the Layer: 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

State of the Layer: July 12 2018

State of the Layer: 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

State of the Layer: June 14 2018