Hello OMG Network V1 Testnet

In Blog, OMG Network by OMG Network

Hello, OMG Network V1
Highlights to v0.4
  • Audited contracts – This is our first public testnet with audited contracts.
  • Transaction Fees – We are now taking fees, which are described by a new API endpoint.
  • Move to Ropsten – We’ve moved from Rinkeby to Ropsten to better approximate Mainnet behavior.
What changed?

Our last environment, named pre-Lumphini (v0.3), was deployed in the middle of the audit process. Since then, we completed the audit with some significant changes to the structure of our contracts, transaction formats, and minor changes to our ABI. Most of these changes are abstracted away behind the child chain, watcher, and omg-js APIs. You can view the audit reports here.


Fee tokens and amounts are described in a new API endpoint, /fees.all. Currently, the testnet is launching with fixed fees per transaction. We will continue to develop the operator pricing model in the coming weeks. From an integration perspective, the mechanics of fee discovery and inclusion will remain the same under new fee models. For ease of integration, fee handling is primarily abstracted behind existing transaction APIs and omg-js, making transaction flow a familiar process for end users. More details in the migration guide below.


The Ropsten testing environment is the closest you can get to being on Ethereum Mainnet. It is a testnet that runs the same consensus mechanism and behaves much like the Ethereum Mainnet. It is supported by both Geth and Parity – two different implementations of the Ethereum node software that both support Mainnet. 

Ropsten ETH (rETH) has no value, it is free and can simply be taken from the Ropsten Faucet. However, because it has a Proof of Work (PoW) consensus mechanism, its ETH can be also mined just like on the Mainnet. The PoW consensus mechanism results in the most similar transaction behavior to Mainnet.

Ropsten is, in its own right, a true and functioning blockchain. It has its own mining pools, own software, a realistic consensus mechanism, etc.

Migration Guides

To migrate your integration from v0.3 to v0.4, you can refer to the guides below:

  • Omg.js, Watcher, and Child Chain API Migration Guide
  • For migration help from v0.2 to v03, you can see our previous migration guide here