Add way of knowing whether websockets is enabled for RPC nodes about chain-registry HOT 1 OPEN

sunnya97 commented on May 27, 2024

Add way of knowing whether websockets is enabled for RPC nodes

from chain-registry.

Comments (1)

daniel-farina commented on May 27, 2024

This is more of a configuration parameter, one of many in the app.toml and I think it would make more sense for the application to test if websockets are enabled vs adding parameter in the chain-registry which might not even be accurate or up to date.

Also there is a websocket endpoint that hopefully it's not modified but in Javascript you can test by doing something like:

const ws = new WebSocket('ws://localhost:26657/websocket')

ws.onopen = function() {
  console.log('Connected to WebSocket endpoint')

  // Subscribe to new block events
  const subscribeMsg = JSON.stringify({
    jsonrpc: '2.0',
    id: '1',
    method: 'subscribe',
    params: {
      query: 'tm.event = \'NewBlock\''
    }
  })

  ws.send(subscribeMsg)
}

ws.onmessage = function(event) {
  const msg = JSON.parse(event.data)

  if (msg.result && msg.result.data && msg.result.data.value && msg.result.data.value.block) {
    const blockHeight = msg.result.data.value.block.header.height
    console.log(`New block height: ${blockHeight}`)
  }
}

ws.onclose = function(event) {
  console.log('WebSocket connection closed')
}

In bash you can use