# Relay
**What is Relay?**
Relay is Blockops' ecosystem intelligence engine—a centralized command center that monitors the entire Web3 landscape so you don't have to. Think of it as your dedicated research analyst that never sleeps, constantly scanning official protocol channels, developer repositories, and authoritative news sources to surface what actually matters.
The platform aggregates high-signal information into two dedicated streams:
* **Release Updates:** Technical client releases and protocol upgrades.
* **Ecosystem Updates:** Strategic news, governance changes, and market-moving events.
Instead of monitoring dozens of Discord servers, GitHub repositories, and Twitter accounts, Relay consolidates everything into a single, filterable feed with proactive alert capabilities.
**The Problem Relay Solves**
**Real-world scenario:** You're running Ethereum validators using Prysm. The client releases a critical security patch at 2 AM. Without Relay, you might not notice until your next routine check—potentially exposing you to slashing or missed attestations. With Relay, you get an immediate Slack notification with a direct link to release notes and checksums.
| Pain Point | How Relay Addresses It |
| ----------------------------- | ---------------------------------------------------------------------------------------------- |
| **Information Fragmentation** | Centralizes critical updates scattered across 60+ protocol channels, forums, and social media. |
| **Missed Hard Forks** | Alerts node operators to mandatory client upgrades, preventing slashing or downtime. |
| **Reactive Security** | Provides instant notifications about exploits or vulnerabilities before assets are at risk. |
| **Noise Overload** | Filters out crypto Twitter hype to find substantive, verified protocol developments. |
| **Manual Monitoring** | Saves teams hours of daily manual tracking across multiple ecosystems. |
### How to Get Started
**1. Navigate to Relay** From anywhere in the Blockops dashboard, locate **Relay** in the left sidebar under the Products section. The Relay interface loads with a brief "Hold on" state, then presents the main dashboard with two primary tabs.
**2. Understand the Dashboard Layout** Once loaded, the Relay interface presents three key zones:
| Zone | Location | Purpose |
| --------------------------- | ---------- | ----------------------------------------------------- |
| **Content Stream Toggle** | Top center | Switch between Release Updates and Ecosystem Updates. |
| **Filter Panel** | Left side | Refine feeds by specific networks and clients. |
| **Subscription Management** | Top right | Configure proactive alerts (Email/Slack). |
**3. Configure Your Network Filters** Before diving into content, set up your filters to ensure relevance. Click the "All Networks" dropdown in the Filter panel. A searchable dropdown appears listing 60+ supported networks.
Select the networks relevant to your operations. If you only operate Ethereum and Polygon nodes, filtering out 58 other networks eliminates noise and surfaces only actionable intelligence.
* *Pro tip: Use the search box and type "Eth" to quickly find Ethereum rather than scrolling through the alphabetical list.*
**4. Explore Release Updates (For Node Operators)** Click the **Release updates** tab to view software releases for blockchain clients. When releases exist for your selected networks, each card displays the client name, network tag, release version, date, and direct links to view the changelog or download the patch.
If you see a "No releases" state, it indicates there are no new releases in the selected timeframe for your filtered networks. Broaden your network filter to "All Networks" to verify the feed is working, then narrow it back down.
**5. Explore Ecosystem Updates (For Strategic Awareness)** Click the **Ecosystem updates** tab to view curated news and announcements. Each card contains the source publication, a network badge, the headline, date, and a direct link to the full article.
*Example Entries:*
* **Security Alert:** "U.S. Treasury Sanctions Russian Exploit Broker" (Bitcoin Magazine) — *Indicates potential address blacklisting affecting transaction privacy tools.*
* **Protocol Governance:** "Winding Down the Official Polkadot Support" (Web3 Foundation Blog) — *Signals transition to decentralized governance.*
* **Technical Roadmap:** "Building Fair Markets: A New Consensus" (Aptos Labs Blog) — *Major consensus upgrade affecting validator requirements.*
### Completion: Set Up Proactive Alerts
Manual checking creates vulnerability windows. Configuring alerts is the final step to maintaining continuous awareness without keeping the dashboard open.
1. Click the **Manage subscription** button (bell icon) in the top-right corner.
2. **Choose Your Channels:** Select Email (best for detailed digests) or Slack (best for team coordination).
3. **Configure Granularity:** Select specific networks and set the Priority Level (e.g., "High Priority" for security patches and hard forks only).
4. **Test Your Configuration:** Send a test notification to verify channel connectivity.
*Expected outcome:* You will receive a confirmation message in your selected channel reading: *"Successfully subscribed to Relay alerts for \[Network]."*
### Best Practices & Troubleshooting
**Establishing Your Daily Workflow**
*For Node Operators & DevOps:*
| Time | Action | Location in Relay |
| ------------------- | ----------------------------------------------- | ----------------------------- |
| **Morning standup** | Check Release Updates for overnight releases | Release updates tab |
| **Weekly** | Review Ecosystem Updates for governance changes | Ecosystem updates tab |
| **Alert received** | Immediate action—verify checksum, plan upgrade | Direct from notification link |
*For Founders & Researchers:*
| Time | Action | Location in Relay |
| ----------- | ----------------------------------------- | ----------------------------- |
| **Daily** | Scan Ecosystem Updates headlines | Ecosystem updates tab |
| **Weekly** | Deep-dive into 2-3 strategic articles | Expand cards for full content |
| **Monthly** | Audit alert relevance—add/remove networks | Manage subscription |
**Troubleshooting Red Flags**
| Symptom | Diagnosis | Fix |
| -------------------------------- | -------------------------------------- | --------------------------------------- |
| **"No releases" always showing** | Network filter too narrow or incorrect | Expand to "All Networks" to verify feed |
| **Too many irrelevant alerts** | Subscription too broad | Narrow to specific networks |
| **Missing critical updates** | Priority filter set too high | Include "Standard" priority for patches |
| **Alert fatigue** | No priority filtering | Switch to "High Priority" only |
{
{% hint style="info" %}
[**Follow us on Twitter**](https://twitter.com/blockopsnetwork) **for more information on upcoming protocols and developments.**
{% endhint %}
---
# 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.blockops.network/developer/products/relay.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.