JOIN THE BUILDERS

Private. Fast. Decentralized.

FidoNext — the open-source mesh for private communication

Inspired by FidoNet, rebuilt for the 2026 Internet.

Privacy by Default

End-to-end encryption using modern protocols (Signal-grade crypto: X3DH, Double Ratchet).

Decentralized Mesh Transport

Message relay and routing built on libp2p: QUIC, GossipSub, MASQUE fallback.

High Performance & Low Latency

Fast communication, optimized NAT traversal, low overhead, resilient transport.

Open Source & Community Driven

Transparent code, open governance, built by engineers for engineers.

MISSION

A human communications network that belongs to people, not corporations.

FidoNext returns control of digital life to the humans who use it. We build an open, decentralized mesh where cooperation replaces corporate infrastructure.

No ads No profiling No data resale

Signal’s privacy, without Signal’s servers.

What is FidoNext?

A privacy-native peer-to-peer mesh built on modern cryptography and decentralized transport.

Application Layer

Cross-platform messaging, media, calls, and offline-first communication clients.

Crypto Layer

X3DH, Double Ratchet, sealed sender, metadata-minimized identity and end-to-end encryption.

Network Layer

libp2p mesh: QUIC, HTTP/3, MASQUE fallback, NAT traversal, gossip routing, resilient multi-relay paths.

Transport & Relay Layer

Store-and-forward relays, offline pickup, TTL windows, CID-addressed file delivery and FEC shards.

HUMAN-FIRST DECENTRALIZATION, NOT ANARCHY

A positive, people-owned vision.

We acknowledge the need to moderate criminal and illegal content. We refuse to become an unchecked haven like Telegram, yet we will never compromise private conversations. Public 1→N channels will ship with on-device LLM moderation — custom models running locally, flagging socially dangerous content before publication, while 1→1 chats and closed groups remain private.

Digital Humanity

Communication is a right, not a corporate product. Person-to-person, without intermediaries.

Community-Powered

Users run the nodes, shape the mesh, and revive the spirit of the original FidoNet.

Post-Server Internet

Messaging that works without Big Tech infrastructure. No central servers to seize or silence.

ROADMAP

From 1:1 chats to a billion-node mesh.

Layered development keeps us sane: application, crypto, network, then Fidonext Core to orchestrate it all.

  1. M1

    Base P2P messenger

    Live

    • PeerManager & MessageChannel built on rust-libp2p with ACK/retry.
    • libsignal-client (X3DH + Double Ratchet) for 1:1 chats.
    • Pre-key bundle exchange via DHT entries or QR handshakes.
    • Pure P2P chat tests across every native surface.
  2. M2.1

    Store-and-forward + relay mesh

    In Progress

    • Circuit-Relay v2 chaining (A → R1 → R2 → B).
    • Encrypted message buffers on relays with TTL windows and ACK handshakes.
    • Bootstrap super-relays on commodity VPS for stability.
    • Reuse native offline states across desktop and mobile for pending messages.
  3. M2.2

    Push notifications

    In Design

    • Hybrid push/poll strategy for Android (FCM) and iOS (APNs).
    • Opt-in lightweight relay hints without exposing metadata.
  4. M3

    Files & media

    Planned

    • 512 KB chunks with AES-GCM + Reed–Solomon FEC.
    • Relay-chain delivery with offline pickup and auto-delete by TTL.
    • Reuse the existing file-sharing UI, swap the backend to CID routing.
  5. M4

    Audio / video on libp2p

    Planned

    • Replace DHT signaling with pure libp2p QUIC streams.
    • Wire the media stack to libp2p (ICE/SDP inside the mesh).
    • Relay-assisted media for NAT/CGNAT situations + SRTP over Signal.
  6. M5

    Groups & PubSub

    Next

    • GossipSub overlays per groupID with MLS (TreeKEM) cryptography.
    • Group UI refresh + sub-relay caches for offline members.
  7. M6.1

    Channels & broadcast topics

    Next

    • 1→N channels propagated through regional PubSub meshes.
    • Relay caches store the latest events and serve them via CID lookups.
    • UI adds lightweight subscription logic for creators and readers.
  8. M6.2

    On-device content moderation

    Next

    • Local LLM screens text / media before publishing.
    • Policy files signed by project keys, distributed as encrypted CID packages.
    • Publisher sees live rules; relays can flag non-verified posts.
  9. M6.3

    Mesh bots & SDK

    Next

    • API & SDK delivery: unified REST/gRPC layer plus TypeScript, Rust, Go, and Python clients for Telegram-speed integrations.
    • Conversation-grade workflows for moderation, mesh notifications, DevOps hooks, and user assistants.
    • Secure execution sandboxes with signed permissions and scoped access to mesh data/keys to preserve privacy.
  10. M7

    Traffic camouflage & DPI resilience

    Future

    • Browser-like JA3 / ALPN signatures over QUIC/HTTP3 443.
    • MASQUE CONNECT-UDP fallback, onion 2-hop paths, padding & timing shaping.
    • Super-relays operate as HTTPS edges.
  11. M8

    Fractal scaling

    Future

    • Realm → Region → Cell sharded DHTs with hierarchical PubSub.
    • HyParView / Cyclon partial views, CDN-grade super-relays with TTL stores.
    • Proof-of-Work and rate limiting for public channels.
FOR DEVELOPERS

The post-server internet is a collaboration.

Rust, C++/Qt, libsignal, libp2p, QUIC, MASQUE — plus the unstoppable curiosity to build for people first.

Rustrust-libp2pTOKIO / asyncQUIC / HTTP3MASQUENoise / TLS1.3C++ / Qt / QMLSwift / Kotlinlibsignal-clientMLS (TreeKEM)
  • Mesh transport evolution: Circuit-Relay v2 chains, NAT traversal, hole punching, MASQUE fallbacks.
  • Mobile energy optimization, push/poll hybrid for iOS & Android, and background delivery.
  • Store-and-forward relays, TTL persistence, CID-based chunk storage.
  • Crypto hardening: MLS research, metadata shielding, SRTP over Signal sessions.
  • Super-relay DevOps, telemetry that respects privacy, and fractal scaling experiments.
Team / Hiring

People-powered technology needs people-powered teams.

We are a community-driven open-source project. Maintainers and core contributors are all welcome.

CTO / System Architect

Needs deep experience across Security/Crypto, system architecture, and P2P networks to own libp2p routing design, privacy posture, and long-term scaling.

Rust & P2P Engineers

Tokio async, Rust-libp2p, QUIC/HTTP3 + MASQUE, libsignal, store-and-forward messaging, Ed25519/Curve25519/AES-GCM security, IPFS/Filecoin + GossipSub relays, DPI-evasion.

C++ / Qt UI Developers

Qt/QML messenger UX, multimedia, Rust ↔ C++ FFI (CXX/UniFFI), cross-platform builds.

Kotlin / Swift Mobile Developers

Rust inside Android/iOS, push (FCM/APNs), secure storage, BLE/QR discovery, messenger UX polish.

Security / Crypto Engineers

libsignal-client, MLS, X3DH/Double Ratchet, metadata obfuscation, threat modeling, MITM hardening, audit readiness.

Marketing / PR

Growth storytelling for privacy tech, open-source community building, SMM across X, Telegram, LinkedIn.

We need early maintainers to own core parts of the architecture.

Call to action

Join the mesh while it’s still growing.

Open-source license. Transparent roadmap. Built by people, for people. The next chapter after FidoNet, Signal, WhatsApp, Telegram etc.

Join the builders