Goose Finance
Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.
Goose Finance is a legacy BSC exchange, farm and vault system whose published farm list uses paired LP tokens and whose measured vault adapter resolves deposited stake tokens as LP inventory. The 2026-08-16 survey measured about $0.27M. Auto-compounding and EGG or Goose Dollar rewards do not remove the adverse reserve conversion inside the LP, so the version-1 AMM-LP dossier controls. The legacy app and vault API are no longer reachable, an additional lifecycle warning rather than a reason to relax the class rule.
- Ships a product line without impermanent-loss exposure that merits its own review
The research file
Mechanism applicability
Goose describes itself as a BSC exchange and yield farm. Its published farm configuration includes EGG-BUSD, EGG-BNB, BNB-BUSD, USDT-BUSD, BTCB-BNB, ETH-BNB, DAI-BUSD, USDC-BUSD and other LP receipts. The Goose Vault separately auto-compounds farm yield. Depositing those receipts leaves the client exposed to swaps changing the paired reserve mix while emissions and compounding add yield on top.
Control and exit applicability
The official contract map identifies a timelock, MasterChef, layer chefs, Goose Bank and Vault Chef. A depositor controls the LP or vault receipt, while Goose and underlying AMM contracts execute reward, strategy and reserve accounting. Exit depends on strategy operation, available pool liquidity, slippage, token quality and BSC settlement and returns the LP composition then held, not a guaranteed original token mix.
Current observation and lifecycle
The DefiLlama API read on 2026-08-16 classified Goose Finance as a Farm and reported approximately $0.27M on BSC. Its adapter reads current wantLockedTotal values from cached strategy addresses and resolves the stake tokens as possible LPs. The former app URL is absent from the survey record and the vault configuration API did not resolve during review, so the measurement supports residual on-chain balances but not a live supported user lifecycle.
Why the class rule decides
The protocol-specific evidence establishes that the measured Goose product family is built around farm and vault positions in paired liquidity. Rewards, harvesting cadence, timelocks and residual TVL do not eliminate adverse rebalancing. Reopen only for a separately measured, currently supported Goose product whose payoff and exit do not depend on pooled market-making inventory.
Sources
The claims above trace to these. Where a number could not be independently verified, the thesis says so.
- Goose Finance Docs — protocol and farm identity · primary · accessed 2026-08-16
Supports: BSC deployment, exchange identity, yield farming, timelock, migrator removal - Goose Finance Docs — Goose Vault · primary · accessed 2026-08-16
Supports: yield optimizer, auto-compounding, Goose Dollar rewards, vault perimeter - Goose Finance GitHub — published farm configuration · primary · accessed 2026-08-16
Supports: paired LP tokens, farm assets, BSC addresses, product mechanism - Goose Finance Docs — deployed contracts · primary · accessed 2026-08-16
Supports: timelock, MasterChef, Vault Chef, contract control perimeter - DefiLlama — Goose Finance survey record · secondary · accessed 2026-08-16
Supports: current TVL, BSC perimeter, Farm category, missing application URL - DefiLlama adapter — Goose vault accounting · secondary · accessed 2026-08-16
Supports: strategy addresses, wantLockedTotal, stake tokens, LP resolution, cached configuration dependency
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. |