# How it works?

The majority of up to date information can be find in our [Whitepaper](https://app.gitbook.com/s/PWuDHqT5CRbrc5eu4gbw/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="https://3120590109-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzHukEzyKtop3oVU5Uj2y%2Fuploads%2F4UoVsJgps9C8WJW0cmMC%2Fimage.png?alt=media&#x26;token=058a38bc-0ecd-4917-a75a-12eb2dddee8e" 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.