M1.1 Local WebSocket-to-TCP bridge (the shim)

[melvincarvalho]

Part of #1 (M1).

Goal

A tiny local process that relays between a browser WebSocket and a Bitcoin TCP peer (port 8333), so a tab can speak the p2p protocol. Target ~100 lines.

Benchmark / acceptance

• From a browser tab, complete a Bitcoin p2p handshake (version/verack) and receive headers and inv from a real peer through the bridge.
• Measure added latency and sustained throughput (MB/s) through the relay.

Notes

Ship as a small downloadable (node script and/or single binary). Document the trust model clearly: the bridge relays bytes only; the tab validates everything. WebRTC/WebTorrent swarming is deferred (see #1).

[melvincarvalho]

Partial: the peer/transport core is done. src/peer.js is a Bitcoin p2p peer over a raw TCP socket using the engine's P2pEngine (handshake, decodeStream framing, ping/pong, waitFor). That is the logic the bridge relays.

Still to do for this issue: the browser-facing WebSocket-to-TCP bridge wrapper (the engine already ships bridge/bridge.js upstream to build on), plus packaging it as a small local download with a documented relay-only trust model.