PQC-gossip Autheo Defensive Console
Single wasm artifact control panel · Browser mode sends via WebTransport bridge (HTTPS/HTTP3 required)
transport: webtransport -> quinn/udp/9001 bridge
Open LB lab

Mission setup

Browser-facing WebTransport URL. Use HTTPS + HTTP/3 bridge endpoints, not raw UDP/9001 listeners.
Optional second WebTransport endpoint for round-robin or mirror tests.
Overrides probes to a specific backend bridge when you need to isolate one node.
Number of ACK metadata samples used to show which backend or LB target answered.
Selects direct, alternating, or mirrored traffic across the primary and optional fallback bridge.
Autheo-provided public DNS name for the LB front door.
Use 443 for Certik / third-party validation unless Autheo provides another port.
Public IP DNS should resolve to; used by host-side DNS diagnostics.
Autheo VPC/private address, useful only for operator-side infrastructure checks.
Raw Quinn UDP backend reached by the LB bridge, not a browser target.
Autheo-provided LB WebTransport endpoint for front-door validation.
What you need to provide: public DNS or IP for your hardware bridge.
Use 443 when possible; 8443 is common for non-root or lab bridge deployments.
Public IP your custom hostname should resolve to for DNS diagnostics.
Private LAN/VPC IP of the custom bridge host behind NAT or firewall.
Raw backend the WebTransport bridge forwards to. Use 127.0.0.1:9001 only when bridge and listener share the hardware host.
Use this if you are testing your own hardware node through its WebTransport bridge.
Primary endpoint UC4 will probe and send traffic to after Apply selected UC scenario.
External Tester Mode · Recommended for Certik / third-party validation
UC4 is the guided path for validating Autheo infrastructure, the load balancer front door, and an operator-supplied hardware bridge or raw QUIC backend.
Autheo test infrastructure
Main bridge:
Load balancer:
Expected path: /pqcnet-gossip
Recommended WebTransport port: 443
Third-party / custom node inputs
Custom bridge endpoint:
Raw QUIC backend peer:
Public host/IP:
Debug/backend peer:
Active transport path: choose UC4 and apply the scenario.
  1. Sender (Node 1+): Initialize wasm -> Install host transport -> Probe bridge TLS/WebTransport -> Send one batch.
  2. Listener (Node 0): Initialize wasm -> Install host transport -> Probe listener hooks -> Start listener.
  3. Use Connect selected role for an automatic role-based setup flow.
  4. Cloud rule: keep PQCNET_RAW_QUIC_PEER=127.0.0.1:9001 only when the bridge and raw listener run on the same host; otherwise point it at the listener's reachable private IP/DNS.
Browser host note: this page can send only to a WebTransport endpoint (HTTPS + HTTP/3). Point the peer field at `pqcnet-webtransport-bridge`, which forwards to raw `pqcnet-super-node` on UDP/9001. Default primary bridge endpoint: `https://bridge.autheolabs.com/pqcnet-gossip`. Default secondary bridge endpoint: `https://lb.autheolabs.com/pqcnet-gossip`.
Cloud quick start: start Node 0/raw listener first, then start the WebTransport bridge, then use this page for Node 1+ sender tests.
If Probe bridge TLS/WebTransport succeeds but Send one batch + ACK fails, the browser reached the bridge but the bridge likely could not reach PQCNET_RAW_QUIC_PEER.
    Guided third-party test flow
      
                

      State + metrics

      Third-party run summary
      Select UC4 to start the guided external tester flow.
      Status: cold start
      Listener hooks: unknown
      Host diagnostics: unknown
      Cloud path: browser -> bridge unknown; bridge -> raw UDP/9001 not validated yet
      TLS cert strategy: unknown
      Backend identity: run "Show backend identity" to sample LB distribution
      Attempts
      0
      Success
      0
      Fail
      0
      avg RTT ms
      n/a
      min RTT ms
      n/a
      max RTT ms
      n/a