Wompie
Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.
Wompie is Magpie’s Wombat-focused yield layer: the measured contracts hold Wombat pool deposit tokens through WombatPoolHelper integrations while Magpie’s locked WOM boosts the rewards paid to depositors. The 2026-08-16 survey measured about $0.75M across BSC and Arbitrum, excluding separately reported Magpie staking. Boosting and compounding do not change the client’s underlying claim on Wombat trading-pool inventory, so the version-1 AMM-LP dossier is dispositive before size or incentive quality.
- Ships a separately measured product whose return does not depend on Wombat liquidity-pool inventory
The research file
Mechanism applicability
Magpie documents a direct Wombat integration and accumulation of WOM to obtain veWOM voting power and boost Wombat yields. The survey adapter enumerates registered MasterMagpie pools, resolves each WombatPoolHelper deposit token and counts those tokens held for the product. The investable return therefore begins with Wombat pool inventory; mWOM, WOM voting power and MGP incentives sit above rather than replace that LP claim.
Control and exit applicability
Pool composition and Wombat contract behavior determine the assets and value available beneath each receipt, while Magpie contracts, its Wombat multisig relationship and reward routing add another control layer. Magpie itself warns that users inherit Wombat Exchange risk through the direct integration. A client exit depends on unwinding the helper and underlying pool at the then-current inventory and liquidity, not a promise to return the contributed token at par.
Current observation and perimeter
The DefiLlama API read on 2026-08-16 classified Wompie as Yield and reported approximately $0.75M: $0.74M on Binance and $0.01M on Arbitrum. It separately reported approximately $0.41M of staking. This record maps Binance to BSC and covers the measured Wombat-linked deposit positions, not standalone MGP, vlMGP or mWOM staking.
Why the class rule decides
Client yield remains contingent on assets committed to Wombat liquidity pools and exposed to trade-driven inventory changes, token divergence, depeg, contract and removal risk. Reward boosting can increase compensation but cannot remove that transformation. The version-1 AMM-LP dossier therefore controls; reopen only for a separately measured Wompie product whose return is not generated from Wombat pool inventory.
Sources
The claims above trace to these. Where a number could not be independently verified, the thesis says so.
- Magpie Docs — ecosystem and Wombat integration · primary · accessed 2026-08-16
Supports: Wompie, Wombat, SubDAO, yield boosting - Magpie Docs — veWOM governance position · primary · accessed 2026-08-16
Supports: veWOM, Wombat voting power, reward direction - Magpie Docs — deployed contracts and multisigs · primary · accessed 2026-08-16
Supports: MasterMagpie, BSC, Arbitrum, Magpie Wombat multisig - Magpie Docs — direct-integration risk disclosure · primary · accessed 2026-08-16
Supports: Wombat dependency, smart-contract risk, loss risk - DefiLlama adapter — Magpie and WombatPoolHelper accounting · secondary · accessed 2026-08-16
Supports: deposit tokens, WombatPoolHelper, MasterMagpie, chain accounting - DefiLlama — Wompie survey record · secondary · accessed 2026-08-16
Supports: current TVL, BSC, Arbitrum, separate staking
Inherited controls
The verdict above grades the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The least safe layer sets the position’s grade, and the position table names which one that is.
| Chain | Verdict | Grade | Control constraint |
|---|---|---|---|
| BNB Smart Chain | Rejected | freezable | the validator set concentrates around one company, and the chain has been halted by decision. |
| Arbitrum One | Approved · limits | hybrid | a single sequencer orders >99% of transactions and admin keys can upgrade bridge contracts on a ~7-day timelock. |