BeaconTruth
Authenticated Bluetooth location beacons. Every advertisement is signed, counted, and verifiable — so a position report can be trusted, not just received.
The service
Enroll
Beacons arrive keyed from the factory — each issued its own master key over an authenticated, write-once channel. Adding one to an account is a scan; keys never travel in the clear.
Authenticate
Every packet carries the next link of a hash chain the beacon alone can produce. Forgeries and replays are rejected at the edge of the platform — with no shared secret anywhere in the system.
Locate
Resolved observations become trusted location data — with a rotating private address, so a beacon is identifiable only to whoever holds its published anchor.
One standard packet
Twenty-three bytes. The token is one link of a hash chain — the beacon holds a seed it never reveals and walks backwards along it, one link a minute, so hearing today's token tells you nothing about tomorrow's. The index says which link it is.
No device ID on the wire. Every beacon still has one — ten bytes, written as sixteen Crockford symbols and printed on the hardware — and its anchor is registered against it at commissioning. Binding the two once, there, is what lets the packet stop repeating it.
Verifying it is hashing forward until you reach the beacon's anchor, and the anchor is public: a hash that proves a beacon without letting anyone impersonate it. There is no key to steal here, and no key we hold either.
0001f0 ac7a549701 2d5638a4c1ab2301c81700 0bbe
Open by design
The packet format, the chain construction, and the registration protocol are specified in full — not reverse-engineered from a scanner. Every beacon's anchor is published in a signed registry, so you can verify a packet offline and never have to take our word for one.