Skip to content

join · open peering

Peer your node with the public network.

Quidnug's public network isn't a closed consortium. Anyone running a node can propose bilateral trust with the seeds: we'll tier your blocks as Trusted in the domains you ask for, if you reciprocate and operate responsibly. The protocol's own rules (signed edges, domain scoping, guardian recovery) do the rest.

  1. Get a quid. The whole protocol is keyed off a Quidnug identity. Generate one in your browser at /quid/ if you don't already have one, or use quidnug-cli keygen for an offline CLI-compatible JSON.
  2. Run a node. Use the shipped fly.toml template or any Docker host. Install a 3-of-5 guardian quorum before going public, no guardians, no peering. Operator guide →
  3. Write a signed peering request. JSON envelope, canonical bytes, ECDSA P-256 signature. The SDKs do the canonical-bytes work for you. See the wire spec.
  4. Submit it. Open a GitHub issue on the peering-request template. Or POST to https://api.quidnug.com/v1/peering/requests once the automation lands. Or email peering@quidnug.com. The issue is canonical.
  5. Wait for review. A seed operator verifies your signature, probes your endpoint, and checks the requested domains are within policy. Decision posted as a comment on the issue with tx IDs for the edges. Target: under 72 hours.
  6. Reciprocate. Within 72 hours of approval, publish your own TRUST edges back to the seed in at least peering.network.quidnug.com. Ghosts get revoked.
  7. You're in. Your blocks propagate via gossip. Your node appears on this site under peers. You can see your edges on any seed's chain. Welcome.

What you're committing to

  • A real, attended contact address and operator URL.
  • Uptime at least 95% measured over a rolling 30-day window. We don't slash for outages, but repeated unreachability is grounds for revocation.
  • Guardian quorum installed before peering; annual key rotation.
  • Prompt response to security advisories posted in #network.
  • Revocation with notice when you stop operating.

What the seeds commit to in return

  • Review requests in under 72 hours.
  • Public decision trail (every rejection cites a standardized reason).
  • No unilateral mass revocation without advance notice in #network.
  • Publish advance notice of protocol upgrades via fork-block (QDP-0009).
Open a peering request → Read the full protocol spec Operator guide
The peering protocol is not a contract. Either party can revoke at any time by publishing a trust edge at level 0 in the same domain, or invalidating the epoch they used to sign. Read the revocation section.