fix: use correct websocket URL scheme (wss://) in hub configurations#1432
Merged
artemijspavlovs merged 1 commit intomainfrom Dec 29, 2025
Merged
fix: use correct websocket URL scheme (wss://) in hub configurations#1432artemijspavlovs merged 1 commit intomainfrom
artemijspavlovs merged 1 commit intomainfrom
Conversation
The WsUrl fields were incorrectly configured with https:// scheme instead of wss:// (or ws:// for localhost). This caused WebSocket-based transaction monitoring to fail immediately when attempting to connect. Fixes part of #1414 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
WsUrlfields in hub configurations to use proper WebSocket schemeshttps://→wss://for secure WebSocket connectionshttp://→ws://for localhostContext
Part of fix for #1414 ("roller reports tx failure, while it actually passed")
The
WsUrlfields were incorrectly configured with HTTP(S) schemes instead of WebSocket schemes. This caused the CometBFT WebSocket client to fail immediately when attempting to connect, as it expectedws://orwss://URLs.Changes
https://dymension.api.onfinality.io:443/public-wswss://dymension.api.onfinality.io:443/public-wshttps://rpc-blumbus.mzonder.com:443wss://rpc-blumbus.mzonder.com:443http://localhost:36657ws://localhost:36657https://rpc-dymension-playground35.mzonder.com:443wss://rpc-dymension-playground35.mzonder.com:443Test plan
🤖 Generated with Claude Code