> For the complete documentation index, see [llms.txt](https://chain-love.gitbook.io/chain.loves-performance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://chain-love.gitbook.io/chain.loves-performance/monitoring/how-it-works.md).

# How it works?

The majority of up to date information can be find in our [Whitepaper](https://chain-love.gitbook.io/chain-love-docs/whitepaper#monitoring-operator) in the Monitoring section.

Essentially, Chain.Love is a part of EigenLayer ecosystem (so called [AVS](https://docs.eigencloud.xyz/eigenlayer/developers/concepts/avs-developer-guide)). 

<figure><img src="/files/mXPcm9EWRxTe3F2F5uzt" alt=""><figcaption></figcaption></figure>

AVS is connected with a set of Operators who represent independent entities [financially motivated](https://docs.eigencloud.xyz/eigenlayer/concepts/rewards/rewards-concept) to execute certain tasks, in Chain.Love's case - validate the health statuses of the API endpoints.

They report their fundings on-chain where then the consensus mechanism is being executed by Chain.Love's relayer to made a majority-influenced decision on whether the provider is up or not. Then, anyone is able independently verify why certain decision was made.