Hey r/SideProject! I'm an independent systems architect working on Jumping VPN and the Veil Routing Protocol (VRP). The project started with a question: Why should losing a network path mean losing the logical session? Think about switching between Wi-Fi and mobile networks, NAT rebinding, unstable routes, or temporary connectivity failures. My approach is continuity-first: SESSION ≠ TRANSPORT. The logical session is treated as the primary unit, while the underlying transport can change. I've been building and testing the experimental runtime in Go on Linux, with a focus on: - Session continuity and recovery - Replay rejection - Deterministic authority decisions - Concurrency and adversarial testing - Reproducible validation evidence I've also published a validation kit so other developers can examine the publicly available tests and evidence without access to the proprietary core. GitHub: https://github.com/Endless33/vrp-validation-kit This is independent R&D, not a claim that every networking problem has been solved. Production-scale validation is still a separate challenge. I'd genuinely appreciate feedback from developers working on networking, distributed systems, VPNs, or infrastructure reliability. What failure scenario would you test first to challenge a continuity-first protocol? I'm especially interested in the cases where this approach might break.   submitted by   /u/Melodic_Reception_24 [link]   [comments]