hive-mesh

Mesh networking library with CRDT sync, transport security, and topology management.

Overview

hive-mesh provides the core mesh networking layer for the HIVE protocol, including:

• Transport - Pluggable transports (UDP bypass, BLE) with connection health monitoring and reconnection
• Security - Ed25519 identity, X25519 key exchange, ChaCha20-Poly1305 encryption, formation keys
• Discovery - mDNS and static peer discovery with hybrid strategies
• Topology - Dynamic topology management with partition detection and autonomous operation
• Routing - Mesh routing with data aggregation and deduplication
• Storage - Automerge CRDT backend with Iroh P2P sync, negentropy set reconciliation, and redb persistence
• Beacon - Geographic beacon broadcasting and observation with geohash indexing
• QoS - Bandwidth management, TTL, retention policies, sync modes, and garbage collection
• Broker - Optional HTTP/WebSocket service broker (Axum-based)

Installation

[dependencies]
hive-mesh = "0.1.0"

Feature flags

# Example with features
hive-mesh = { version = "0.1.0", features = ["automerge-backend", "bluetooth"] }

Quick start

use hive_mesh::{HiveMeshBuilder, MeshConfig};

#[tokio::main]
async fn main() -> anyhow::Result<()> {
    let mesh = HiveMeshBuilder::new()
        .with_config(MeshConfig::default())
        .build()
        .await?;

    // mesh is ready for peer discovery and data sync
    Ok(())
}

Kubernetes Deployment

hive-mesh includes a binary target (hive-mesh-node), Dockerfile, and Helm chart for Kubernetes deployment.

# Build the binary
cargo build --release --bin hive-mesh-node --features node

# Build Docker image
docker build -t hive-mesh-node:latest -f deploy/Dockerfile .

# Deploy to k3d (local Kubernetes)
k3d cluster create hive-alpha
k3d image import hive-mesh-node:latest -c hive-alpha
helm install hive-mesh deploy/helm/hive-mesh \
  --set "formationSecret=$(openssl rand -base64 32)" \
  --set replicaCount=3

See the full Deployment Guide for details on configuration, verification, cluster lifecycle, and multi-cluster federation testing.

Development

# Build (default features)
cargo build

# Build with all optional features
cargo build --features automerge-backend,bluetooth,broker

# Run tests
cargo test

# Clippy
cargo clippy -- -D warnings

CI

CI runs via GOA (GitOps Agent) on every Radicle patch:

1. Format - cargo fmt --check
2. Clippy - cargo clippy -- -D warnings
3. Tests - cargo test
4. Feature builds - automerge-backend, bluetooth, broker

Results are posted as patch reviews (accept/reject). Community patches require a delegate "ok-to-test" comment before CI runs.

Manual CI

# Run the full CI pipeline locally
bash .goa

Source

• Radicle: rad:z2Jq9dpxMjf1H17JTT1D89RnvP4kQ (browse)
• crates.io: hive-mesh

License

Apache-2.0

OTA Firmware Updates

hive-mesh nodes can push firmware updates to HIVE-Lite ESP32 devices over UDP:

# Via HTTP API (when running as hive-mesh-node)
curl -X POST http://localhost:3000/api/v1/ota/<peer_id> \
  -F "firmware=@firmware.bin" -F "version=0.2.0"

# Check progress
curl http://localhost:3000/api/v1/ota/<peer_id>/status

The OTA sender implements stop-and-wait reliable transfer with SHA256 verification and optional Ed25519 signing. See ADR-047 for protocol details.