Blocknative websocket warning

[0xSzeth]

Blocknative logs a warning in the console that the Websocket connection is closed before the connection is established. In this particular example, the warning occurs at line 226 in the web3enabled.ts file, which is where is initialize the instance of bnc-notify and is within the connect() function.

McFly thinks this is causing our app to prevent the loading of data.

Potentially related to the double-load of most pages on init?

[0xSzeth]

The issue appears to happen intermittently. Will continue to track for now.

[0xSzeth]

Here's another example where the warning occurs at a different point in the stack. Specifically at line 159 in the web3enabled.ts file, which is where the notify instance is configured. In blocknative's documentation, it says if networkID is passed as a configuration all other wss connections will be closed. Maybe this is causing an issue?

https://docs.blocknative.com/notify#config

[0xSzeth]

Every time we fetch an asset price from Chainlink price feeds we're call readonlyweb3() to get a new instance of Web3. Is calling this for every asset price causing the previous connection to break, and therefore the warning? What if we just passed an instance of Web3, calling it a single time from the parent component, vs creating a new Web3 instance every time we fetch a price?

I suppose we could take this even further and just instantiate a new version of Web3 once for the entire application on Init and pass that down to child components as necessary.

[0xSzeth]

From the Blocknative discord server: