Proven on real hardware
Dated, factual notes as TAWK moves from specification to running hardware. Short on adjectives, long on things that actually happened.
A message carried over the cellular network
A TAWK node joined a commercial cellular network and carried traffic across it end to end — the same messages, unchanged, that the mesh already moves over its own long-range radios. Cellular is not a dependency and never becomes one: it is simply one more path TAWK will use while it happens to be there, and step around the moment it is not.
Devices now choose their own path
A device with more than one radio picks between them per message, on its own — preferring a path it has real evidence is reachable, then one that can carry the message whole, then whichever worked most recently. Where two long-range modes have to share a single radio, the device schedules between them and meets its neighbours at an agreed time instead of talking over itself.
A second, independent implementation
Work began on a second implementation of TAWK, written in a different language to reach the small networking hardware the first one cannot. The two are held to the same wire format by a shared set of conformance vectors: both must produce byte-identical output, or the disagreement is a bug in one of them. Two independent implementations that agree is a far stronger claim about a protocol than any single codebase can make on its own.
A smaller message on the wire
The message header was reworked and is now close to a fifth smaller. On fast links that is invisible. On the slow, long-range, duty-limited radios — the ones that matter most once infrastructure is gone — a smaller header means more room for the message itself and less airtime spent at every hop.
Handhelds joined, and a self-built coordinator took over
A pocket-sized handheld with a screen and keyboard joined the mesh as a full participant. Separately, a coordinator assembled from ordinary commodity parts took over serving a site network from the purpose-built appliance bought for the job, and by casual observation outperformed it. Both point the same way: TAWK should never require anyone to buy particular hardware.
Time that survives a power cut
Devices now hold accurate time across a loss of power, and some take it straight from satellites. Ordinary messaging deliberately does not depend on a clock — that is what lets TAWK work in places where no clock can be trusted — but the features that genuinely need one, such as knowing when a stored message has aged out, now have a dependable source.
Cross-radio relay demonstrated end to end
A TAWK message originated on a device with only a long-range, low-power radio and was delivered to a device with only a different radio type entirely — crossing three radio technologies through two independent relay devices. Every relay in the chain handled the message blind: able to pass it along, unable to read it. This is the first end-to-end demonstration of TAWK’s transport-agnostic relay on physical hardware, and it worked exactly the way the specification says it should.
The full protocol on low-cost embedded hardware
The complete TAWK node — routing, message envelopes, multi-hop relay — now runs on the class of inexpensive, battery-friendly microcontrollers used in consumer electronics, across three different board families. One device demonstrated bridging two radios at once, relaying between networks while participating in both.
A cleaner post-quantum core
The cryptographic core was migrated to a fully self-contained implementation of the NIST-standardized post-quantum algorithms. The same codebase now builds for every processor family TAWK targets, with an extensive interoperability test suite passing on all of them. Work has also begun on hardware-accelerated coordinator configurations — the path to the independently validated, higher-assurance tiers described in the configurations.
Coordinator load testing
The coordinator design was load-tested across a fleet of machines, sustaining message volumes far beyond what any of the deployments described on this site would generate — on a single commodity computer. Detailed figures will be published after the current patent and export-review process completes.
TAWK is patent pending. Some technical detail is deliberately withheld while filings and export-control review are in process. If your evaluation needs specifics, get in touch: consulting@ckservicesllc.com.