Skip to content

Conversation

@Bennethxyz
Copy link

This PR adds a minimal radio networking module to exo.

What

  • RadioTransport abstraction with an in-memory LoopbackHub/LoopbackRadioTransport
  • RadioServer: handles a small JSON protocol to proxy Node operations over radio
  • RadioPeerHandle: sends prompts/tensors/results via RadioTransport
  • RadioDiscovery: loopback-based beaconing; serves as a reference for real radios

Why

  • Addresses [[BOUNTY - $200] Radio Networking Module #2] Radio Networking Module bounty. This provides the interfaces and a reference implementation to plug in real radio transports (LoRa, AX.25/KISS, etc.) without changing Node.

Notes

  • Backwards compatible: doesn’t alter existing gRPC/UDP/Tailscale modules
  • Next steps: implement a concrete LoRa/Serial transport and simple framing with retries/acks.

lone added 3 commits October 22, 2025 10:50
…-token overhead\n\n- Add async batch queues with short timeout and max batch size\n- Stack logits and call engine.sample once for the batch (with per-request fallback)\n- Forward sampled tokens and emit callbacks per-request\n\nThis is an incremental step toward full forward-pass batching as requested in exo-explore#1.
…pback transport\n\n- RadioTransport abstract interface + LoopbackHub/LoopbackRadioTransport\n- RadioServer handling minimal JSON protocol over radio\n- RadioPeerHandle for sending prompts/tensors/results over radio\n- RadioDiscovery skeleton (loopback-based beacons)\n\nThis provides a foundation for implementing real LoRa/AX.25 transports while matching exo’s Server/Discovery/PeerHandle interfaces (see exo-explore#2).
… to per-request\n\n- Prevent passing batched logits to TinygradDynamicShardInferenceEngine.sample\n- Safety check token count; fallback if mismatch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant