glm-5.2
5e07203b86
Adds docs/research/alknet-channels/poc-plan.md — a standalone three-step POC plan that derisks the channels layer in isolation (no call protocol, no real transport, no real adapters): - Step 1: chunk format + N-channel demux/mux — generalizes TTY's 5-byte ChunkReader/ChunkWriter to the 9-byte format, validates decompose→stream→ recompose for 3+ concurrent channels with the sync-core/async-shell split pattern from TTY's REQ-TTY-01. - Step 2: per-channel Connection presentation — wraps each reassembled channel as Connection::from_stream and runs a minimal echo ProtocolHandler through the full path. Validates the existing Connection abstraction is sufficient; no core changes needed for the POC. - Step 3: tunnel handler — opens a TcpStream and pumps bidirectionally, reusing TTY's pump_session shape with two pumps. Validates the same concepts behind the TTY crate work as a generic port proxy. Stretch goals: WASM build of the sync core, mixed channel types on one connection, hub relay sketch with channel_id remapping. Adds three open questions to phase-0-findings.md: - OQ-CH-12: unknown channel_id on demux (lenient drop vs strict error). - OQ-CH-13: core BidiStreamSource trait — additive refactor to make ChannelConnection a first-class peer of QUIC (many bidi streams) rather than a bag of yield-once Connections. Likely +EV; not needed for the POC but should be evaluated in Phase 1. - OQ-CH-14: client-side channels endpoint — the symmetric ChannelClient type (analogue of AlknetEndpoint vs CallClient). After the POC we're probably going to need some light refactoring to the core to make these easier; mostly additive and not breaking in major/pita ways. Updates phase-0-findings.md De-risk POC section to point at the detailed plan and adds the poc-plan to References.
Alknet
Status: Pre-alpha — This project is undergoing a major architectural pivot to an ALPN-as-service model. The previous implementation has been archived and a greenfield rebuild is in progress.
A self-hostable networking toolkit built on QUIC+TLS with ALPN-based protocol dispatch. Each protocol handler (SSH, SFTP, Git, HTTP, DNS, messaging, call protocol) registers an ALPN string on a shared endpoint. The ALPN negotiation during the TLS/QUIC handshake routes connections to the correct handler before any application bytes are read.
Core Insight
A service IS an ALPN. One endpoint, one port, many protocols — dispatched by the TLS handshake, not by application-level peeking or separate listeners.
Crates
| Crate | Status | Description |
|---|---|---|
alknet-vault |
stable | Local key vault: BIP39/SLIP-0010/AES-GCM key derivation and encryption |
alknet-core |
planned | ProtocolHandler trait, ALPN router, auth/identity, config |
alknet-ssh |
planned | SSH handler (russh), SOCKS5, port forwarding |
alknet-call |
planned | JSON-RPC call protocol (EventEnvelope framing) |
alknet-fs |
planned | Content-addressed file storage (iroh-blobs backend) |
alknet-sftp |
planned | SFTP handler (russh-sftp protocol core) |
alknet-git |
planned | Git smart protocol handler (gix) |
alknet-http |
planned | HTTP handler (axum, REST API, MCP) |
alknet-dns |
planned | DNS handler (hickory-proto, pkarr) |
alknet-msg |
planned | E2E encrypted messaging, mixnet support |
alknet |
planned | CLI binary (assembles and registers handlers) |
Documentation
- ALPN-as-service architecture — pivot proposal
- Cleanup plan — greenfield transition plan
- SDD process — spec-driven development process
- Research references — iroh, russh, russh-sftp deep dives
Reference implementation (previous architecture) is preserved at /workspace/@alkdev/alknet-main/.
License
Licensed under either of
- Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.