# Changelog Roundup for October 19, 2026

> Only a node's own key or a device approval in the portal can now change who a node counts toward. Also this week, ISPs detected automatically, cleaner leaderboards, a new router check, and repeat deploys of unchanged sites.

Published: October 19, 2026 · Author: John Federico · Category: Updates · Tags: roundup, changelog

Source: https://blog.evolvingedge.ai/post/changelog-roundup-2026-10-19/

The most important change this week is a security fix for node operators: no one but you can now set who your node counts toward. For customers, deploying a site that hasn't changed no longer fails.

## For node operators

[Only you can determine who owns your node](https://changelog.evolvingedge.ai/2026/10/node-owner-set-only-by-node/). Until now, a credential issued for one node could set the owner of a different node, so a node could end up counted toward someone who didn't run it. That affected whose profile, leaderboard placement and referral progress it counted toward, and whose earnings it would count toward once payouts begin. From 13 October, an existing node's owner changes only under that node's own key or through a device approval in the portal. Any other owner change is accepted but ignored. The fix doesn't check whether the gap was used before then. If your node runs under an ID other than the one it enrolled with, it keeps its current owner. To move it to someone else, approve the device again in the portal. Otherwise, you need to do nothing.

[Your node's ISP is now detected from its connection, not your entry](https://changelog.evolvingedge.ai/2026/10/isp-detected-from-connection/). The Hardware & Connection form in the portal no longer asks for your ISP. Your node's page, the metro leaderboard, and your operator profile show the ISP your node's network belongs to, and any ISP you typed in earlier has been replaced with what's been detected. This ensures that two spellings of the same provider now show as one name. If your network isn't in our list yet, you'll see a dash. Private profiles still hide the ISP on leaderboards.

[Operators with no check-in for 7 days are now removed from every leaderboard](https://changelog.evolvingedge.ai/2026/10/inactive-operators-leave-leaderboards/). Metro leaderboards, the Top 5 and the Community page's metro top 5 kept listing operators whose nodes had gone quiet. Now only nodes that have actually checked in within the last 7 days appear on a board. Registering again doesn't count. On a metro leaderboard each node is judged on its own, and rank trends follow the same rule. If your node has been offline, bring it back: it returns to the boards when they next refresh, which happens every hour.

[Your node now finds the first router on your ISP's network](https://changelog.evolvingedge.ai/2026/10/nodes-find-first-isp-router/). From v0.0.117 onward, your node looks for the first router outside your home network, at most once an hour and in the background, never during a visitor's request. It reports that one hop, about 120 bytes, with its next check-in. Nodes behind the same router go offline together if the router fails, so we use this only to see which nodes share a point of failure, never for eligibility, rankings, earnings or where sites are placed. It needs no administrator rights. If your node can't measure, it works exactly as before. You need to do nothing.

## For customers

[Deploying a site whose content hasn't changed no longer fails](https://changelog.evolvingedge.ai/2026/10/unchanged-sites-redeploy/). Re-running a deploy with nothing changed, for example a repeated CI job, used to be refused with `workload already exists with different bytes`, because each build recorded its build time in the package. The same files now produce the same package every time. Your first deploy of an unchanged site may still be refused once. Deploy any change and it's settled. **This covers Level 0 sites only: Level 1 and Level 2 sites are encrypted with a fresh secret on every build**, so an unchanged redeploy is still refused, and so are rollbacks. Both are known and not fixed yet. The command-line tool downloads the new builder for you, so you need to do nothing.

For everything else, see the [full changelog](https://changelog.evolvingedge.ai).