On this page
OmiseGO is the earlier name associated with OMG Network, a project built to scale Ethereum payments. The OMG token and the later BOBA token are separate assets. This distinction is essential for anyone returning to an old wallet or a profile written before the projects' later developments.
As of October 8, 2026, this profile can document the historical scaling model and the 2021 BOBA distribution to eligible OMG holders. It does not establish that the original OMG payment network is currently operating as described in its early promotional materials.
What OmiseGO set out to build
The original idea linked payment infrastructure with Ethereum-based settlement. OMG Network used a Plasma-style architecture, in which activity could occur away from Ethereum's main chain while relying on mechanisms tied back to it. That approach sought to reduce the burden of processing every transfer directly on Ethereum.
Layer 2 is a broad label, not one uniform security model. A Plasma system and an optimistic rollup can have different requirements for data, withdrawals and dispute handling. The particular implementation matters more than the shared claim of faster or cheaper transactions.
The original Coins Rate profile blurred a payment company's merchant relationships with adoption of the OMG token. A merchant using a conventional payment processor is not necessarily accepting OMG, securing its network or generating demand for its token.
OMG is a token, not company equity
OMG is an Ethereum token. Holding it is not the same as owning a stake in a payments company, and a company's commercial partnerships do not automatically confer rights on token holders.
Token supply, available trading supply and service utility are separate concepts. A fixed issuance does not establish that a network feature promised in an early roadmap was delivered. This article does not use a historical market capitalization or ranking as evidence of present relevance.
When identifying an old holding, the chain and contract must match the asset in the original records. A familiar ticker in a wallet interface is not enough to establish that a similarly named token is the same one.
How Boba fits into the history
Boba emerged from development associated with the OMG ecosystem, but it uses its own BOBA token. Exchanges documented a distribution to eligible OMG holders based on a November 12, 2021 snapshot. For participating holders, the stated ratio was one BOBA for each eligible OMG.
A snapshot-based airdrop is a historical eligibility event. Buying OMG later does not recreate the old eligibility condition, and the event should not be described as a permanent exchange right. The asset held, the holding location and the rules applied by a participating custodian affected distribution.
Boba's present tokenomics page describes its own 500 million-token allocation and unlock history. Those are BOBA figures, not a new supply schedule for OMG. Treating Boba as simply a renamed OMG token would erase an economically important distinction.
What remains uncertain about the legacy network
The old article presented very large theoretical throughput claims and future staking ambitions as if they settled the project's prospects. They do not establish current throughput, validator participation or usable withdrawals. A network's theoretical design must be separated from the service actually available.
Current OMG production activity and legacy deposit and withdrawal routes remain unconfirmed. A token continuing to appear in markets is not enough to fill that gap. Tokens can remain transferable even when an associated application changes direction.
How to interpret old balances and markets
An exchange listing, a token balance and a usable scaling network answer different questions. The first concerns a service provider, the second concerns a ledger entry, and the third concerns infrastructure. All three can change independently.
For an old OMG balance, preserve the original chain information and transaction history before following any migration or recovery instructions. Claims that a holder must urgently convert to BOBA should be checked against an authentic, applicable announcement rather than inferred from the historical airdrop.
The lasting lesson of the OmiseGO story is the importance of separating a token from its wider corporate and development ecosystem. That separation makes the project's history easier to understand without converting old ambitions into present capabilities.