Docs
How it works
Login. Publish. Dial. Wallet, dest-map, galaxy relay, CryptKey.
1. Login as a point
Connect a web3 wallet (Frame on localhost, or --browser for MetaMask / Rabby). Pick an Azimuth ID you own. Azimov rederives the networking CryptKey from the wallet when that matches what is on-chain. If keys were never set, it writes them. If they miss, it confirms a reset — that increments life — unless you pass --yes.
A master ticket (az login --ticket) or a key from a running ship (az bind) stores the same key.
2. Your name goes on the map
Your planet tells its sponsor galaxy where it lives. Peers look you up on that dest-map. The map is how ~you becomes a reachable endpoint without exchanging a file. It answers where. It does not admit anyone.
Most galaxies are not live yet. If the sponsor is dark, the node falls back to nut.relay.azimov.network.
3. Connect privately
Direct when it can. A galaxy carries the rest (relay). Encryption is WireGuard. The data plane is a kernel TUN: utun on macOS, az0 on Linux. Opening it needs an administrator (root, or CAP_NET_ADMIN on Linux).
Each peer is one /128 in fd00:1776::/64 and one galaxy-assigned /32 in 10.176.0.0/16. The interface does not take the default route. LAN and the overlay stay on the ordinary gateway. Public traffic can leave through a friend: exit. Reachability is ping6 to that address. az ping reports the magicsock path.
Inbound starts closed. az mesh add puts a point on pending. They accept, and a member can reach this node’s overlay address. Mesh answers whether. az mesh secret is optional privacy; default dests still publish the roster.
The OS has the address. An installed peer answers on the kernel interface as zod and zod.azimov.network. A pending peer does not. ~zod is not a label. az ssh still takes ~you. Userspace mode does not install the resolver. Running a galaxy: galaxy.