Open Code. Public Trust.
GhostMesh is a public utility. We believe digital rights tools must be transparent, audit-ready, and community-owned. Read our code, submit patches, or audit our cryptography.
Where to Contribute
Join one of our primary coordinate engineering teams.
01. Cryptographic Auditing
Auditing of our custom serverless Signal Double Ratchet protocols, perfect forward secrecy implementations, and zero-knowledge ID schemes.
02. Client Engineering
Developing and tuning native low-power linkers (BLE and Wi-Fi Direct) for Android and iOS systems, alongside lightweight user interfaces.
03. Local AI Optimization
Quantizing 1.4B / 3B parameter models for offline translation and emergency feed indexing. Optimizing memory footprints on edge devices.
Repository Map
Understanding the Workspace
The GhostMesh codebase is segmented into modular workspaces. The core background daemon (`daemon`) manages low-level routing and radio transmission. Crytographical algorithms are separated into a standalone, pure audit library (`crypto`). Clients call daemon endpoints via RPC interfaces.
daemon: Written in Rust for maximum memory safety and low runtime footprint on Android platforms.
crypto: Zero external dependencies except verified mathematics primitives, maximizing audit auditability.
ghostmesh-protocol/
├── daemon/ # Core background daemon
│ ├── src/
│ │ ├── transport/ # BLE & Wi-Fi Direct linkers
│ │ └── routing/ # Store-and-forward routing engine
│ └── Cargo.toml
├── crypto/ # Cryptographic primitives library
│ ├── src/
│ │ ├── ratchet/ # Serverless Double Ratchet
│ │ └── zk_proofs/ # Zero-knowledge signature logic
│ └── Cargo.toml
├── clients/ # Native user-facing applications
│ ├── android/ # Android client (Kotlin)
│ └── ios/ # iOS client (Swift)
└── docs/ # Protocol specifications & RFCsContributor Sign-off
To protect project integrity, all code contributions must be cryptographically signed via GPG or SSH keys. Core protocol changes require review by at least two maintainers and mathematical validations.