Learning guide
DeFi Automation and Keeper Network Vocabulary
A practical glossary-style guide to keepers, oracle feeds, rebalance rules, risk parameters, and automation limits.
Vocabulary-first analysis, reviewed against primary references where they are listed. Read our editorial methodology.
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.
Applied reading
Understanding what happens when an automated job is late
A protocol may rely on an external actor to call a contract when a condition becomes true. If no caller arrives, the contract can remain unchanged even though the condition is visible on-chain. Keeper systems solve this coordination problem by monitoring conditions and submitting transactions.
Reliability depends on more than detecting the event. The caller needs funds, network access, correct gas settings, valid permissions, and enough incentive to act. Duplicate calls, chain reorganizations, congestion, and reverted transactions also need handling. Automation is therefore an operating system around a contract, not just a timer.
Concept boundaries
Terms that are easy to confuse
Trigger
The condition that makes a job eligible to run.
A true condition does not guarantee that a transaction will be submitted or confirmed.Keeper
An actor or service that monitors and executes eligible work.
The keeper initiates a transaction; the contract still enforces execution rules.Incentive
Payment or benefit offered for completing the job.
An incentive improves participation but does not guarantee timely or correct execution.Idempotency
Design that makes repeated execution safe or predictable.
It protects against duplicates, not against a permanently missed job.Knowledge check
Test the distinction, not the definition
Why can an on-chain condition remain unexecuted?
Most contracts cannot wake themselves; an external transaction must call the relevant function.
What should happen when two keepers submit the same job?
Contract logic should make duplicates harmless, reject stale work, or ensure only one valid result.
Why monitor confirmed outcomes instead of submitted transactions?
A submitted transaction can remain pending, be replaced, revert, or disappear during a reorganization.
Source trail
Primary references used for this guide
These references support the terminology and risk distinctions above. They are provided so readers can verify the underlying material.
FAQ
Is DeFi Automation and Keeper Network Vocabulary financial advice?
No. Crypto Term Game publishes educational vocabulary guides only. The site does not provide investment, tax, legal, trading, token, or product advice.
How should beginners use this guide?
Read the headings first, compare the related glossary terms, then play the daily board to practice grouping terms by function instead of memorizing isolated definitions.