# Relay Monitoring ### Monitoring relays In addition to monitoring the beacon node api for validators subscribed to our pool, we monitor the relays for updated 'validator\_registration'. By monitoring this, we're able to catch any changes made to the fee recipient address. For this reason, we're requiring the use of mevboost by all validators subscribed to the pool. If the protocol does not recognize that a validator is registered with the relay, or that the latest validator registration returned is associated with an incorrect fee recipient, that validator will be excluded from rewards cycles until the fee recipient is updated. The advantages for requiring MEV boost are: 1. Higher rewards for pool members. 2. Helps us detect quickly the change of a validators `feeRecipient` through the relay registration. Registration with one of the following 6 relays is required to be included in the rewards cycle. More relays will be added as their api responses become reliable. ``` 'https://boost-relay.flashbots.net', 'https://relay.ultrasound.money', 'https://aestus.live', 'https://agnostic-relay.net', 'https://mainnet-relay.securerpc.com', 'https://bloxroute.max-profit.blxrbdn.com' ``` ### Check relay api before subscribing to the pool Want to verify your relay registration before joining the pool? Easy-peasy, just copy and past the url of the relay you're using into your browser and input the public key associated with your validator. ``` https://boost-relay.flashbots.net/relay/v1/data/validator_registration?pubkey=YOUR_PUBLIC_KEY ``` ``` https://relay.ultrasound.money/relay/v1/data/validator_registration?pubkey=YOUR_PUBLIC_KEY ``` ``` https://aestus.live/relay/v1/data/validator_registration?pubkey=YOUR_PUBLIC_KEY ``` ``` https://agnostic-relay.net/relay/v1/data/validator_registration?pubkey=YOUR_PUBLIC_KEY ``` ``` https://mainnet-relay.securerpc.com/relay/v1/data/validator_registration?pubkey=YOUR_PUBLIC_KEY ``` ``` https://bloxroute.max-profit.blxrbdn.com/relay/v1/data/validator_registration?pubkey=YOUR_PUBLIC_KEY ``` --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.smoothly.money/relay-monitoring.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.