MyKAI Node 0.4.4 — Know your node is working
A one-click, two-way check that proves your node is reachable both ways — plus a node that lists itself on the public map automatically, faster connections on startup, and a quieter setup with fewer permission prompts.
What's new
"Is my node working?" — now there's one clear answer
A new Check hub connection in Settings → Network runs a direct two-way test with MyKAI's hub node:
- You reached the network — your node is connected and contributing.
- The network reached you back — other nodes can actually connect to you (you're publicly reachable).
Two green checks means your node is fully live — the single clearest answer to "is everything actually working?" It runs automatically the moment your node finishes syncing (no button to hunt for), and it remembers the last successful result with a date and time, so you can glance and know exactly when it was last confirmed.
Your node puts itself on the public map
Public nodes are now added to the public Kaspa map (kaspa.stream) automatically — once per launch, quietly in the background, with no clicks and no pop-up window. Your node shows up for other operators on its own. You can still add it manually any time, and you can switch the automatic listing off in Settings → Network. (Reachable nodes get picked up by the network's crawlers within a few hours regardless, so you're never left off the map.)
Faster, more reliable connection on startup
Your node now links into the network immediately when it launches, instead of waiting on the slower, gossip-based discovery process. Fresh nodes and nodes behind a home router get connected — and visible to peers — much sooner.
Smarter reachability for VPN & manual-IP setups
If your node was advertising the wrong address to peers — common after a VPN exit-server change or an ISP IP renewal — the reachability check now catches the mismatch and points you straight to the fix (re-detect and apply your current external IP). Auto-update-on-VPN-change keeps the advertised address current as you switch servers.
A quieter setup — fewer permission prompts
Fresh installs now handle the firewall rule, clock auto-sync, and antivirus exclusion during installation — right when you've already approved the installer. For most people the one-click setup opens with everything already done and no extra Windows permission pop-ups. (A third-party antivirus like Bitdefender still needs an exclusion only you can add — no app can edit another AV's settings — but MyKAI walks you through it step by step.)
Cloud & always-on stability
Fixed a reconnect race that could make headless / cloud nodes restart in a loop. Always-on nodes now run uninterrupted and report telemetry reliably.
Public-map cleanup
The old automatic submission to nodes.kaspa.ws was retired — that endpoint broke when the service moved to kaspa.stream and was logging repeated errors. The new automatic listing above rides the live map page directly, so it keeps working through the operator's changes.
Still Toccata-ready
Your node stays on Kaspa 2.0.0 (Toccata), ready for the network's June 30 hard fork. If you're on an older bundled node, updating now keeps you from falling behind the upgraded network.
Auto-update behavior
If you're on any 0.3.x or 0.4.x version, MyKAI will detect this update on next launch and prompt you to restart. Your data, settings, account key, and node identity are all preserved — and your synced chain data carries over, so there's no full re-sync.
If auto-update doesn't pick it up, download the installer below and run it over your existing install.