Network

Pipes↑ Why · Alex reaches the laptop at home from a café Alex gets through from any network that allows the web, and directly where the network lets it.

A pipe is a stream or a datagram channel, and only the relay WebSocket is required

Every other way through is an optimisation.

A direct pipe's certificate hash or fingerprint arrives sealed

Whoever relays the offer must not be able to stand in the middle.

Where the network allows, a session moves onto a direct pipe by itself

The relay is the floor, not the way: a direct pipe is quicker, and carries nothing through anyone else.

When no direct pipe can be made, or one drops, the relay carries on

A network that blocks UDP, or a NAT nothing gets through, costs speed and nothing else.

Anything that forwards sees only `{to, ciphertext}`↑ Why · Someone checks every claim before trusting it What a relay sees is checked byte by byte in a test anyone can run.

Relays are the part someone else may run.

Sessions↑ Why · Alex loses a phone, and it opens nothing A stolen phone can't stand in for another key, or read what it recorded.

Sessions are mutually authenticated by node key

A key is the address; no certificate authority or DNS is trusted.

Key exchange is hybrid X25519 + ML-KEM-768

Traffic recorded today must not open to a quantum computer later.

Every signed or sealed thing names its algorithm

Algorithms change without breaking old data.

The chain is verified once per session, and its end ends the session

A hybrid chain is 3.5 KB and doubled call latency in the spike.

Lost packets and network changes↑ Why · Alex reaches the laptop at home from a café The café wifi drops, the hotspot takes over, and Alex's shell carries on.

A session survives a pipe change with nothing lost, nothing repeated and no handshake

Networks flap; a handshake per flap is slow and a lost keystroke is wrong.

A pipe that dies in silence is noticed within seconds, and calls in flight finish

A network that drops without closing the socket leaves it looking open, and everything sent into it is lost while the page says all is well.

Messages are numbered and sealed one by one, with a key per direction

A message must open on whichever pipe it arrives, and a nonce must never repeat.

Datagrams are never resent and pass a replay window

A late video frame is worthless; a replayed one is an attack.

#Pipes↑ Why · Alex reaches the laptop at home from a café Alex gets through from any network that allows the web, and directly where the network lets it.

#A pipe is a stream or a datagram channel, and only the relay WebSocket is requiredproof

#A direct pipe's certificate hash or fingerprint arrives sealedproof

#Where the network allows, a session moves onto a direct pipe by itselfproof

#When no direct pipe can be made, or one drops, the relay carries onproof

#Anything that forwards sees only {to, ciphertext}proof↑ Why · Someone checks every claim before trusting it What a relay sees is checked byte by byte in a test anyone can run.

#Sessions↑ Why · Alex loses a phone, and it opens nothing A stolen phone can't stand in for another key, or read what it recorded.

#Sessions are mutually authenticated by node keyproof

#Key exchange is hybrid X25519 + ML-KEM-768proof

#Every signed or sealed thing names its algorithmproof

#The chain is verified once per session, and its end ends the sessionproof

#Lost packets and network changes↑ Why · Alex reaches the laptop at home from a café The café wifi drops, the hotspot takes over, and Alex's shell carries on.

#A session survives a pipe change with nothing lost, nothing repeated and no handshakeproof

#A pipe that dies in silence is noticed within seconds, and calls in flight finishproof

#Messages are numbered and sealed one by one, with a key per directionproof

#Datagrams are never resent and pass a replay windowproof