A clean relay view for a local-first Git mesh.

ForkMesh keeps encrypted repository data on independently operated desktop hosts while the Worker coordinates discovery, authenticated HTTPS routing, encrypted rooms, and clone failover.

Browse repositories Read docs

The live network, compressed into the signals that matter.

Activity, payout eligibility, and leaderboards share one surface so the page reads like a monitoring console instead of separate reports.

Host activity

Last 24 hours

minute samples
Loading activity...

Payouts

Node wallets

eligibility
Loading wallets...

Non-custodial These are public payout addresses only. ForkMesh never stores payout-wallet private keys or controls node funds. Federated nodes are eligible only after an approved relay forwards the original fresh node-signed health and ForkMesh-mirroring proof; wallet-only claims are excluded. User-owned funds, the community-funded pool, pending allocations, and completed on-chain transfers are separate states. Eligibility does not guarantee selection or payment.

Reputation

Leaderboards

network wide
Loading leaderboards...

Relay architecture

Cloudflare coordinates the route. Desktop hosts keep the code.

The Worker is the reachable control plane. It helps clients find an active path without becoming the canonical home for every Git object.

  1. 01

    Catalog Durable Object

    Indexes public repository metadata for /api/repositories.

  2. 02

    HTTPS mirror gateway

    Desktop nodes expose loopback gateways through authenticated Cloudflare Tunnels; game sockets carry no repository bytes.

  3. 03

    Git clone protocol

    git clone https://forkmesh.com/owner/repo streams upload-pack data from a healthy, integrity-verified mirror under the original URL.

  4. 04

    Issue and PR inbox

    Signed submissions arrive through Worker inboxes and become Git files when merged.

  5. 05

    Encrypted rooms

    Default chat uses a relay-derived authenticated shared key. Frames encrypt on the wire, but the relay can decrypt them; persisted history is capped at 500 frames for 7 days.

  6. 06

    Storage boundary

    The relay coordinates paths. The hosting desktop mirror remains the source of truth.