Plain-language terms

ForkMesh Terms

Last updated July 23, 2026.

Short version: ForkMesh is experimental distributed code-hosting software. Use it only for repositories you have the right to mirror, keep your keys on your own device, and independently verify every transaction before signing it.

Using ForkMesh

You are responsible for the repositories, messages, issues, pull requests, profile data, and payment addresses you publish through ForkMesh. Do not use ForkMesh to host or distribute content you do not have permission to share.

Joining the network

Joining ForkMesh does not require a cryptocurrency payment. You may optionally publish a self-custodial payout address or voluntarily contribute from your own wallet to the community reward pool. ForkMesh never asks for a payout- or contribution-wallet private key, seed phrase, or mnemonic. Separately, the first instance operator may explicitly import the existing community-pool key into that operator’s encrypted local Qt signer.

Wallet custody and fund states

ForkMesh does not hold, custody, or control user funds. Wallet keys and transaction approval stay on the user’s device. The interface distinguishes user-owned wallet funds, the community-funded public pool, temporary pending allocations, and completed on-chain transfers. A pending allocation is not a ForkMesh balance or custodial wallet: if no external address is supplied before its displayed deadline, it expires and remains at the external source.

Rewards and availability

Community rewards are voluntary incentives, not investments, wages, yield, or a promise of financial return. Any payout, reward, uptime, or earnings display is experimental and may change. Running a node does not guarantee selection, payment, availability, or data recovery. Visual coins and fountain effects are illustrations; only a finalized transaction on the configured public network represents a completed transfer. You are responsible for backing up your own repositories and keys.

Third parties

We try our best not to use third parties. The current public service still involves a few:

  • Cloudflare for hosting, Workers, D1 storage, caching, and relay infrastructure.
  • A Solana JSON-RPC endpoint for payment-reference lookups.
  • Bundled open-source font files served locally by ForkMesh; no remote font service is used.
  • Tailwind Play CDN on the current home page.
  • The Solana network for payment settlement.
  • Any Git hosting provider or remote repository you choose to mirror.

No warranty

ForkMesh is provided as-is. The software and network may have bugs, outages, incomplete features, or data loss. Use it at your own risk.

Read the privacy notes