Simplifying Omega One
Simplifying the Omega One Whitepaper
Here we’ll quickly breakdown what Omega One is and the system’s consensus protocol, potential vulnerabilities, and projected future state — all straight from the white paper in a way we call can understand!
Note: You can access my annotated version of the white paper here. These notes have been compiled from the most crucial descriptive aspects of Omega One’s technical stack/environment.
What is Omega One?
Omega One is a decentralized exchange platform that strives to solve the problems of crypto market illiquidity, fragmentation, trade cost inefficiency, and security. Omega One solves these problems by providing traders, investors and institutions with a decentralized automated trade execution system that intelligently implements their trades across the world’s crypto exchanges, shielding them from counter-party risk and reducing their costs of trading.
Problems of Crypto Trading Markets
- A lack of liquidity, causing realized costs of trading to be often many times higher than published commissions and fees. Liquidity is the ability of a market to absorb transactions without a change in price. The total value of even the BTC and ETH asset classes are still much lower than traditional markets and are considerably fragmented.
across many exchanges. Here’s an example:
For instance, buying $1m worth of EUR vs USD tends to move the price by ~0.01%, while buying $1m of ETH vs BTC will move the price by 1%-10% depending on conditions, or 100-1000 times the most liquid traditional markets. This can cost traders up to 25 times as much as the published exchange fees, but since the extra costs are hidden in the price of the purchased asset they are often not fully accounted for. (Omega One White Paper)
- A lack of security, in which the most liquid transparent venues come with risk of loss due to hacking. All production exchanges are centralized, and open to hacking.
- A lack of transparency into the actual costs of trading. Until there are trading services that provide transaction cost benchmarking and analytics to these institutions, they will be obstructed from trading in this asset class, hindering the maturation of crypto markets.
Omega One Architecture/Features
The Omega One Architecture is compartmentalized into the following 6 components
- User Interface/API of the platform
- Omega One Wallet — Holds members funds in a decentralized, trustless and non-custodial portfolio and locks member funds within the wallet when making trades on the platform
- Omega Private Exchange — Internally matches parent orders. Such matching is a part of an automated trade execution service that matches our member’s orders, offloads unmatched liquidity onto public exchanges via a trading engine, and settles directly onto multiple blockchains.
- Trading Engine — Assesses overall liquidity across exchanges given the net order its received from the private exchange. Based on zed assessment, it will break chunks of the “Net Order” into “Child Orders” that represent a timeslice of executable liquidity demand for each pair at a given moment. That “Child Order” is then further broken down into “Street Orders” that are the actual orders executed on each exchange (these can be placed as limit orders, market orders, or other order types depending on how the trading logic can best optimize market liquidity).
- Balance Sheet Manager — Omega One requires a significant balance sheet in order to harvest liquidity from the marketplace and trustlessly serve it up to our members in the Omega Private Exchange. At a minimum, Omega One needs to keep at least enough funds on all exchanges, across all assets, in order to perform the trades required to satisfy all open Net Orders.
Additionally, here are some standout aspects of the platform:
- High level of interoperability between blockchains (and their respective overlying tokens)
- Protocol is mediated by the Omega Token (OMT), a cryptographic token that provides membership access and can be used to pay trading fees.
- Higher OMT balances correlate to preferential liquidity treatment and discounted trading fees.
- Omega One will provide enhanced security by intermediating between blockchain wallets and on- or off-chain exchanges with our own balance sheet, shielding our members from risk.
- Omega One will provide enhanced transparency by providing benchmarking and analytics of transaction costs to our members, to allow them to audit the market impact of their trading.
- Liquidity transaction flow of Omega One (pg. 9):
The Omega One Token Economy
- OMT is an Ethereum (ERC20) tradable asset.
- Tokens will be sold to members initially in a token auction, and then after launch on an ongoing basis.
- NEO has two native tokens, NEO (abbreviated symbol NEO) and NeoGas (abbreviated symbol GAS).
- Total Token Volume: 100 million tokens (represents the right to manage the network). Management rights include voting for bookkeeping, NEO network parameter changes, and so on. The minimum unit of NEO is 1 and tokens cannot be subdivided.
- GAS is the fuel token for the realization of NEO network resource control, with a maximum total limit of 100 million. The minimum unit of GAS is 0.00000001.
- Token distribution follows decay algorithm in about 22 years time to address holding NEO.
Omega One Token/Gas Distribution Mechanism
- NEO’s 100 million tokens is divided into two portions. (1st 50M to token sale supporters of NEO, 2nd 50M goes to NEO Council to support NEO’s long-term development, operation and maintenance and ecosystem w/ 1 year vesting period)
- GAS is generated with each new block. The initial total amount of GAS is zero. With the increasing rate of new block generation, the total limit of 100 million GAS will be achieved in about 22 years. The interval between each block is about 15–20 seconds, and 2 million blocks are generated in about one year.
Omega One Consensus Protocol
- Velocity Engine — The Velocity Engine takes the NetOrder (6) in each Pair.Direction and manages how fast it is traded (size/time).
- Execution Engine — While the Velocity Engine is responsible for deciding how much size s of a given NetOrder should be traded in a given time t, the Execution Engine is responsible for trading that slice of the NetOrder most efficiently within that time.
- Velocity Engine is developed poorly and project’s trades cannot scale
- Execution Engine is developed poorly and project’s trades cannot scale
- The functionality of the exchange is dependent on the centralized exchanges it is placing orders on. So if credible exchanges get hacked that Omega One uses — it has less liquidity to pull from
- Omega One’s broker accounts on centralized exchanges (so that it can settle trades more quickly without transferring your money all the way to the many exchanges your trade is settling on) will be subject to attacks and have limited security (limited to the exchange team’s security practices)
This is a huge technical obstacle to overcome when it comes to Omega’s risk management and protocol centralization — fronting costs on centralized exchanges to ensure the security of trader funds is risky at this stage (see pg.12 in white paper)
- Most of funding going into counterbalance funds for trading (pg. 33)