On this page
OMNI incentive contracts
The incentive package is separate from the deployed Omniasset bridge, OFT representations, Omnilink, Morpho markets, and ERC-4626 vault accounting.
| Contract | Responsibility |
|---|---|
OmniVotingEscrow | Locks OMNI and returns non-transferable, linearly decaying veOMNI power. |
OmniGaugeController | Verifies vaults, records epoch votes, reserves budgets, and distributes emissions. |
OmniVaultGaugeFactory | Creates one gauge for an approved vault token. |
OmniVaultGauge | Escrows vault shares and streams OMNI pro rata. |
Deployment state
These contracts are implemented and tested, but they are not deployed. OMNI is unset and all token-dependent functionality is inactive.
The contracts support deployment before OMNI launches. The controller can set the token once, verify initial gauges, and activate locking, staking, voting, and emissions separately.
Core accounting
The escrow calculates voting power from locked amount and remaining duration. One account has one lock, so the same principal cannot produce a second voting balance.
Votes always target the next epoch and replace the voter's earlier allocation for that epoch. A lock must remain valid through the target epoch.
The controller keeps protocol emission reserves separate from externally sponsored reserves. Finalization snapshots eligible votes and stores each gauge's allocation before rewards are transferred.
Each vault gauge uses a cumulative reward-per-staked-share index. Organic vault yield is not part of that calculation.
Safety properties
- OMNI cannot be recovered from the voting escrow.
- Staked vault shares and OMNI cannot be recovered from a gauge.
- OMNI and registered vault tokens cannot be recovered from the controller.
- Expired OMNI locks remain withdrawable during ordinary activity pauses.
- Deprecated and removed gauges keep the share-withdrawal path open.
- A special withdrawal pause is limited to 24 hours with a seven-day cooldown.
- Stopping a gauge preserves accrued rewards and returns only unvested emissions.
The controller uses two-step ownership transfer for a later multisig, timelock, or governance migration. A production deployment still requires an independent security review and a published address record.