You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Decision: shipped localhost bridge vs ADR-0001 native messaging — re-scope #49/#50 and write the missing ADR #202
Resolved 2026-07-10 → ADR 0006. Decision recorded below; this issue can close once the ADR merges and #49/#50 bodies are updated.
Problem
ADR-0001 prefers a native-messaging wire and names the localhost port the rejected alternative (docs/adr/0001-dapp-connectivity-architecture.md:82-89, :148-152) — but the localhost wire is what shipped (#62/#63/#139/#141/#146/#148): a hand-rolled loopback HTTP server hardcoded to 127.0.0.1:8765. #49 (spike) was written to compare the two before any wire existed; #50 (PRD-04) specs the native-messaging end state. The plan and the shipped code disagreed, and no ADR recorded the shipped experimental wire.
Decision (2026-07-10)
Recorded in ADR 0006:
Accept the shipped 127.0.0.1:8765 loopback bridge as the alpha transport — explicitly temporary/experimental. Do NOT invest heavily in hardening it now (no token auth / DNS-rebinding work beyond the existing loopback Host check).
Priority = the two ends, not the pipe:deckard-core signing + the browser extension working and tested end-to-end. The transport is a swappable constraint we expect to replace.
Acceptable only because the alpha is testnet-keys-only per SECURITY.md; does not survive real value.
Activity
docs(bridge): #202 · ADR 0006 localhost transport + fix stale browser…
hellno commentedon Jul 13, 2026
All acceptance items done — closing.
docs/adr/0006-localhost-dapp-bridge-transport.md).127.0.0.1:8765loopback bridge is the temporary alpha transport; native messaging is the post-audit replacement, not the first wire.main.