COM — Communications
Cross-Home signed messaging. One substrate (Ed25519-signed JSON), multiple transports. Trusted Peers, Broadband Gateway, and Sneakernet (USB carry) are functional; LoRa/Meshtastic is hardware-ready (see the Mesh section); Satellite lights up last.
Compose
PRIMARYChoose a send method; the message is signed and routed accordingly. Existing per-transport composers below remain available for reference.
Send method
MEDIUM
TRUST
Recipient
Direct: signed envelope POSTed to the peer's gateway.
Inbox
0 messages
No messages yet. Once a peer sends you something, it appears here.
Trusted Peers (HTTPS gateway under the hood)
FUNCTIONAL
Both Homes online, fast, internet-dependent. Recipient resolves from your trust ring.
Signs a
message/v1 envelope with your device sub-key, POSTs it
to the peer's registered gateway URL, received via
/api/comms/gateway/receive on the other end. Carries a plain-text
body (≤1MB), sender pubkey, recipient pubkey, and signature. Attachments use a
separate path.
Send to a peer in your trust ring
No peers in trust ring yet. Add one via
POST /api/peers.
Broadband Gateway (ad-hoc URL)
FUNCTIONAL
Reach a peer whose URL you know directly (you supply the destination).
Same protocol + envelope as Trusted Peers, but you provide the URL instead
of picking from your ring — useful for ad-hoc known URLs. The recipient still
verifies your signature against THEIR trust ring: they only accept your
message if you're already on their list.
Send to a URL you trust
Your gateway is at
http://127.0.0.1:58773/api/comms/gateway/receive.
Share this URL with peers who need to reach you.
LoRa Mesh (Meshtastic)
SEE RADIO PANEL BELOW
Off-grid messaging over LoRa radio — no internet, no carrier.
Range ~5–15 km line-of-sight, slow (~kbps). Your Meshtastic radio
(T-Beam / Heltec) connects over USB serial; the same Ed25519-signed
envelope rides the mesh, fragmented across packets and reassembled +
verified on the other Home. Practical body ~10KB due to fragmentation —
conversation events fit, large attachments don't.
Device status:
use the Radio panel below to connect
Privacy note: raw LoRa is broadcast — readable
by anyone in range, and Meshtastic's built-in channel key is a
weak shared secret. Presence witness is the live LoRa
capability; sealed message-carrying over mesh is available as
an experimental opt-in in the Radio panel below (content is
E2E-encrypted above the radio; traffic analysis is not hidden).
To connect: use the RADIO — LoRa mesh panel further down
this page — plug in your Meshtastic radio, pick the port, and
Connect. Enabling Broadcast Presence turns this from
presence-only into live off-grid presence.
WiFi Mesh (LAN, no radio)
READY
HOME-to-HOME messaging on your local network — no radio, no internet.
The common case: two Homes on the same WiFi/LAN. Same Ed25519-signed,
end-to-end-encrypted envelope as LoRa — the encryption rides above the
transport, so content privacy is identical; the LAN just moves the
ciphertext. Send an encrypted message directly to a peer Home's LAN
address; content is E2E-encrypted to the recipient (home2v).
Sovereign by construction: LAN-only (rejects non-RFC1918
addresses in code — never an internet POST), explicit-peer only (no
broadcast), trusted-ring peers only. Residual: a passive LAN observer
sees sender/timing/size; content is encrypted, traffic analysis is not.
To send: pick WiFi mesh (LAN) in Compose with a validated peer set.
Mesh Presence-Witness (presence only, live)
GATED
Signed evidence a subject was within LoRa range at time T — proximity, no message content.
A peer's signed announcement that a subject was within LoRa radio range at a
time T is a presence witness — evidence of proximity, no carrier or
internet. Presence only: no message content rides (the schema is closed +
byte-capped). Message-carrying mesh is the separate section above.
Self-attested presence is graded BELOW peer-witnessed (a signed self-claim
isn't independent corroboration).
Privacy: presence announcements broadcast
UNENCRYPTED over RF. Anyone with a radio in range can hear them.
The gate defaults OFF; nothing transmits until you open it.
checking…
Transport: mock.
Real LoRa hardware (T-Beam/Heltec) drops in at the same seam.
Self-attested presence is graded BELOW peer-witnessed (a signed
self-claim is not independent corroboration).
Sneakernet (USB carry, live)
LIVE
The most sovereign transport: zero network. Sign → save to USB → carry → import + verify.
Sign a message into a bundle, save it to USB, physically carry it to the other
Home, import + verify there. The Ed25519 signature is what makes
carrying-by-hand trustworthy — a tampered bundle fails verification.
Satellite (Iridium SBD)
MODEM?
At sea or truly remote, off every network. Plug a 9602/9603 SBD
modem (e.g. RockBlock) into a serial port, point HOM3 at it, and
send the smallest signed event headers over the Iridium network.
Starlink is just internet -- use the Broadband Gateway for that.
SBD carries up to 340 bytes per message -- HOM3 sends event
HEADERS, never bodies (the chain lives offline anyway). Delivery
costs Iridium credits, takes seconds to minutes, needs sky view,
and is best-effort: marked unconfirmed unless the modem reports a
success session. The driver speaks the modem's AT command set
directly -- no vendor SDK, same lean approach as the LoRa link.
Outbox
0 pending · 0 retrying · 0 failed
Retry policy: 30s → 1min → 5min → 30min → 2hr → 12hr → mark delivery_failed.
After 24h elapsed since first attempt, give up. Failed messages stay
in this list for you to manually retry or cancel.
The delivery worker runs this schedule
automatically; under airgap each attempt fails cleanly and the
message waits for the egress door rather than being dropped.
Outbox is empty.