The WalletConnect relay protocol is the transport layer that routes encrypted messages between wallets and dapps. Governance over which relay implementations are officially supported, recommended, or deprecated directly affects every connection in the ecosystem. This page tracks the decision-making process, authority, and timelines that determine relay protocol selection—from the legacy centralized bridge to decentralized relay networks—and the operational consequences for infrastructure operators, wallet providers, and dapp teams that depend on message delivery guarantees.
Protocols
Relay Protocol Selection and Deprecation Governance
Tracks governance decisions on which relay protocols are officially supported, recommended, or deprecated, including timelines for transitions from centralized bridges to decentralized relay networks. Critical for infrastructure operators managing message delivery dependencies.
introduction
RELAY GOVERNANCE
Introduction
How the WalletConnect ecosystem governs relay protocol selection, recommendation, and deprecation, and why infrastructure operators must track these decisions.
Relay governance decisions are not purely technical upgrades; they are operational directives with forced migration timelines. When the WalletConnect Foundation or Technical Steering Committee (TSC) deprecates a relay protocol, all clients must migrate to a supported alternative before the sunset date or risk connection failures. The transition from the centralized bridge to a decentralized relay network introduced new trust assumptions, latency profiles, and fallback behaviors that wallets and dapps must explicitly handle. Operators need to understand the decision-making authority, notice periods, and compatibility windows to plan infrastructure changes without service disruption.
For teams running production WalletConnect infrastructure, relay deprecation is a hard dependency risk. A missed migration deadline can break session establishment for an entire user base. Chainscore Labs can assess relay migration readiness, review fallback strategy implementations, and model the operational impact of relay protocol changes on your specific integration architecture.
RELAY PROTOCOL SELECTION AND DEPRECATION
Governance Snapshot
Governance decision areas that affect which relay protocols are supported, recommended, or deprecated, and the operational impact of those transitions.
| Area | What changes | Who is affected | Action |
|---|---|---|---|
Relay protocol selection | A new relay protocol is formally recommended or mandated for new client versions | Wallet developers, dapp SDK integrators | Review new relay spec for compatibility with existing session management and message delivery logic |
Relay protocol deprecation | An existing relay protocol is marked for deprecation with a mandatory sunset timeline | Node operators, wallet teams, exchange infrastructure | Audit active sessions and migrate to supported relay before the sunset date to avoid service disruption |
Centralized bridge sunset | The centralized bridge relay is deprecated in favor of a decentralized relay network | Infrastructure operators, high-availability wallet services | Assess decentralized relay latency, reliability, and fallback strategy; test message delivery under degraded conditions |
Relay fallback configuration | Governance defines the order and conditions for falling back between relay protocols | Multi-relay wallet implementations, dapp connection managers | Verify fallback logic matches the canonical governance decision to prevent session loss during relay outages |
Relay message size limits | Parameter changes to maximum message payload size per relay protocol | Dapp developers sending large transaction payloads, wallet UI teams | Test maximum payload scenarios against new limits; adjust dapp message chunking if required |
Relay rate limiting rules | New or adjusted rate limits per client or per session on a specific relay protocol | High-frequency dapps, notification services using Push API | Implement client-side throttling and backoff to match governance-mandated rate limits |
Relay privacy and encryption requirements | Governance mandates a minimum encryption standard or transport security for all relay protocols | Security teams, custodial wallet operators | Audit relay message encryption implementation against the new mandatory standard; remediate gaps |
Relay protocol removal | A previously deprecated relay protocol is removed from the official client and no longer supported | Long-running wallet instances, embedded devices with infrequent updates | Force-upgrade any client still using the removed relay to avoid permanent loss of wallet connectivity |
technical-context
INFRASTRUCTURE DEPENDENCY
Relay Architecture and Governance Scope
The relay network is the message delivery backbone for WalletConnect sessions, and its governance directly affects the security, availability, and decentralization of all wallet-dapp connections.
The WalletConnect relay protocol serves as the message-passing layer between wallets and dapps, abstracting transport away from the application logic defined in the Sign, Auth, and Push APIs. The current production relay is a centralized WebSocket-based message server operated by the WalletConnect Foundation, which handles session proposal, settlement, and request/response delivery. This architecture creates a critical dependency: every active WalletConnect session relies on the Foundation's infrastructure for message routing, making the relay's operational status, geographic distribution, and access-control policies a systemic risk factor for the entire ecosystem.
Governance over relay protocol selection and deprecation determines which message transport mechanisms are officially supported, recommended, or phased out. This includes decisions about transitioning from the centralized relay to a decentralized relay network (DRN), the adoption of alternative transports such as Waku or libp2p-based gossip protocols, and the timeline for sunsetting legacy relay endpoints. The relay parameter in session proposals and the relay API configuration in client SDKs are governed by specifications that the Technical Steering Committee (TSC) can amend, meaning a deprecation decision forces every wallet and dapp to update their client implementation or risk connection failures. Infrastructure operators must track these governance decisions to plan migration windows, test fallback relay configurations, and ensure their message delivery remains compliant with the latest protocol requirements.
The operational impact of relay governance extends beyond simple transport switching. A deprecation of the centralized relay without a fully production-ready decentralized alternative introduces a transition period where message delivery reliability, latency, and censorship resistance are in flux. Wallet developers need to assess whether their relay client supports the new transport, handle relay discovery and connection fallback logic, and maintain backward compatibility with peers that have not yet upgraded. Dapp operators must verify that their Web3Modal or direct SDK configurations point to supported relay endpoints. Chainscore Labs can assist teams with relay migration readiness reviews, fallback strategy design, and integration testing against proposed relay architectures to ensure uninterrupted session delivery during protocol transitions.
RELAY MIGRATION IMPACT
Affected Stakeholders
Wallet Operators
Wallet teams are the most directly affected by relay protocol changes. A deprecation of the centralized bridge in favor of a decentralized relay network requires immediate action to update SDK dependencies and connection logic.
Action items:
- Audit the current
relayconfiguration in your Web3Wallet SDK implementation. - Test session establishment and message delivery against the new relay endpoint in a staging environment.
- Monitor for increased latency or changed pairing behavior under the new relay topology.
- Update user-facing documentation if the connection flow changes.
Failure to migrate before a hard deprecation date will result in broken wallet connections for all users. Chainscore can perform a pre-migration audit of your relay integration and fallback logic.
implementation-impact
RELAY TRANSITION PLANNING
Operational Impact and Migration Requirements
Governance decisions on relay protocol selection directly affect the message delivery infrastructure for every connected wallet and dapp. Teams must plan for migration timelines, fallback strategies, and compatibility windows to avoid service disruption.
01
Client Compatibility and Version Support
Deprecation of a relay protocol requires all clients to support the successor protocol. Wallet and dapp operators must audit their SDK versions to confirm compatibility with newly mandated relay paths. Older client versions that lack support will fail to establish sessions, effectively breaking connectivity for users who have not upgraded. Teams should map their user base's version distribution against the deprecation timeline to quantify the impact of forced upgrades.
02
Centralized to Decentralized Relay Migration
A governance decision to deprecate the centralized bridge in favor of a decentralized relay network represents a fundamental shift in trust assumptions and network topology. Infrastructure operators must transition from maintaining a connection to a single bridge endpoint to participating in or connecting to a distributed network of relay nodes. This migration requires new operational runbooks, monitoring for peer discovery and message propagation, and a re-evaluation of latency and reliability guarantees.
03
Fallback Strategy and Dual-Write Periods
During a deprecation window, governance may mandate a dual-write period where clients publish messages to both the legacy and successor relay protocols. This operational requirement doubles the message delivery load and introduces complexity in deduplication and error handling. Teams must implement and test a fallback strategy that gracefully degrades if the new relay path fails, ensuring session continuity while the ecosystem transitions. The duration of this period is a critical governance parameter.
04
Monitoring and Observability for New Relay Paths
A relay protocol change invalidates existing monitoring for message delivery latency, success rates, and endpoint availability. Operators must deploy new observability tooling specific to the successor protocol's transport and topology. For a decentralized relay network, this means monitoring peer health, message gossip propagation, and network partition risks rather than a single bridge health check. Alerting thresholds must be recalibrated to avoid false positives during the transition.
05
Chainscore Migration Readiness Review
Chainscore Labs can assess your infrastructure's readiness for a relay protocol migration. Our review covers SDK version compatibility across your user base, dual-write implementation correctness, fallback logic resilience, and observability gaps for the new relay path. We deliver a prioritized remediation plan to ensure your service remains operational through the deprecation window and beyond.
RELAY TRANSITION EXPOSURE
Risk Matrix
Evaluates the operational, security, and integration risks introduced by governance decisions to select, recommend, or deprecate relay protocols within the WalletConnect infrastructure.
| Risk Area | Failure Mode | Severity | Affected Actors | Mitigation / Action |
|---|---|---|---|---|
Centralized Relay Deprecation | Mandatory deprecation of a centralized bridge with insufficient notice period causes a hard disconnect for wallets and dapps that have not migrated. | Critical | Wallet operators, dapp frontends, SDK integrators | Verify deprecation timelines against canonical governance announcements. Implement a fallback relay selection mechanism in the client. Chainscore can perform a migration readiness review. |
Decentralized Relay Instability | A newly recommended decentralized relay network experiences performance degradation or message loss under load, disrupting session reliability. | High | Infrastructure operators, high-frequency trading dapps, wallet UX teams | Monitor relay network performance metrics. Do not remove centralized relay support until decentralized options meet a defined SLA. Chainscore can model relay failure scenarios. |
Relay Selection Fragmentation | Governance fails to designate a clear default relay, leading wallets and dapps to select incompatible relay networks, causing connection failures. | Medium | Multi-chain wallet developers, dapp developers, end users | Adhere to the canonical relay registry. Implement clear error messaging for relay mismatch. Chainscore can audit multi-relay client logic for spec compliance. |
Governance Capture Risk | A single entity or small coalition influences the relay selection process to favor a relay network they control, introducing centralization and censorship risks. | High | Ecosystem participants, governance delegates, risk assessors | Scrutinize governance proposals for conflicts of interest. Demand transparent selection criteria. Chainscore can provide governance impact assessments for relay proposals. |
Cryptographic Suite Incompatibility | A new relay protocol mandates a cryptographic suite not yet supported by legacy wallets, preventing them from establishing sessions. | High | Legacy wallet maintainers, hardware wallet vendors, mobile SDK teams | Audit the cryptographic requirements of candidate relay protocols against your supported client matrix. Plan for phased rollout. Chainscore can review cryptographic transition impacts. |
Message Payload Limit Mismatch | A new relay enforces stricter message size limits than the deprecated one, causing silent failures for dapps sending large session payloads. | Medium | Dapp developers using complex transaction requests, identity proof flows | Test payload size limits against all recommended relays. Implement client-side message chunking or compression. Chainscore can validate payload handling across relay implementations. |
Session Migration Data Loss | During a forced relay migration, active session state is not preserved, requiring users to manually reconnect and re-authorize all sessions. | Medium | End users, wallet UX teams, customer support | Design session persistence logic that is relay-agnostic. Test migration paths in staging. Chainscore can review session migration implementations for data integrity. |
Unclear Deprecation Authority | Ambiguity in the governance charter about who can trigger a relay deprecation leads to a contested decision, delaying critical security patches. | High | Security teams, node operators, protocol maintainers | Clarify the decision-making authority for emergency deprecations. Monitor governance channels for disputes. Chainscore can analyze the deprecation policy governance for gaps. |
OPERATIONAL PREPAREDNESS
Relay Migration Readiness Checklist
A structured checklist for infrastructure operators, wallet teams, and dapp developers to validate readiness before a relay protocol transition or deprecation takes effect. Each item identifies what to verify, why it matters for session continuity, and the signal or artifact that confirms readiness.
What to check: Audit your production systems for any open pairing proposals, active subscriptions, or pending session requests that are still bound to the relay URL or protocol being deprecated.
Why it matters: Sessions cannot be transparently migrated between relay protocols. Any session still active on the deprecated relay will be severed when the relay is decommissioned, leading to silent failures for end users.
Readiness signal: You have a complete list of active session topics and pairing URIs that depend on the old relay, and you have a plan to either gracefully disconnect them or prompt users to re-establish sessions before the cutoff date.
resource-links
OFFICIAL SOURCES
Canonical Resources
Use these sources to verify WalletConnect relay protocol behavior, deprecation signals, CAIP dependencies, and operational readiness before changing wallet, dapp, or infrastructure integrations.
Chains We Build On
Looking to build on a specific blockchain?
We build smart contracts, DeFi applications, wallets, tokenization platforms, and blockchain infrastructure across the major ecosystems teams choose today. That includes Ethereum, Arbitrum, Optimism, Polygon, Avalanche, Solana, Sui, Aptos, Hedera, Stellar, and NEAR, with support for additional EVM and non-EVM networks based on your product requirements.
EVM ecosystems
- Ethereum
- Arbitrum
- Optimism
- Polygon
- Avalanche
- Cronos
Non-EVM ecosystems
- Solana
- Sui
- Aptos
- Hedera
- Stellar
- NEAR
Additional ecosystems
- Polkadot
- Cosmos
- TON
- Cardano
- Algorand
- Tempo
Also available for Base, appchains, custom EVM networks, and cross-chain product architecture.
RELAY GOVERNANCE FAQ
Frequently Asked Questions
Common operational and strategic questions about the governance process for selecting, supporting, and deprecating relay protocols within the WalletConnect ecosystem.
A new relay protocol is typically proposed through the WalletConnect Technical Steering Committee (TSC) or a dedicated WalletConnect Improvement Proposal (WCIP). The process requires:
- Specification Submission: A formal spec detailing the transport layer, message encoding, and security properties.
- Reference Implementation: A working implementation demonstrating compatibility with the core WalletConnect client libraries.
- Security Review: A public analysis of the relay's trust model, censorship resistance, and message integrity guarantees.
- TSC Ratification: A formal vote by the TSC to accept the relay as a supported transport.
Teams should verify the current status of any proposed relay against the canonical TSC meeting notes and the official WalletConnect specs repository. Do not assume a relay is production-ready until it appears in a stable client release.
Trusted by Industry Leaders
Delivering blockchain solutions for 5+ years.
We have partnered with 50+ leading DeFi protocols, NFT ecosystems, and fintech innovators to build secure, scalable, and capital-efficient blockchain products.
Selected Partners & Clients
“I've been working with Chainscore Labs for last 3+ years, they've consistently delivered with strong ownership across multiple projects. The team is reliable and detail-oriented.”
L
Lee Erswell
CEO, Telos Foundation
how to get started
How to get started?
If you're looking for blockchain integration, ChainScore Labs has 5+ years of experience helping teams build and integrate exchanges, wallets, smart contracts, tokenization solutions, and protocol-connected products, we can help you choose the right path, integrate securely, and get to production faster. Our team consists of experienced blockchain developers and architects who can help you with your blockchain integration needs.
01
Exploration & Strategy
Define your product goals and choose the right blockchain architecture for your use case.
02
Architecture & Design
Design the smart contracts, tokenomics, and security parameters of your system.
03
Development & Integration
Build and integrate with wallets, oracles, and front-end dApps for a seamless experience.
04
Security & Launch
Comprehensive audits followed by a risk-managed mainnet deployment to protect your users.
Explore More Solutions
Discover our
blockchain development services.
We build production-grade blockchain solutions for top-tier projects across DeFi and Web3.
Book a Call
Start a build
Need a blockchain engineering team?
Send the project context and we will respond with next steps, scope questions, and a practical path to delivery.