Verify meta not found

Code

NETWORK/VERIFY_META_NOT_FOUND

What it means

The connection flow is missing required verification metadata (token/address/etc.), so the client/server cannot authenticate the WebSocket connection.

When it happens

• The client/server is missing required verification metadata for a WS connection (e.g. token/address).

Typical scenarios:

• Client did not call the “get world route” API before connecting
• Route fetch failed and the app continued anyway
• Local state was cleared but UI still tries to connect

How to handle

• Treat as a client state/integration error.
• Re-fetch world route (host/token/address) and reconnect.