Files

glm-5.1 13b0991fb8 Resolve all architecture open questions, add 13 ADRs, update specs

Resolved all 11 open questions based on project guidance:

Transport:
- OQ-01/OQ-07: ACME/Let's Encrypt with domain + IP paths (ADR-008)
- OQ-02: Default to n0 relay, --iroh-relay override (ADR-009)
- OQ-05: Transport chaining supported natively (ADR-010)

Client:
- OQ-06: Programmatic-first API, no ~/.ssh/config (ADR-011)

Server:
- OQ-04: Ed25519 + OpenSSH cert-authority, no password auth (ADR-012)
- OQ-08: fail2ban-friendly logging + built-in rate limiting (ADR-013)

TUN:
- OQ-03/OQ-09: Deferred entirely, recommend tun2proxy (ADR-014)
- tun-shim.md marked deprecated

NAPI:
- OQ-10: Expose both connect() and serve() (ADR-016)
- OQ-11: Use napi-rs for FFI bridge (ADR-015)

Additional ADRs created during review:
- ADR-006: No logging of tunnel destinations (was phantom reference)
- ADR-017: Stealth mode protocol multiplexing
- ADR-018: Control channel for pubsub over SSH

Fixed: ADR-002 status → Superseded, ADR-007 title typo,
WRAUTH_SERVER typo, ADR-005 stale wraith-tun refs,
undefined ACL feature removed from server.md,
--proxy semantic difference documented.

2026-06-01 17:31:28 +00:00

1.5 KiB

Raw Blame History

ADR-009: Default iroh Relay with Override

Status

Accepted

Context

iroh requires a relay server for NAT traversal and initial connection establishment. The n0 project provides free relay servers (https://relay.iroh.network/) that work out of the box. However, relying on a third-party service creates a dependency:

n0's relay could change terms, rate-limit, or go down
Production deployments may want self-hosted relays for reliability and privacy
The relay URL is a configuration point that should be explicit

Conversely, requiring users to set up a relay server before they can use iroh transport is a significant friction point for testing and quick starts.

Decision

Default to n0's relay servers. Allow override via --iroh-relay <url> CLI flag. Document self-hosted relay setup in project documentation.

This matches iroh's own defaults — n0's relay is the standard starting point. Users who need production reliability self-host.

Consequences

Positive: Zero-config iroh transport for testing and development. wraith serve --transport iroh just works.
Positive: Self-hosting is a single flag override, not a complex setup requirement.
Negative: Default depends on n0's infrastructure. If n0's relay is down, default iroh connections fail (but this is the same experience as every iroh user).
Negative: Privacy-conscious users must remember to --iroh-relay to avoid n0. Mitigated by documentation.

References

transport.md
OQ-02 — resolved by this ADR

1.5 KiB Raw Blame History