---
description: Learn how to monitor and trigger rebalance and liquidation operations
---

# Understanding the Keeper in f(x) Protocol

### Introduction

In DeFi, a Keeper is an entity or system responsible for _automating on-chain actions_ that cannot execute themselves. Since smart contracts on blockchains are passive, they require an external trigger—this is where Keepers come in.

While f(x) is a fully on-chain system, the Keeper is designed to actively monitor positions and initiate actions once certain conditions are met.

Maintaining an active Keeper community is critical for the f(x) Protocol. Therefore, we’ve written this document to help you understand some key concepts and processes related to Keepers.

### Related contract addresses



* PoolManager(Long): `0x250893CA4Ba5d05626C785e8da758026928FCD24`
* WBTC Long Pool: `0xAB709e26Fa6B0A30c119D8c55B887DeD24952473`
* wstETH Long Pool: `0x6Ecfa38FeE8a5277B91eFdA204c235814F0122E8`
* ShortPoolManager: `0xaCDc0AB51178d0Ae8F70c1EAd7d3cF5421FDd66D`
* wstETH Short Pool: `0x25707b9e6690B52C60aE6744d711cf9C1dFC1876`
* WBTC Short Pool: `0xA0cC8162c523998856D59065fAa254F87D20A5b0`
* fxETH(wstETH CreditNote): `0x7c5350BaC0eB97F86A366Ee4F9619a560480F05A`
* fxBTC(WBTC CreditNote): `0xB25a554033C59e33e48c5dc05A7192Fb1bbDdfc6`

You can double-check the contracts for the last update on [Github](https://github.com/AladdinDAO/fx-protocol-contracts/tree/main/ignition/deployments)
