White paper
The endpoint addressing layer: self-describing variable-depth ternary coordinates, stateless O(1) vector forwarding in transit, and session state sharded to the ingress/egress sector only.
The address field is not a fixed integer burned into silicon. A 2-bit depth header opens every packet: 00 carries a 4-byte coordinate, 01 carries 8 bytes, 10 carries 12. An old node parses the flag and forwards without understanding the wider field, so the namespace can grow from thousands of endpoints to 3^36 (about 1.5 x 10^17) without a protocol break.
The routing plane is stateless: a relay reads the target coordinate, subtracts its own, and forwards in the direction of the vector difference. Memory use is a fixed register frame regardless of network size.
The state plane is sharded: session tokens, exit envelopes and last-seen records live only at the origin and destination sectors, bounded to roughly 5,000-10,000 local endpoints — about 320 KB, inside ESP32 SRAM.
Kademlia and IPFS map endpoints onto random logical hashes and maintain O(log N) remote buckets per node, with constant churn. Tri-Star addresses are packed physical coordinates: no announce storms, no global table, and the carrier (LoRa, CB audio, BLE, Reticulum, UDP) is interchangeable.
Forwarding latency, stack high-water marks, 10^4-entry sector tables, spatial-void recovery and exit-token replay resistance are proposed embodiments until measured on real multi-node silicon. No figure in the specification is yet a published result.
Published summary of an attorney-review draft or engineering record — not a filing, not a patentability opinion, not a safety certification. Engine parameters, signing keys and customer records never appear in any published paper.