# 90 — Glossary

The terms below recur throughout the case studies. We tried to keep them short. Where a term has a different sense outside this book, the book's sense takes precedence inside.

**Adversary.** The actor we model in the threat-model chapter — rational, capitalised, patient. Distinct from "attacker"; we use *adversary* for the modelled entity, *attacker* for a real person observed in a real incident.

**Conservation invariant.** A predicate stating that the sum of relevant balances is unchanged across a transaction or a sequence. The most common invariant we evaluate.

**Monotonicity invariant.** A predicate stating that a value moves only in one direction. Less common than conservation; useful for vault principals, lender debts, and burn-only token supplies.

**Concentrated liquidity.** An AMM design (Uniswap v3, Orca Whirlpools, Phoenix) where LPs supply liquidity within a price range rather than across the full curve. The substrate for both legitimate JIT activity and the attack in chapter 50.

**Critical / High / Medium / Low.** Severity buckets, defined in the threat model by USD-equivalent profit per attack. Inputs to triage; not absolute thresholds.

**Genetic fuzzer.** The search engine that drives the `fuzz` command. Population-based, with breeding and mutation; described in chapter 70.

**Governance griefing.** Use of a DAO's governance machinery to extract value from the DAO through asymmetric attention costs rather than through direct theft. Chapter 40.

**JIT liquidity.** *Just-in-time* liquidity: minting a concentrated AMM range immediately before a swap and burning it immediately after, to capture that swap's fee. Chapter 50.

**LP token.** *Liquidity-provider token*: a fungible token representing a pro-rata share of an AMM pool. Subject to dilution attacks (chapter 30) and to slippage at mint (chapter 20).

**Pyth.** A first-party oracle network on Solana, in which price publishers post prices directly. Used as the canonical example of a freshness-sensitive oracle in chapter 10.

**RPC endpoint.** A JSON-RPC server that proxies for the validator. The fuzzer issues read calls (`getProgramAccounts`, `getSlot`) to whichever endpoint is configured. Public endpoints rate-limit aggressively; we recommend a paid endpoint for any scenario that re-fetches state.

**Sandwich.** Three-transaction MEV pattern: front-run, victim, back-run. Chapter 20.

**Slippage parameter.** A user-supplied minimum acceptable output on a mint, burn, or swap. The standard mitigation against sandwiches and against share-dilution attacks.

**Staleness.** The lag between an oracle's last on-chain update and the current slot. Chapter 10 is built around the staleness window.

**TWAP.** *Time-weighted average price*: an aggregation of a price feed over a window. The most common mitigation against same-block manipulation. Discussed in chapter 30.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://economicfuzz.gitbook.io/economicfuzz-docs/reference/90-glossary.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.