# Relay Monitor Deployment Notes

Notes below are for a POC / demo of the relay monitor with [expanded features](https://hackmd.io/@andriidski/B1IPW-Cln) deployed on [Sepolia](https://sepolia.dev).

Short recorded demo of what the Relay Monitor Website looks like, deployed on Sepolia and monitoring the Flashbots Sepolia Relay and a Faulty Relay -- https://share.cleanshot.com/Lr7YD2Sc

### URLs

* Relay Monitor Website
* https://sepolia.rm.mev.software
* Relay Monitor API
* https://sepolia.api.rm.mev.software
* Relay Monitor API Spec
* https://spec.rm.mev.software
* Faulty Relay/Builder to demonstrate monitoring by Relay Monitor
* https://builder-relay-sepolia.rm.mev.software
* Note: no website UI since this just mimics the bid delivery

### Setup

- 1x Beacon Node
- Lighthouse currently
- To support `getWithdrawals()` the custom fork is needed. See [here](https://flashbots.notion.site/MEV-Boost-Capella-Upgrades-00cea01704794f6eb4f792c55b69c441) for more context
- 1x Relay Monitor service
- Docker image built from [this](https://github.com/ralexstokes/relay-monitor/pull/49) PR
- 1x Relay Monitor website service
- Same docker image as Relay Monitor "monitor" process
- 1x Relay Monitor "fuzzer"
- Simulates a Faulty Relay/Builder that the monitor then monitors
- Code is here https://github.com/andriidski/relay-monitor-fuzzer
- Docker image built from latest `main`
- Configured to return faulty bids every once in a while, e.g. invalid timestamp or PREVRANDAO
- 1x PostgresDB service
- The spec repo is deployed via GH pages
- Code is here https://github.com/andriidski/relay-monitor-specs