EpixNet
Peer-to-peer web

Websites shared by peers.

Signed websites, verified content transfers, and encrypted channels. EpixNet brings peer-to-peer publishing to internet connections, local networks, and configured mesh links.

Download EpixNet Explore EDX & ECX
How it works

Content, channels, and connections.

EpixNet combines EDX for moving content, ECX for encrypted channels, and Epix chain records for names and identities. The transport underneath can change without replacing the applications above it.

EPIX CHAIN identity · name records name key record name key record … chain records · configured verification resolve name check name records resolve destination EPIXNET peer-to-peer distribution · serves the bytes client resolves a name when needed, then fetches the bytes from peers.

Names and records on the Epix chain.

Epix chain records support .epix names and identities. New lookups and chain updates may need network services; content already available locally can be read without a fresh chain connection.

The network moves the bytes.

Site files can be stored and shared by peers that retain them. A page may also request external services, and network discovery or name resolution can involve supporting infrastructure.

Signed content, checked by the client

Clients check signed manifests and file hashes when accepting xite content. These checks help detect unauthorized changes; they do not prove that content is safe, accurate, or lawful. Protect signing keys and review any permissions you grant.

Inside EpixNet

Two building blocks. Different jobs.

EDX moves the files that make a xite. ECX carries encrypted conversations. Both use the peer network, with different rules for what is shared and who can read it.

EDX / content transfer

Fetch pieces. Verify as they arrive.

EDX requests content by its hash and checks incoming ranges against that identity. It can fetch missing pieces from multiple peers and retain verified progress after an interrupted transfer.

  • BLAKE3 content hashes and incremental range verification.
  • Small-file bundles reduce the number of separate requests.
  • The peer protocol runs over TCP, Tor, I2P, and Reticulum in supported builds.
What does that mean for a website?

A page can request the files and ranges it needs, while the node keeps verified pieces for reuse. A slow or interrupted peer does not necessarily mean starting again. The required content must still be available from a reachable peer.

Read the EDX format
ECX / encrypted channels

Conversations carried in sealed envelopes.

ECX is the channel and envelope system used by Epix Mail. Peers replicate encrypted records; the connected node uses the linked identity’s keys to find and open messages addressed to it.

  • Pairwise encrypted sessions with keys that advance as messages are exchanged.
  • Padded envelopes and detection tags designed to limit exposed messaging metadata.
  • A shared channel foundation for applications, with mail integrated today.
Where does decryption happen?

Your connected EpixNet node encrypts, decrypts, and indexes messages. Use a node you trust. The device, recipients, network observations, and local storage settings still matter; encrypted channels do not guarantee anonymity.

Read the channel protocol
01 / peer-to-peer

Your readers are the network.

Peers can retain and share downloaded content. Availability depends on the copies they keep, their connectivity, and the application’s sharing settings.

  • Share hosting across peers.
  • Reduce dependence on a single content host.
  • Keep useful local copies where supported.
02 / cryptographic identity

Publish with cryptographic keys.

Keep backups and protect signing requests, recovery information, and any local wallet password. Key-based publishing does not eliminate phishing.

03 / .epix domains

Names you actually control.

Use .epix names through EpixNet’s name-resolution support. Name control and resolution depend on chain rules, the software, and configured network services.

04 / distributed delivery

More peers can help share the load.

Additional reachable copies can improve access. Actual speed depends on peer availability, bandwidth, routing, and the files being requested.

05 / desktop browsing

Browse through your local client.

On supported desktop setups, install the client and open xites through its local web interface in a compatible browser. Native .epix addressing and routing features vary by browser and platform.

06 / intermittent connections

Keep useful content close.

Read files retained on your device when a connection disappears. When networking resumes, peers can exchange update hints and fetch available changes. Content retention, reachable peers, and external services still determine what works.

Explore offline & radio setups
07 / open source, MIT

Audit it. Fork it. Run it.

EpixNet’s core source is released under the MIT license. Bundled components retain their own licenses. Contributions, review, and forks are welcome.

Offline & off-grid

Beyond an internet connection.

A cached page, an isolated local network, and a radio-connected mesh are different ways to use EpixNet. Choose the setup that fits the connection you actually have.

01 / on your device

Read while disconnected.

Keep guides, reference pages, and other xite files on your device before you leave a connection. Offline Mode pauses node peer networking so you can work with available local content.

02 / nearby peers

Share over a local network.

An isolated Wi-Fi or Ethernet network can connect nearby nodes without an internet uplink. Keep node networking enabled and configure local discovery or reachable peers. Preload the content and identity information you need.

03 / radio bridge

Extend the network over radio.

Reticulum supports networks that combine IP links with LoRa or packet-radio interfaces. EpixNet’s current mesh connection is TCP-based; a radio deployment needs a compatible Reticulum bridge, suitable hardware, and configuration.

Integration path: direct LoRa/Bluetooth radio drivers are not exposed by EpixNet’s current mesh settings. The complete radio setup still needs hardware validation.

  1. EpixNet node
  2. Local TCP link
  3. Reticulum bridge
  4. LoRa / packet radio
  5. Remote mesh peer
Example deployment path: EpixNet connects by TCP to a compatible Reticulum bridge; the bridge supplies the radio interface. This is not a built-in phone-radio feature.
Should I enable Offline Mode for radio?

No. The Offline Mode switch disables node peer networking, including Reticulum. To exchange data over a local or radio-connected mesh, leave that switch off and configure the intended network path. No internet uplink and no networking are different conditions.

What happens when a connection returns?

Propagation peers can retain recent update hints. Your node asks what it missed, then fetches available content and verifies it. Hints have bounded retention and are not backups of the site; catch-up depends on peers still holding the files.

What should I prepare before going off-grid?

Load the xites and identity information you need, configure your peers or mesh bridge, and test the setup while you can still make changes. Small pages and text suit narrow radio links better than large media. New chain lookups, wallet broadcasts, and third-party web services may remain unavailable.

Reticulum interface guide EpixNet mesh implementation
Get EpixNet

Pick your operating system.

Open-source software. Review the release notes for supported platforms, installation steps, and build-specific features. Identity and wallet requirements depend on what you use.

v— · Desktop and mobile projects · check release availability

EpixNet for Windows.

  • EDX verified content transfers
  • ECX encrypted channels for mail
  • Browser features vary by platform
  • Tor and I2P in supported builds
  • Privacy settings vary by feature and build
  • Content shared through reachable peers
  • Open source, MIT
View releases Check available files

See release requirements

Release notes

Other platforms and source code: Installation guide

Build on it.

Explore the source, protocol documentation, and guides for building a xite.

Developer guide