Yggdrasil Mesh Node VPS Hosting

Yggdrasil builds an end-to-end encrypted IPv6 mesh on top of any underlying network transport. Each node has a public key, and the lower 16 bytes of the SHA-512 of that key become the node's IPv6 address in the 200 colon colon slash 7 range. Routing uses a spanning tree with cryptographic verification, and traffic between any two nodes is encrypted with the recipient's public key without any need for a key exchange handshake. The result is an overlay network where the IP address is the public key, which simplifies authentication and removes the need for separate TLS or VPN tunneling for most applications.

The network bootstraps through public peers. New nodes connect to one or more public peers from the community-maintained list, and from there they participate in the spanning tree and can reach any other node in the mesh. Public peers therefore play a load-bearing role: if there were only a few of them, network reliability and latency would degrade. Adding a high-uptime offshore VPS to the public peer list is one of the most direct ways to strengthen the network for end users in your region.

Yggdrasil is bandwidth-efficient and CPU-modest. A 1 Gbps VPS can serve hundreds of simultaneous peers without breaking a sweat. The entry-tier offshore plan is more than enough for a contributing public peer, and the geographic placement matters more than the spec sheet. A public peer in a region that is currently under-served by the community list adds disproportionate value compared with adding another peer in a region that already has dozens.

Yggdrasil installs from prebuilt packages on Debian, Ubuntu, Arch and most other modern distributions. The config file is generated on first run and includes the node's private key, listening addresses, peer list and multicast settings. For a public peer the relevant changes are to set Listen to a public TCP or QUIC endpoint, advertise that endpoint on the community public peer list, and disable multicast discovery on the public interface to avoid responding to scanning probes from arbitrary IPv6 hosts.

The node's identity is the public key. Operators who want to publish a stable public peer endpoint should generate the key once, back up the config file to an offline encrypted volume and avoid rotating the key unless the private side is suspected of compromise. Rotating the key changes the IPv6 address and breaks any existing peer relationships that target the old key. This is the same operational discipline as running a Tor relay with a stable fingerprint.

Latency and packet loss matter more for public peers than absolute throughput. A peer that occasionally drops connections is worse than a slower peer that stays up. AnubizHost offshore nodes are placed in datacenters with low jitter and direct uplinks to major IXPs, which keeps the spanning tree stable and minimizes routing churn. Routing churn in Yggdrasil propagates network-wide, so a flapping public peer is a network-wide annoyance and operators should treat uptime as a first-class priority.

Yggdrasil traffic is end-to-end encrypted and the public peer cannot decrypt traffic it forwards. Operator privacy still matters because the public peer endpoint is observable on the clearnet IP that the VPS uses. AnubizHost accepts BTC, ETH, XMR and USDT with no KYC at signup. The billing record contains only the account email and the transaction hash. Operators commonly use a Tutanota or Proton email and a fresh wallet address to keep the public peer disconnected from any real-world identity.

At the hypervisor level we do not retain traffic captures or packet headers for Yggdrasil customer traffic. There is no historical record of which IPs connected to the public peer, what volumes they exchanged or how long they remained connected. The VPS disk image is encrypted at rest on the host node and we do not maintain a backup unless the operator explicitly enables the snapshot service. Combined with offshore jurisdiction, this leaves very little data available to any third party who issues a legal request for the host.

Jurisdiction choice for a Yggdrasil public peer is straightforward. Any jurisdiction that tolerates encrypted overlay networks is sufficient. Iceland and Romania are the defaults in our catalog and align with the broader privacy-tools hosting set. Operators who want a public peer in a region currently under-served by the community list can request placement on a specific node, and we will accommodate where capacity allows.