Scroll to go deeper · Move to disturb · Click to fire
Overlay network · run by volunteers
A network nobody owns.
Route, store, resolve and earn. Traffic hides behind three relays, files are split into encrypted pieces held by many machines, and names belong to whoever holds the key. Volunteers run every part of it, so there is no single switch anyone can turn off.
0 peers online right now
01 · Network
Every node finds its place by hashing its own name.
Peers
0
Links
0
Capacity
0 TB
illustrative
Network map · Surface
Hover the rabbit head to open the live node graph · tap a node for its address and peers
A node’s spot on the ring is the SHA-256 hash of its ID, the same keyspace the network’s lookup table uses, so side-by-side here means side-by-side there. The lines are worked out from that ordering, not measured, and no IP address is ever shown. The roles on the live network include storage, gateways, AXON relays, workers, compute, validators and watchtowers; this demo uses four of them.
04 · Credits
Be useful. Earn credits.
Store shards
Hold encrypted pieces of the network's data.
Relay bandwidth
Carry onion-routed traffic you cannot read.
Run a gateway
Bridge people in from the ordinary web.
Stay up
Sustained uptime is measured by Proof of Facilitation.
Only checked work pays: Proof of Facilitation audits what each node actually did. Going offline costs you nothing except the pay you would have earned. Add a payout address to collect; on-chain settlement is still being switched on. How the credit economy works
05 · Live now
The pool, as it stands.
Capacity in use
0%
Peers online
0
Capacity pooled
0 TB
Countries
0
Roles running
0
07 · Run a node
Give disk and uptime. Get credits and a local S3 endpoint.
You give
Disk space (20 GiB unless you change it) and time online. If you want, also a port the internet can reach so you can relay, an HTTPS gateway, or a container worker.
You get
Browser access to the network, credits for work that passes audit, and your own S3-compatible storage endpoint on your machine.
Relaying is optional, but every node that relays makes everyone harder to trace.
# Linux: one static binary
chmod +x dendritic-node
./dendritic-node
# first run saves its settings to
# ~/.config/Rabbiit/storage-node/config.json
# AXON proxy listens on 127.0.0.1:4480
08 · FAQ
Questions
Is anonymOS a Linux distribution?
No. Its kernel is original code in D with no garbage collector. It answers Linux system calls as a compatibility layer over its own capability core, which is why unmodified musl programs run even though nothing underneath is Linux.
Will my Linux, Windows or Android apps run?
Programs built against musl, in practice Alpine packages, install and run. glibc packages from other distributions don’t. Windows, macOS and Android apps are planned through Wine, Darling and Waydroid inside their own domain. Android is closest: the ART runtime starts, but no .apk runs yet.
What do I need to try anonymOS?
An x86_64 virtual machine with UEFI firmware, x2APIC enabled, 4 vCPUs and 4 GB of RAM, or 6 GB if you plan to install. It is developed in QEMU and VirtualBox and hasn’t been confirmed on physical hardware.
Is it secure enough to rely on?
Not yet. Capabilities, domains and signed updates exist, but memory hardening is missing: no ASLR, no non-executable stack, and only partial W^X. Updates are signed with a development key and the boot loader doesn’t yet check its modules.
What does a node give, and who can see it?
Disk space (20 GiB by default), uptime and any extra roles you switch on. Your node holds encrypted pieces it can’t read and only talks to other volunteers through AXON, so volunteers never learn each other’s IP addresses. The operator, rabbiit, does see your IP through the node’s check-in signal; the privacy promise is between volunteers.
Can a gateway read what it carries?
No. It looks only at the TLS server name to decide where to send a connection, then forwards the still-encrypted bytes. Encryption runs all the way to the destination site.
Is anonymous routing live?
Yes, end to end: nodes reach each other over AXON through three-hop circuits. How much that hides depends on size, and the network is small today, so treat it as working rather than as anonymous yet. Nothing here hides timing from someone watching both ends, and this website itself is still served over ordinary HTTPS.
How are node operators paid?
In credits, for storage and audit work that Proof of Facilitation has confirmed, once you add a payout address. Downtime isn’t penalised, just unpaid. On-chain settlement is still being turned on.
Why this exists
Being watched is the default. This is how you opt out.
It isn’t about hiding
It’s looking up a diagnosis, searching a word that counts as evidence where you live, or keeping a source’s name safe.
Nobody to lean on
Operators who don’t know each other, in different places. No company to subpoena, no server to seize, no one person who holds the whole picture.
Safety in numbers
Privacy that only a few people use makes those few stand out. It protects you only when it’s ordinary, and that takes people more than cryptography.
Checked around the clock by independent monitor nodes on several networks, not by the website’s own server. That’s the only way to tell “the site is down” apart from “the site can’t be reached from one place”.
Figures below are a snapshot from 22 October 2026. The live feed is on dendritic.network/status.
Each cluster is a role, with one sphere per node running it. A node counts under every role it runs, so clusters overlap. Tap a cluster.
11active nodes
220 GiBstorage offered
2regions reporting
19 / 64nodes reporting in this week
Components, last 90 days
Response time by region
Region
Mean
Checks
Failed
Canada
77 ms
236
0
Unknown
no successful check
531
59
Storage is self-reported, so treat it as a ceiling. Traffic is added up from what nodes report about themselves, because the server never sees node-to-node transfers. Reporting in is optional, so it measures coverage, not health. Gaps where nobody reported are shown as gaps, not zeros: an idle network and an unmeasured one look the same on a chart and mean completely different things.
Settlement
The epoch chain
Every hour, the network’s checked work is committed to Ethereum Sepolia as a pair of Merkle roots. They’re read straight from the chain, not from the website, because independence is the whole point of settling on-chain.
An example chain. Green means finalized, red means a dispute is open. Tap a block to raise or settle a dispute.
Four AXON to the dollar. AXON is spent in the store, and what’s spent flows back to the treasury that pays the people running the network.
AXON currently lives on Ethereum Sepolia, a test network. It can’t be moved to mainnet. To see it, switch your wallet to Sepolia (MetaMask hides test networks by default). Gas there is free test ETH from a faucet.
Where the supply sits
1,000,000 AXON minted. 393,000 (39.3%) is in people’s hands. Tap a ball.
Ways in
Membership$5 / monthEvery machine in the lab, plus 20 AXON in your wallet each month. Without it you get one machine a month, chosen for you.
Pack4 AXON$1
Pack20 AXON$5
Pack60 AXON$15
Pack200 AXON$50
No account needed: paste the wallet the AXON should go to, pick a pack and pay. Copy the address from your wallet rather than typing it, because a typo is someone else’s real address and the transfer can’t be undone. Buy on dendritic.network
Earn it
Run a node. The only way new AXON is created is as payment for checked work, settled each epoch.
Spend it
The store takes AXON for everything it sells, and cards for physical and digital goods.
Claim it
Rewards are claimed, not sent. See the three calls on the epochs section. Anyone can send the claim for you; the AXON still lands in your wallet.
One operation is queued on Timelock P and can run after 18 November 2026. No on-chain proposals exist yet. The older off-chain poll, one member one vote, is kept as an archive with no on-chain authority.
Records
The network’s books
What exists, who controls it, and what has moved. Where a contract exists, the numbers come from the chain; where it doesn’t, that’s said plainly.
Three balances that never mix
Try pulling them together: there’s no link between them. AXON never buys points, points never become AXON, and no ownership record reads an AXON balance.
Releases are published on-chain. Nodes wait for a release’s activation time, fetch it from the storage network, and install it only if its SHA-256 and size match. A revoked release is never installed, and nodes on it roll back.
What the fleet reported running at the last snapshot: 7 on one build, 6 on another, plus a debug build and a dev build. Tap a group.
How to read a figure
on-chain
Read live from the chain at the block shown
indexed
From the site’s copy of contract events
attested
An off-chain record whose hash is on-chain (none yet)
design
From design documents, not from any chain
This isn’t an audit. It shows what anyone can check, with every address linked to the explorer.
Activity board
The network, as tickers
How much AXON exists and moves, how much sits in payment channels, what compute costs and how many nodes are up, measured from the chain and the site’s own records.
Activity only. Nothing here is for sale or an investment. AXON has no market price: no exchange lists it, and this board never shows one.
How each epoch’s rewards will be shared between services under reward policy v1. Nothing is shown as paid until an epoch actually pays out. Toss the pools around; tap one for its share.
Thirteen pools, from storage at 25% to mailbox and delegate at 2.5% each.
Join
Run a node
Four steps: install, pick your roles, add a payout address, start it and leave it running. It shows up on the network map within about five minutes. Not sure what your machine can do? Try the device check first.
Tap a step.
Pick your roles
Choose as many as you like. A single machine happily runs storage and validation together. Roles marked with a port need the internet to reach your machine, which on a home connection usually means a port-forwarding rule and won’t work behind carrier-grade NAT.
curl -fsSL https://rabbiit.io/install.sh | sh
The config above is a starting point built from the documented setting names; check it against the node’s README before relying on it. The installer is an ordinary shell script, so read it first if you like. Leave axon.seeds empty to join the public overlay. No binaries are published yet.
Its own dashboardAt 127.0.0.1:9090, local only. Capacity, peers and earnings, and every setting can be changed there later.
Paid by claimOnce reward contracts deploy, each settled epoch makes your share provable and you claim it in one transaction.
Leaving is finePieces are erasure-coded across many nodes, so stopping costs redundancy the network rebuilds, not data.
Networking built inNo proxy or router changes needed for storage and validation. Relaying needs axon.relay and axon.listen.
Using it
Browse the network
Every node runs a small proxy on your own machine at 127.0.0.1:4480. Point a browser at it and you can open services inside the network by their .key.axon address or by a registered name.
The proxy only listens on your machine, since anyone who can reach it can use your circuits.
Two kinds of address
.key.axon
A 56-character address that is the service’s public key. It works with no setup, no lookup and no certificate authority: the address proves the key.
Registered names
Like example.axon. These need your node set up with the on-chain resolver: axon.name_rpc, axon.name_contract, and axon.name_suffixes for any extra TLD.
Ordinary websites
Refused by default. Nothing leaves the network unless you set axon.exit_via to an exit, and there is never a silent fallback to a direct connection.
Firefox
Settings → search “proxy” → Network Settings.
Manual proxy configuration: HTTP proxy 127.0.0.1, port 4480.
Tick “Also use this proxy for HTTPS”.
Remove localhost, 127.0.0.1 from “No proxy for” so .key.axon routes.
Save, then visit http://<address>.key.axon.
A separate Firefox profile (firefox -P) saves switching back and forth.
Or use a proxy-switching extension that sends only *.axon to the proxy. Remember: the network hides your IP from a service, not what you send it. Logging in identifies you whatever the route.
Naming
Names and TLDs
Every service already has an address: its public key, as .key.axon. The registry, a contract called AxonTLD, lets you put a readable name like example.axon on top, owned by your wallet and pointing at one or more services.
Names only work inside the network. Registering example.com here gives you no control of the real example.com.
A name tree hanging from the .axon root. Tap anything to learn the rule behind it; pull a branch to see what moves with it.
OwningFirst come, first served. The registering wallet owns it with no expiry or renewal. Only the owner can change, transfer or release it; the admin can’t seize it.
RulesASCII letters, digits and hyphens; up to 63 bytes a label and 253 in total. Unicode is refused, so convert to xn-- yourself.
RecordsUp to 32 per name: AXON keys (the only kind the proxy dials), plus A, AAAA, MX and raw DNS records. The proxy tries up to four AXON destinations, primary first, and never falls back to the open internet.
SubdomainsOnly the parent’s owner can create them. Releasing a name removes everything under it.
TransfersTwo steps: the owner proposes, the recipient accepts. Records survive and the old owner loses all control.
FeesA small fee per change in the chain’s native currency, plus gas. Reading is free. Send the exact fee; anything else reverts.
New TLDs
Real internet TLDs like .com are switched on by the administrator after marking them as in the IANA root zone. Any new or custom TLD needs a token-holder vote: anyone proposes, holders vote by balance, and after the voting period anyone can execute it. .axon was on from the start. Disabling a TLD only stops new registrations.
What a name gives away
Registering is a public transaction, forever, and a wallet’s history can often be traced to a person.
The name-to-key link is readable by anyone. The service’s IP stays hidden, but its existence doesn’t.
The RPC you resolve through sees what you look up, and you trust its answer.
Short and dictionary names can be guessed.
If a service must stay hidden, share its .key.axon address and don’t name it. An optional bridge can also serve the registry as real DNS through BIND, for people who want standard tools to read it.
Read this first
Security and anonymity
What the network hides, what it doesn’t, and how far today’s network is from what the design can do.
The designShaped like Tor: three-hop onion circuits, a pinned guard, self-certifying addresses and hidden services met at a rendezvous.
Needs a crowdProtection is only as big as the set of honest relays run by different people on different networks.
Small todayTreat it as working end to end, not yet as hiding you.
Names are publicRegistering one is a permanent public record.
Why the crowd matters
An attacker who runs a share of the relays can link you when they hold both your guard and your last hop. Move the sliders and build circuits to see how quickly a small network gives you away.
Red relays belong to the attacker.
Who learns what
Watcher
Learns
Your ISP
An encrypted stream to one guard, nothing about where it goes
Any one relay
Only its two neighbours in the circuit
A directory holder
Blinded entries it can’t turn into a list of services
The service you visit
That someone asked and what they asked, but not who
Someone who knows a name
The service’s key, not its IP
What it can’t protect against
Someone watching both ends can match timing and volume. This is the known limit of all low-latency onion routing, Tor included.
Many hostile relays make it likely they hold both ends of your circuit, especially on a small network.
A hostile guard sees your IP and, with help near the service, can link you.
What you send. A login names you whatever the path.
rabbiit sees node operators’ IPs through heartbeats. The privacy promise is between volunteers.
Today’s network
Current deployments are development networks and aren’t anonymous: six relays is the minimum for hidden services to work at all, test clusters let relays on one subnet form circuits, and some use two hops for speed. More independent relay operators on different networks and in different countries is what changes this. Two design gaps remain: every node learns the full relay list, which won’t scale forever, and nodes behind NAT can’t relay yet.
Checklist for real anonymity
allow_same_network set to false everywhere.
hops left at 3, never 2.
Many relays from independent operators across networks and countries.
Guards pinned, with a plan for rotating and watching them.
Requests that carry nothing identifying.
For names: a trusted RPC and a wallet whose history doesn’t point to you.
An eye out for sudden relay growth from one operator.
Control
Management panel
Buy a name, point it at your service, and manage everything in one place. Your wallet is your account.
From a running node to a named site in four moves. Tap a step.
Read the contracts, wire up a wallet, and talk to a running node. The smart contracts and API run on Ethereum mainnet. Until they’re deployed there, the live contracts are test deployments on Sepolia, where AXON has no cash value.
01Wallet
Connect a browser wallet and switch it to Ethereum mainnet (chain 1).
AxonChannels, the bootstrap registry, AxonTLD and the timelock contracts are also deployed. Their current addresses are listed on the live Records page; always take addresses from there rather than from a copy.
03Read the chain
These assume AXON follows the standard ERC-20 read interface. Confirm against the ABI the creator publishes before writing anything that sends transactions.
04Node interfaces · local
127.0.0.1:4480AXON proxy. Point a browser or HTTP client here to reach .key.axon services and registered names.
127.0.0.1:9090The node’s own dashboard: capacity, peers, earnings and settings.
S3-compatibleEach node exposes a local storage endpoint; see the node’s README for its address.
All three listen only on your own machine.
05Public API
The API will run against the contracts on Ethereum mainnet. Its endpoints, authentication and rate limits come from the creator; this panel will hold them once they’re published.
awaiting spec
Run a node · step zero
Which node are you?
Measure this device in a few seconds and see which roles it can carry. Then head to Run a node to set it up.
✦Which node are you?
Measure this device and get the roles it’s suited to. The test runs entirely here and nothing is sent anywhere.
Privacy · what you give away
Your browser, as every site sees it
No login, no cookie, and websites can still tell your browser apart from millions of others. This is what they read.
◉Fingerprint mirror
Every website can read these details from your browser right now. Combined, they often single you out without any cookie.
reading…
Hidden by the networkYour IP address and the location it reveals. Services you reach through three relays see a relay’s address, not yours.
Not hiddenEverything in the grid above. It travels with your browser, so use a separate, hardened browser profile for anything sensitive.
Sovereign seal
Where did this screenshot come from?
Every page of this network carries its own near-invisible signature. Read it back from any screenshot.
⌖Screenshot verifier
Every page here carries the Sovereign Seal, a near-invisible pattern recording the session, the hour and the page. Drop in a screenshot to read it.
Works best on PNG screenshots at their original size. Heavy compression, unusual resizing or editing can erase it.
Governance · the handoff
Road to full decentralization
Every control the creator holds at launch, and the step that hands each one to the network.
▲Road to full decentralization
0%
The network launches with the creator holding key controls, then hands each one off. This tracks every control point, where it stands, and what retires it.
Account
Your slip
A slip is your account. Sign in with an Ethereum wallet, and the first sign-in creates it, with no email and no password. Or use a name and password instead.
Signing in is a message your wallet signs. It costs no gas and moves no money.
With a wallet
Your wallet shows a sign-in request naming the site. Approve it and you’re in. You can then buy AXON packs, subscribe, and register .axon names.
With a password
Pick a name of up to 20 characters, which is never shown publicly. There’s no password recovery, so keep it safe. You can link a wallet later from your profile.
No wallet yet?
Install MetaMask and switch it to Sepolia to see test AXON.