[dhaavi]

Geographical: No enforcement, but if you choose the wrong country, packets will have issues reaching you, because routing is "bucketed" into layers of regions. Routers only hold the bext x routes to each bucket.

Transport is custom in order to support source routing, but I use the WireGuard library for setting up the interface and such.

(I have experience with cryptography in network protocols from Safing/SPN - the cryptography of which was audited without fault. Also, I am _very_ cautious and keep to standards as close as possible.)

[irq-1]

Cities with significant internet POPs would be better than countries. 1. You control the list of locations (so Singapore not Brunei.) 2. People can easily choose from a list of cities. 3. Latency tests could make it a non-issue. 4. Local connections in semi-isolated areas (think antarctic or islands in the south pacific) can be identified by people with a config.

[dhaavi]

Interesting idea - thanks! Will think about this more.

[evbogue]

Maybe there's a way to offset this risk by testing the speed of connections?

How does peer discovery work? Where do the region buckets live?

[dhaavi]

Latency is considered in routing.

Every router announces itself on the network. Routers can optionally publish their IANA IP addresses.

Buckets live on the routers themselves.