If your tokenomics can be gamed, your protocol will be gamed, often without a novel Solidity bug.
Emission curves, vesting cliffs, gauge weights, points programs, and oracle-linked rebases are not "business logic beside the code." They are the code that decides who ends up with governance, liquidity, and the treasury. Attackers read the whitepaper the same way they read a contract: looking for paths where the incentives pay more than the cost of capital and risk.
This note is for founders and security leads who shipped a clean audit of the vault and still lost the plot in the incentive layer.
What "economic exploit" means here
We mean strategies that are valid under the rules as written and still break the product:
- Governance capture through emission or voting shortcuts
- Treasury or liquidity drains via incentive loops
- Oracle and rebase games that mint or unlock value early
- Vesting and unlock bugs that look like accounting errors until they are empty wallets
If the only finding language you accept is "unauthorized access," you will miss most of this class. The access was authorized. The design paid the attacker to use it.
Common surfaces we still see
### 1. Emission cliffs and governance capture
Large unlocks or concentrated emissions create windows where a motivated actor can buy influence, direct gauges, or pass parameter changes before distributed holders organize. The contract may enforce the schedule perfectly. The schedule itself is the vulnerability.
Ask: who can vote after the next unlock, and what can that vote move? Include delegated voting, ve-style locks, and "points" that later convert to tokens.
### 2. Vesting and unlock logic bugs
Cliff math, TGE exceptions, revocation paths, and merklized airdrops are recurring bug farms. Classic shapes:
- Unlock that can be called twice under different wrappers
- Revocation that does not stop a claimed-but-untransferred balance
- Admin rescue that bypasses the vesting schedule for "ops"
- Rounding that favors the claimant across many small calls
Treat vesting contracts with the same hostility as vaults. They move the same asset.
### 3. Liquidity incentive loops
Liquidity mining, bribes, and reflex booster mechanics can be looped until the treasury or the emissions budget is the exit liquidity. On-chain, each step looks fine. In aggregate, honest LPs are paying a mercenary cohort that leaves when the subsidy ends, often with the governance token overhang still to clear.
Model the loop with adversarial capital, not with the happy-path spreadsheet.
### 4. Oracle-dependent rebasing and pricing
Rebasing tokens, algorithmic supply changes, and collateral factors tied to spot oracles invite:
- Short-term price manipulation around rebase or funding events
- Circular dependency (token price depends on pool that depends on token incentives)
- Liquidation cascades when the "fair" price is a thin market
If supply or solvency reads an oracle, the oracle is part of tokenomics. Price it in the threat model.
### 5. Hidden admin and exception paths
"Emergency" mint, discretionary emissions, whitelist mints for partners, and upgradeable token logic are tokenomics. They rarely appear in the investor one-pager. They always appear in the incident report.
List every path that can change supply, transferability, or voting power outside the public schedule.
A practical review boundary
When we scope tokenomics as attack surface, we force:
- Supply map — genesis, emissions, unlocks, burns, admin mints; who can change each
- Time map — cliffs, cliffs-after-TGE, voting delays, bribe epochs
- Governance link — how token weight becomes parameter power
- Incentive loops — LP, borrow, points, referrals; profitable adversarial strategies
- Oracle and pricing links — what supply or solvency functions read
- Exception paths — pause, blacklist, rescue, upgrade, discretionary allocate
If any row is "tokenomics consultants signed off," it still needs an adversarial read against the deployed contracts and configs.
Closing note
A protocol can be memory-safe, reentrancy-guarded, and still insolvent by design.
Review the schedule and the incentives with the same seriousness as the vault math. The market already does.
AN3 Intel · field notes on DeFi economic risk.