ZeroNet uses Bitcoin cryptography and BitTorrent technology to build a decentralized censorship-resistant network.
Users can publish static or dynamic websites into ZeroNet and visitors can choose to also serve the website. Websites will remain online even if it is being served by only one peer.
Connecting to Tor before ZeroNet
Inside Whonix-Gateway (Qubes-Whonix:
Extend onion-grater Whitelist
To download and verify Zeronet via git, run the following commands in a terminal inside Whonix-Workstation:
First install dependencies.
Qubes-Whonix: If the ZeroNet qube is based on a Qubes TemplateVM, complete this action in the TemplateVM.
Update the package lists.
sudo apt-get update
git python-msgpack python-gevent.
sudo apt-get install git python-msgpack python-gevent
Qubes-Whonix: The actual install can be done in the ZeroNet qube.
Retrieve ZeroNet's signing key. 
gpg --recv-keys "960F FF2D 6C14 5AA6 13E8 491B 5B63 BAE6 CB96 13AE"
git clone https://github.com/HelloZeroNet/ZeroNet.git
Change into the ZeroNet folder.
Check the ZeroNet signature.
git log --show-signature
./zeronet.py --tor always --fileserver_ip $(qubesdb-read /qubes-ip)
./zeronet.py --tor always --fileserver_ip 10.152.152.11
(Note: the following will be no longer required once Whonix releases a custom Tor Browser for connecting to alternative networks. )
Configure Tor Browser to connect to localhost.
In Tor Browser type
about:config into the URL bar -> press
Enter -> search for
network.proxy.no_proxies_on -> Set to
Start Tor Browser.
Navigate to the ZeroNet web interface. Paste http://127.0.0.1:43110 into Tor Browser's url field and press enter.
The process is now complete and ZeroNet can be used. Note that full ZeroNet functionality has been confirmed in Whonix. 
/usr/local/etc/onion-grater-merger.d/because that onion-grater settings folder is persistent in Qubes-Whonix TemplateBased ProxyVMs, i.e. Whonix-Gateway (commonly called
sys-whonix). Non-Qubes-Whonix users could also use
/etc/onion-grater-merger.d/. Qubes-Whonix users could also use
/etc/onion-grater-merger.d/but then users would have to make
/etc/onion-grater-merger.d/persistent, which would require doing this inside the Whonix-Gateway TemplateVM (commonly called
whonix-gw-14) and restart their Whonix-Gateway ProxyVM or to use bind-dirs. Both is more more complicated than simply using
/usr/local/etc/onion-grater-merger.d/which is persistent either way and even allows multiple Whonix-Gateway ProxyVMs based on the same Whonix-Gateway TemplateVM for lets say one Whonix-Gateway ProxyVM extending and relaxing onion-grater's whitelist and the other Whonix-Gateway ProxyVM with the default more restricted onion-grater whitelist.
- Except in the case of YaCy that needs internet access.
- As at May 2018.
This is a wiki. Want to improve this page? Help is welcome and volunteer contributions are happily considered! See Conditions for Contributions to Whonix, then Edit! IP addresses are scrubbed, but editing over Tor is recommended. Edits are held for moderation.