Le-Space

under evaluation

LoRa Mesh

We are testing LoRa mesh for commercial open-source applications — applications that keep working in parallel when the internet or the electricity grid fails, and in places that have neither.

For groups and communities that want to shrink their metadata footprint, a clear game-changer.

What we are testing right now

Stationary Chrome PWAs with Bluetooth LE that reconcile their data with mobile devices — peer to peer, over CRDTs (e.g. OrbitDB, Yjs), with no servers, no accounts and no passwords.

Where it would be used

  • Booking systems with little to no metadata and no tracking, for fitness and yoga studios.
  • Booking systems for coworking spaces with several locations.
  • P2P logistics: Alice in Hamburg sends a parcel to Munich — the system finds registered travellers who already cover the route, daily or spontaneously, by train or by car. Across several hops each hop only sees the meeting point and the handover time, only the last one the recipient's address — and every hop earns a reward.
  • P2P argument mapping for parties and civil-rights movements — democracy 2.0.

Conceivable, not built yet

Devices in branches that reconcile their data over WebRTC and over a LoRa mesh — whichever of the two happens to be there.

Libraries and demos this builds on

  • webrtc-qr — the library: two devices connect by scanning a code — no signalling server.
  • qr01 — the tutorial chapter for this: a todo list moves from phone to phone by scanning a code — over a Wi-Fi hotspot, with no internet involved.
  • ablage — a P2P dropbox between devices and people, no servers and no accounts — over webrtc-qr and libp2p.
  • yogasuci — an emerging showcase: booking yoga classes without middlemen, metadata or tracking.
  • design issue #161 — webrtc-qr lets two devices find each other by one reading the other's "call" as a QR code. This open discussion thinks through whether that call could travel over a LoRa radio mesh instead — through walls, across floors, to a counter with nobody standing at it — including what the radio's limits allow.

What is being planned right now

The courier over the mesh, as thought through in design issue #161 — in two variants. Bob walks in with phone and node, and the counter answers with nobody standing at it. Or a customer books their hairdresser appointment from home: the handshake travels by radio instead of through a signalling server, so no SaaS provider ever sees the metadata — and the appointment stands.

Sequence diagram: Bob’s phone signs a WebRTC offer, sends it over Bluetooth to his node, the LoRa mesh relays it to the node at the counter, the unattended tablet verifies the signature and answers over the same path; WebRTC then connects only where an IP path exists. Sequence diagram: Bob’s phone signs a WebRTC offer, sends it over Bluetooth to his node, the LoRa mesh relays it to the node at the counter, the unattended tablet verifies the signature and answers over the same path; WebRTC then connects only where an IP path exists.

Work on this with us

We are looking for tech partners, testers, investors and pilot customers — for applications that also work without the internet: as a fallback, exclusively offline, or as an option for people who would rather keep their data to themselves, with no metadata and no tracking. Booking systems for fitness and yoga studios or coworking spaces, for example.

Write to us — contact@le-space.de

On the mesh you can reach us at le-space.de e45c, YSGs0MrcH9QOcAlIxvYkJWaV64AvKgx/tXS27SiCzXM=

The key is the part that identifies us — node names are set by whoever owns the node. It radios in the EU-868 region and is often on the move, so it answers wherever it currently has a mesh in range.