Why not using #Reticulum a well worked out network stack and build network protocol extensions and fancy apps on it, instead of reinventing the wheel.
https://reticulum.network/manual/zen.html
Thanks for pointing it out. This is the first time I'm reading about it.
It seems Zen is about moving data across unreliable networks and making sure messages can get through without infrastructure, but seems to avoid defining what those messages mean, who is allowed to send them, how they should be ordered, or how shared history should work.
2WAY does all that too, by defining how state is validated, authorized, ordered, and shared so different parties can converge on the same result without relying on transport behavior or application-level convention.
It seems Zen is about moving data across unreliable networks and making sure messages can get through without infrastructure, but seems to avoid defining what those messages mean, who is allowed to send them, how they should be ordered, or how shared history should work.
2WAY does all that too, by defining how state is validated, authorized, ordered, and shared so different parties can converge on the same result without relying on transport behavior or application-level convention.