Introduction to Chainlink Keepers
Chainlink Keepers is in beta. We're continuing to test the network with users and improve the experience based on your needs. Please reach out to firstname.lastname@example.org with any feedback.
A major limitation of smart contracts is that they can't trigger or initiate their own functions at arbitrary times or under arbitrary conditions. State change will only occur when a transaction is initiated by another account (such as user, oracle, or contract).
To solve this problem, blockchain projects can:
- Create highly reliable infrastructure trigger smart contract functions - centralized and expensive to build/maintain,
- Outsource it to a 3rd party - often centralized and a single point of failure
- Use an open market solution - decentralized, but can come with complex incentive alignment, the potential for competitive bots that increase the cost of execution, and difficulties ensuring reliability
- Use the Chainlink Keeper Network
Chainlink Keepers provide users with a decentralized network of nodes that are incentivized to perform all registered jobs (Upkeeps) without competing with one another, allowing you to focus on critical smart contract functionality. Learn how the network works.
An example Decentralized Finance (DeFi) use would be to detect the fulfillment of a condition that triggers the execution of trades. Tasks like this generally can't be automated on-chain and must be handled by an off-chain service due to smart contracts' inability to self-execute.
The Chainlink Keeper Network is a decentralized solution where independent Keeper nodes are incentivized to check and perform Upkeep correctly.
Supported Blockchain Networks
Chainlink Keepers are currently available on Kovan and ETH mainnet. If you are interested in using Keepers but need it on a different blockchain or network, please reach out to us and let us know.
Making sure your Upkeeps execute when you expect
Our goal is to ensure flawless execution of your Upkeeps. To get the most out of Chainlink Keepers, we recommend you review these docs in full - understand their capabilities, usage patterns, best practices, and how to maintain the health of your upkeep.
We strongly recommend to start by testing your Keeper-compatible contracts on testnet before moving to mainnet. At any point during your testing process, please reach out to us if you have questions that have not been addressed, or take a look at our Keepers Frequently Asked Questions.
- Create a Keeper compatible contract
- Deploy your contract onto a supported testnet
- Get LINK on the testnet
- Register your Upkeep on testnet
- Test, iterate, and finalize your Keeper compatible contract
- Deploy your fully tested contract onto mainnet
- Register your Upkeep on mainnet
- Fund your upkeep on mainnet
- Confirm the first performance of your Upkeep
️ Open Beta Note
Your registrations on testnet will be auto approved immediately. To help us streamline the process of onboarding your use case on mainnet, please fill out the optional details (and form) during testnet registration so our onboarding team can expect your use case on mainnet. Mainnet registrations will be reviewed by our onboarding team before being approved. We are working towards a fully self-serve model.
|› Making Keeper Compatible Contracts|