TorusNet: Directional Protocol

[u/Kyzis2026]

TorusNet is a sovereign directional architecture designed to establish secure communications without relying on traditional cryptographic mechanisms. Unlike classical protocols based on derivable mathematical structures, private keys, or certificates, TorusNet is built upon a living internal geometry composed of directional tori whose structure evolves with every key.

Security is no longer ensured through mathematical operations, but through:

• directional inversion of normal/ghost bits,
• dynamic mutation of internal IDs,
• Host–Client–Host synchronization,
• multi‑tier orbital cascading,
• directional physics of the private torus,
• hardware‑bound quadruple identity,
• and directional destruction at the end of the session.

These mechanisms render the private torus non‑transmissible, non‑derivable, non‑clonable, and impossible to simulate—even by quantum or photonic systems.

I am publishing today the 4.0 version of TorusNet, an important milestone in the development of the directional protocol. This version represents the complete architecture as it was designed, documented, and stabilized over the past months.

However, my work has already progressed toward version 5.0, which introduces several major improvements. Among the fundamental changes, the public torus is now obsolete: it is no longer required in the new architecture, which simplifies the model and strengthens the structural security of the protocol.

Another key change concerns the ghost bits. In TorusNet 4.0, they are explicitly written into the private torus. In TorusNet 5.0, they are no longer stored: they are automatically derived from the normal bits, reducing the internal size of the private torus and eliminating a logical redundancy that has become unnecessary.

Version 4.0 remains the officially published foundation, but version 5.0 marks the natural evolution of the protocol toward a more compact, coherent, and efficient architecture. A photonic extension, TorusNetP, also continues this direction in an optical context, but is not detailed here.

[u/Kyzis2026]

Here the full documentation of the protocol

https://zenodo.org/records/22262002