> download

Download Mainnet

Mainnet Browser and node for Windows, Linux and macOS – as signed releases with checksums. This page only shows releases that are in the public registry log and whose signatures have been verified.

No release yet.

There is no release yet that is in the registry log and passes verification. Files offered elsewhere as “Mainnet” are not from us – check every file as described below.

Android app

The Mainnet app for Android is only available here as a signed APK – not on Google Play and not in any other app store. Offers there are not from us.

Not published yet.

There is no verified Android release in the registry log yet. As soon as there is one, the APK will appear here with its checksum. Until then you can put the portal on your home screen as a tab. Instructions on the home page →

iPhone and iPad

There is no full iOS app yet – it will come later. Until then: open the portal in Safari, Share icon → “Add to Home Screen”. The tab only does public things (find a domain, search, WHOIS, domain cards, buying info, film) and needs no keys. Instructions on the home page →

Verify it yourself

Compute the checksum – it must match the SHA-256 in the table exactly:

Windows  certutil -hashfile mainnetd.exe SHA256
Linux    sha256sum mainnetd.exe
macOS    shasum -a 256 mainnetd.exe

Verify the signed manifest (both signatures, release key = update-key, the file). Put the file at <folder>/<platform>/<file name>; “keys” is the key manifest from /log/v1/keys:
```
$ mainnet release pruefen <version>.mnrelease --keys keys --root <root-fingerabdruck> --dist <ordner>
  # windows-x86_64/mainnetd.exe liegt in <ordner>/windows-x86_64/
```
Take the root fingerprint from an existing installation or compare it through several channels. With your own log mirror (--log <registry> instead of --keys/--root) the command also checks the log entry.
Existing nodes update themselves with verification: “mainnetd update --check” shows the newest release from the verified log, “mainnetd update --installieren” asks first, downloads over Tor and checks size, BLAKE3 and SHA-256.
If a checksum or signature does not match, do not run the file and let us know through the chat.

Specification

The mn1 protocol is openly specified: identity and keys, addresses, registry log, zone and mail, transport, message formats, ordering and chat, domain cards. The specification will be published here together with the first release.

Source code

Audit status

As of 27 Oct 2026: the code has had an internal review (pre-audit), but no external audit yet. An external audit by specialists is planned before the public launch; the report will be linked here. Until then: Mainnet has not been independently audited.