Learning guide
DeFi Automation and Keeper Network Vocabulary
A practical glossary-style guide to keepers, oracle feeds, rebalance rules, risk parameters, and automation limits.
Automation is market plumbing
DeFi automation can include keepers, bots, schedulers, or services that call protocol functions when certain conditions are met. The vocabulary often describes maintenance tasks rather than user-facing trading ideas.
A keeper might update a price, trigger a liquidation, rebalance a vault, execute a queued operation, or call a function that keeps a system within its designed rules.
Oracles and triggers
An oracle feed supplies outside data, often a price or rate. A heartbeat can describe how often a feed updates. A deviation threshold can define how much a value must move before an update is expected.
Automation depends on triggers. If the trigger is stale, delayed, or manipulated, the automated action can be wrong even when the code runs exactly as written.
Risk parameters are not predictions
A risk parameter is a setting used by a protocol or system, such as a collateral factor, liquidation threshold, fee, delay, or cap. It describes how the system behaves under defined conditions.
These settings are sometimes changed through governance or administrator processes. Learning the terms helps readers understand documentation without treating the parameter as investment advice.
How this appears in the game
Keeper bot, oracle feed, heartbeat, deviation threshold, rebalance rule, and risk parameter terms often group around automation infrastructure.
The game uses those groups to teach how DeFi systems are maintained. It does not recommend automated strategies or protocol usage.