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

Maintenance Event – June 5th 14:00 UTC

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.

Maintenance Event – June 5th 14:00 UTC

State of the Layer: May 23 2018

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

State of the Layer: May 23 2018

State of the Layer: Apr 13 2018

Community

Over the past few weeks we’ve seen an increase in community emails about where and how users can trade or sell some of the property tokens they hold. While traditional changes do sometimes offer a larger orderbook/market they may not always carry the property market you are looking or they may delisted the market you wanted to use. With this in mind we wanted to remind all users that the OmniDex is always available and allows you to post trades of one Omni Protocol token for any other Omni Protocol token. If there is a matching order on the book your trade is completed instantly, otherwise it’ll stay open until another user posts a matching trade. Check out the full getting started guide for additional information: https://github.com/OmniLayer/omniwallet/wiki/Using-the-OmniDex

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

Project Updates

OmniExplorer/OmniAPI

The second round of updates and tweaks to the UI are now out. Addresses should be easier to copy and overall localizations should be a bit better. Updates to api data/calls to support additional data filtering is underway in preparation for the next release.

Omniwallet/OmniEngine

This past month we’ve rolled out some additional Property Management features within Omniwallet. First, Managed properties are now available in Omniwallet. Users now have the ability to create a Managed property as well as access to the Grant/Revoke utilities of these tokens. Additionally the Change Issuer functionality is also now available. These features are accessible from the My Assets page within your Omniwallet account.

Roadmap

State of the Layer: All Hands – Feb 13 2018

State of the Layer: Apr 13 2018

State of the Layer: All Hands – Mar 13 2018

Community

After nearly a month of dedicated work we are pleased to provide this months update.  As promised our initial 2018 roadmap is now complete and available below. Along with this we are also excited to announce updates for several of our hosted projects.

Want to engage more with Omni?

Check us out on Reddit Telegram, and Twitter.

Project Updates

OmniExplorer

The first phase of the redesigned Omni Explorer is now complete and in final review/testing. We anticipate it should be ready for release tomorrow. Built on react boilerplate this is a ground up rebuild. Designed to have a minimal initial load, data is loaded from our api server as needed. The next phase will finish the majority of the ‘coming soon’ placeholders. But for now the core dataset (address balances, history, transaction details, and property information) is available. Here is a little sneak peak of what to expect with the release:

Teaser

OmniAPI

Now operational, our hosted api service is feeding data to the newly redesigned OmniExplorer. Over the next several days we will be updating and documenting available routes, endpoints and example calls to provide integrators with initial access to protocol data.

Omniwallet/OmniEngine

In preparation for the new explorer, our backend parser (omniEngine) has been updated and now supports unconfirmed/pending network transactions. This data is accessible and usable by both the new api server as well as Omniwallet. Users should notice pending transaction data a little more quickly now within wallets when receiving transactions from outside services.

Omnicore

As previously stated we are currently looking for additional c++ developers familiar with bitcoin technology who would like to participate in and contribute to the project.  Any interested applicants can contact jobs@omni.foundation

Roadmap:
  • Omni Core
    • Fees distributed to Omni holders from decentralized exchange
      • Decentralized trades not involving Omni are subject to a 0.05 % fee
      • This fee is distributed to all Omni holders
    • Optimizing transaction size
      • Shorter marker
      • Merging version and type fields
      • Using LEB128 to compress numbers
    • Non-fungible tokens
      • Creating, managing and sending uniquely identifiable tokens
    • Send-to-many transactions
      • Allows to bundle transactions
      • Requested by and very useful for exchanges
    • Crowdsales supporting bitcoin
      • Currently only tokens can be collected
      • Opens the road for native bitcoin based ICOs
    • Updating the architecture of Omni Core
      • Useful for thin clients
      • Paves the way for verification with VerSum or similar
  • Omni API
    • Update api documentation
    • Improve/add
      • Exchange information
      • Statistics and usage information
  • OmniExplorer
    • Refine UI/Styling
    • Improve Mobile design/rendering/size
    • Evaluate reporting/graphing/statistics/info options
  • OmniWallet
    • Refactor to use new OmniAPI
    • Enable better portability/usability in stand alone configurations
    • HD address/wallet support with recovery phrase
    • Hardware wallet integrations
  • Other items
    • Possible Electrum integration
      • Show token balances
      • Create and transfer tokens

 

State of the Layer: All Hands – Feb 13 2017

State of the Layer: All Hands – Mar 13 2018

State of the Layer: All Hands – Feb 13 2018

Community

Want to engage more with Omni?

Check us out on Reddit Telegram, and Twitter.

Project Updates

 

OmniExplorer

Work on layouts and component structure continues. Getting ready for data integration from api

Omnicore

As previously stated we are currently looking for additional c++ developers familiar with bitcoin technology who would like to participate in and contribute to the project.  Any interested applicants can contact jobs@omni.foundation

 

OmniAPI

Initial api service is running. Streamlining, optimizing and legacy OE route integration work underway.

 

State of the Layer: All Hands – Feb 06 2017

State of the Layer: All Hands – Feb 13 2018