Summary

When all nodes for a specific coin (e.g., Dash, ADM) are disabled, the browser's debug console prints full error stack traces. This clutters the console, makes debugging harder, and exposes unnecessary internal details. Instead, a short, readable message should be shown.

Motivation

Developers and testers need clean and meaningful console output. Full stack traces for known and expected conditions (like all nodes being disabled) create noise, reduce clarity, and may cause confusion. Showing concise, human-readable messages helps distinguish between expected states and real issues, improving both development experience and debugging efficiency.

Detailed description

Steps to reproduce

1. Disable all the Dash nodes
2. Go to chat list
3. Open the browser's debug console
4. Go to a specific chat

Current behavior:

The console shows a full error stack trace:

index-LW_Nxjnd.js:354 t2: dash: All nodes are disabled
    at wwt.getNode (index-LW_Nxjnd.js:253:12460)
    at wwt.useClient (index-LW_Nxjnd.js:253:11890)
    at i6t._invoke (index-LW_Nxjnd.js:354:72989)
    at i6t.getBalance (index-LW_Nxjnd.js:354:72051)
    at Ps.handler (index-LW_Nxjnd.js:354:65572)
    at Array.<anonymous> (index-LW_Nxjnd.js:24:2530)
    at Ps.dispatch (index-LW_Nxjnd.js:24:10116)
    at Ps.dispatch (index-LW_Nxjnd.js:24:9086)
    at a.dispatch (index-LW_Nxjnd.js:24:1740)
    at s (index-LW_Nxjnd.js:354:65936)

The same issue occurs for other coins, including ADM.

Expected behavior:

• Do not display full error stack traces in the debug console when no coin nodes are available
• Catch the error and show readable info instead

Examples:

• DASH: All nodes are disabled
• If an action was performed: ADM: All nodes are disabled, Failed to fetch contact list

Screenshots or videos

Alternatives

No response

Proposed technical implementation

No response