5OMCADE supply
One billion OMCADE exist, and no more can be made. This page shows where they sit, how the first 29 million reach circulation, and what releases OMCADE from the reserve today.
5.1Absolute maximum ratings
| Parameter | Value | Conditions |
|---|---|---|
| Total supply | 1,000,000,000 | Fixed. All of it was minted when the contract was deployed. |
| Minting after deployment | None | No new OMCADE can be created. |
| Reserve custody | Safe.global multisig | Holds the supply not in circulation. Moving anything needs multiple signers. |
| Planned circulation through Phase III | 29,000,000 | The distribution matrix below, liquidity allocation included. |
| Permanently unrecoverable | 10,000,000 | Sent by mistake to a pool contract that can't return them. Nobody can move them; they still count in the total. |
5.2The whole supply, to scale
- Phase I · Beta
- Phase I · Alpha
- Phase II · VIP epochs
- Phase III · VIP epochs
- Liquidity allocation
- Unrecoverable (sent to a pool by mistake)
- Reserve (Safe.global multisig)
- Note 1. On 11 October 2026 the reserve held 979,964,190 OMCADE: not every planned release has left it yet.
5.3Distribution through Phase III
| Channel | OMCADE | Details |
|---|---|---|
| Phase I · Beta | 2,000,000 | Distributed to early participants. |
| Phase I · Alpha | ~2,000,000 | Distributed to early participants. |
| Phase II · VIP epochs | ~5,000,000 | 500,000 per epoch over 10 consecutive epochs. |
| Phase III · VIP epochs | ~10,000,000 | 1,000,000 per epoch over 10 consecutive epochs. |
| Liquidity allocation | 10,000,000 | For the public pool, drawn on in tranches, as permanently locked positions, whenever fee OMCADE can't keep the pool supplied. Replaces the original allocation, lost in a transfer error (see note). |
| Total, Phase I–III | 29,000,000 | The cap on OMCADE released through Phase III. |
- Note 1. Figures as published in the OMCADE Platform Whitepaper, v2.1.0, §4.3. “~” marks allocations stated as approximate there.
- Note 2. There is no team allocation. Team members hold small amounts of OMCADE from the reserve, used only to test the platform (see below).
- Note 3. The original 10,000,000 OMCADE liquidity allocation was sent by mistake to an old OMENX/USDT pool contract, which can't return them. Nobody, Omen included, can ever move them, so they are permanently out of circulation. The allocation above replaces them from the reserve, so the plan for Phases I to III still releases 29,000,000 from the reserve. VIP epochs have also shared out about 1,500,000 OMCADE collected as platform fees: OMCADE players had already spent, going back out, not new OMCADE from the reserve. That's why VIP epochs total about 16,500,000 so far. The platform features listed below release OMCADE too, and every release can be followed on BscScan.
5.4What releases OMCADE from the reserve
Outside the matrix above, OMCADE leaves the reserve only through these platform mechanics.
| Mechanic | What it releases | Status |
|---|---|---|
| Faucet NFTs | A fixed daily amount per NFT, set by its tier. | Live |
| Manager NFTs (Asset Manager in the app) | Paid in OMCADE when a holder burns the NFT. | Live |
| Referrals | A share of referred players' allocations. | Live |
| Daily spin | OMCADE grants on the daily reward wheel. | Live |
| Team test wallets | Small amounts sent to the team's wallets to test the platform. Each wallet is listed with Omen's other wallets, and from the day the pool opens none sells OMCADE for USDT. | Live |
| Fee-sized VIP epochs | After Phase III, each weekly VIP allocation is sized from the OMCADE fees collected that week: 3 points of the 15% fee from launch. Starting with the epoch of Monday 19 October 2026, 15% of each epoch goes into permanently locked liquidity, and VIP members receive the rest. 15% is the base share, and it may change as purchases grow, with public notice first. | At launch |
- Note 1. Any change to these is announced first, with notice.
- Note 2. Every release is an on-chain transfer, so circulation can be followed on BscScan from the wallets on the Contracts page.