Devices that prove where they are
- Problem
- Signed proof of physical presence that nobody can fake.
- Built
- Rust firmware on ESP32-C6, radio lab research, signed proofs.
We find out which radio gives the accuracy your product needs and how each unit behaves. In our own hardware lab we test Wi-Fi FTM/RTT, Wi-Fi CSI, UWB, BLE, LTE and mmWave radar, each against a written acceptance plan, then carry the option that passes into Rust firmware with per-device calibration, and sign what the device reports so nobody can fake it later.
| Radios | Wi-Fi FTM/RTT · Wi-Fi CSI · UWB · BLE · LTE · mmWave |
|---|---|
| Tested | in our own hardware lab, against a written acceptance plan |
| Models | pose and activity on mmWave point clouds |
| Evidence | Ed25519 on every message |
How a project runs
| Radio choice | Wi-Fi RTT, UWB, BLE, LTE, mmWave radar and Wi-Fi CSI, each tested against a written acceptance plan, plus the hardware specification and procurement. | |
|---|---|---|
| Ranging accuracy | Wi-Fi FTM ranging on ESP32-C6 with a seven-step accuracy pipeline, live tuning over MQTT and per-device calibration, because every unit behaves a little differently. | |
| Machine learning on sensor data | Pose and activity models trained on mmWave point clouds, and occupancy heatmaps. | |
| Phone signals and sensor fusion | A mobile app that collects radio signals and sensor data on native Android and iOS, so a position is backed by more than one source and judged against how the device moved before. | |
| Signed evidence | Ed25519 on every message and signed multi-party proofs with witness quorums, with relay, Sybil, replay and clock skew attacks mapped to a control before code was written. | |
| From signal to record | Signed evidence from devices through verifiers and a witness quorum to a blockchain record, so nobody can fake where a device was. |
Stack
Proof
FAQ
It depends on the accuracy your product needs and how your devices behave. We test the candidates (Wi-Fi FTM/RTT, UWB, BLE, LTE, mmWave radar, Wi-Fi CSI) against a written acceptance plan before the design goes into firmware.
Yes. We test radios and sensors in our own hardware lab, each against a written acceptance plan.
Radio ranging is noisy and every unit behaves a little differently, so each device gets its own calibration and can be tuned live.
Not if the evidence is signed and confirmed by others. We use Ed25519 on every message and witness quorums, and map relay, Sybil, replay and clock skew attacks to a control before writing code.
Related
Our team owns the research and the engineering of your system.
DirectionRust firmware, radios, sensors and signed device data.
TechnologyFTM, CSI and IEEE 802.11bf: what they can and cannot do.
Guide802.15.4z, Bluetooth Channel Sounding, RSSI and Wi-Fi RTT compared.
GuideNext step
A 30 minute call with Mykhailo. You leave with a clear view of scope, risks and next step.
Mykhailo Tiutin
CTO, Vareger
