The dendritic network

Browse the network

Every dendritic-node runs a small proxy on your own machine. Point a browser at it and you can open services inside the dendritic network: by their self-certifying .key.axon address, or by a registered name.

1. Before you start

You need a running node. Run one; any role will do. Its proxy listens on 127.0.0.1:4480 (the axon.proxy_listen setting) and accepts both plain HTTP requests and CONNECT. It is bound to this machine only, because whoever can reach it can use your node's circuits.

The proxy reaches two kinds of address:

  • <56 characters>.key.axon: a service's public key written as an address. It works with no further setup: no lookup, no certificate authority. The address proves the key.
  • Registered names, like http://example.axon: only once your node has a name resolver configured (below).

2. Firefox

  1. Open Settings, search for proxy, and click Network Settings… → Settings….
  2. Choose Manual proxy configuration.
  3. HTTP Proxy: 127.0.0.1, Port: 4480.
  4. Tick Also use this proxy for HTTPS.
  5. If you want .key.axon names to route even though they look local, clear localhost, 127.0.0.1 from No proxy for.
  6. Leave the DNS-over-proxy defaults as they are and click OK.

Then visit http://<address>.key.axon, or a registered name such as http://example.axon.

A Firefox profile kept just for this (firefox -P) saves you switching the proxy back and forth.

3. Chromium

Launch it with the proxy on the command line, ideally with a separate profile:

chromium --proxy-server="http://127.0.0.1:4480" --user-data-dir="$HOME/.config/chromium-dendritic"

Or keep your normal browser and use a proxy-switching extension such as FoxyProxy, with a pattern that sends only *.axon and *.key.axon to 127.0.0.1:4480.

4. Names and other TLDs

Resolving .axon names, and any extra TLD admitted on this network (such as .com inside it), needs the node to be configured with the on-chain resolver: axon.name_rpc (an Ethereum JSON-RPC URL) and axon.name_contract (the registry address), plus axon.name_suffixes for any TLD other than .axon. Without them, only self-certifying .key.axon addresses work. Configuring the resolver.

Names are network-local

Registering example.com in this registry does not give you the public-DNS example.com, and it has no effect on the internet. Inside the dendritic network, and only for nodes configured to resolve .com, it resolves to the AXON identity its registrant set.

Lookups are plain eth_calls to the RPC you configured. You trust its answers; no cryptographic proof is checked.

How to register a name →

5. Ordinary websites

The proxy refuses ordinary internet addresses. The dendritic network is an internal network, and nothing leaves it unless you choose an exit: set axon.exit_via to an exit's .key.axon address and your node routes clearnet requests through it. There is no silent fallback to a direct connection. Exits and their risks.

Browsing through the overlay hides your IP from the service, not what you send it. A login or anything else identifying in a request identifies you regardless. What the network does and doesn't hide.