$ the-wire · showcase
Gateways: v3 signing fixes connection, mDNS UI removed
By RepoJournal · Filed · About OpenClaw · Composed from the cited sources · methodology
![openclaw-docs-sync[bot]](https://avatars.githubusercontent.com/u/13697529?v=4)
The Windows node now speaks v3 signaling exclusively, fixing the most disruptive connection failures and removing the now-dead discovery UI.
The connection protocol in the Windows node now matches the reference implementation. The client uses SignConnectPayloadV3 instead of the legacy SignPayload/BuildDebugPayload, and the operator-4-mode signature cascade (V3Auth→V3Empty→V2Auth→V2Empty) is gone. "Signature rejection = real" means failures now surface as genuine errors instead of falling back to older auth modes [1]. This is a breaking change for any gateway that still expects v2 signatures.
The ConnectionPage UX was rebuilt, borrowing from node-2: a status card with a disconnect button and connection attempts counter, live decode preview for setup codes via manager.ApplySetupCodeAsync(), and a Recent Gateways card listing GatewayRegistry entries with connect/remove actions [2]. Available Gateways discovery is gone, along with the mDNS scan button and related code-behind (AutoScanAsync, PopulateGatewayList, OnConnectToGateway, OnConnectWithToken, OnCancelTokenPrompt). Gateway switching now flows through GatewayRegistry [3]. Pairing state no longer gets overwritten by disconnect events, so after the gateway sends PAIRING_REQUIRED and closes the socket, the UI stays on the Pairing screen [4].
The architecture wiring is also further along: SettingsChangeImpact classifier prevents reconnects for UI-only changes, DeviceIdentityStore persists tokens, SshTunnelManager.StartAsync is no longer a stub, and NodeConnector starts after operator handshake [5]. In openclaw, housekeeping removed the legacy cmd installer [6] and cleaned BlueBubbles references [7]. A new Telegram mantis evidence builder is in development [8], and auth default models were canonicalized [9].
Action items
- → Update any gateway or client that relies on v2 signature fallback to support v3-only auth openclaw/openclaw-windows-node [immediate]
- → Remove any UI flows or tests depending on the Available Gateways mDNS discovery section openclaw/openclaw-windows-node [plan]
References
- [1] Fix connection protocol: v3 signatures, remove cascade, structured errors ↗ openclaw/openclaw-windows-node
- [2] Upgrade ConnectionPage UX with manager integration ↗ openclaw/openclaw-windows-node
- [3] Remove Available Gateways discovery section from ConnectionPage ↗ openclaw/openclaw-windows-node
- [4] Fix pairing state: don't let disconnect overwrite PairingRequired ↗ openclaw/openclaw-windows-node
- [5] Wire connection architecture: settings classifier, identity store, node connector, per-gateway identity ↗ openclaw/openclaw-windows-node
- [6] chore(installer): remove legacy cmd installer ↗ openclaw/openclaw
- [7] chore(channels): remove bluebubbles hangover ↗ openclaw/openclaw
- [8] feat: add telegram mantis evidence builder ↗ openclaw/openclaw
- [9] fix(models): canonicalize auth default models ↗ openclaw/openclaw
