Skip to content

Runtime v0.0.62

Latest

Choose a tag to compare

@mmalmi mmalmi released this 14 Nov 00:38
Immutable release. Only release title and notes can be modified.

Bounded discovery toward offline peers, and run-time preferred WebRTC peers for an application's own devices.

  • Core ports native FIPS's lookup limits: after a lookup times out, fresh lookups for that target wait 30 s, doubling to 300 s; transit nodes forward lookups for one target at most every 2 s. A new peer, changed tree coordinates, or a session with the target clears the wait.
  • WebRTC auto-connect waits 30 minutes after five consecutive failed dials to one peer, resets on a newer advert, connection or recovered signaling, ignores failures while the node has no working link, and dials adverts that missed their refresh last.
  • WebRtcTransport.setPreferredAutoConnectPeers replaces preferred peers at run time. They match by identity in either key parity, are dialed first, and back off from 1 s to 30 s without the 30-minute wait.

In a 16-node in-memory mesh, dialing one dead advert for an hour fell from about 10.6 MB to 0.22 MB of lookup traffic. Wire formats are unchanged. Verified with 316 core, 114 WebRTC, 14 WebSocket, 6 Memory and 6 Ethernet tests on the pinned toolchain; Rust bridge lookup interop passed, with one pre-existing routed-session bridge failure recorded in build-provenance.json.

Browser, device, public-network and live idle-traffic acceptance remain with consumers.