Submit a hub

Submit an intentionally public Direct Connect hub for independent verification.

Manual submission

Supported protocols: ADC (adc://), ADCS (adcs://), NMDC (dchub://) and NMDCS (nmdcs://). Use the hub's public, reachable address.

Acceptance queues independent testing. It does not promise instant publication.

Register from your hub

Luadch-ng operators can announce a hub with etc_regserver_announce.lua. Only announce an intentionally public hub. Configure a real hub_hostaddress and a reachable advertised TCP/TLS port, load and enable the plugin, and allow outbound HTTPS.

  1. Configure plugin settings

    Add this excerpt inside your existing cfg/cfg.tbl table:

    etc_regserver_announce_activate = true,
    etc_regserver_announce_url = "https://hublist.eu/register",
    etc_regserver_announce_tls_verify = true,
    etc_regserver_announce_cafile = "/etc/ssl/certs/ca-certificates.crt",

    The CA path shown is a Debian/Ubuntu example. Use a platform-correct PEM CA bundle that exists on the hub's operating system. Keep TLS verification enabled.

    Preserve existing registration targets (optional)

    If the operator already announces to other lists, preserve the operator's existing target with the optional URL-array form. Replace the labelled placeholder below with that existing URL:

    etc_regserver_announce_url = {
      "https://hublist.eu/register",
      "https://operator.example/existing-registration-target", -- operator's existing target
    },
  2. Apply and verify

    Reload or restart the plugin as your Luadch-ng installation requires, then check the hub logs for the registration result. Acceptance only queues independent testing. After a successful unchanged announcement the plugin normally stops announcing it; the hublist pinger maintains liveness, so periodic announcement is not required.

Official Luadch-ng plugin documentation