glm-5.2
8692f9748e
Adds three sections filling the conceptual gaps in the phase-0 findings: - Hub Motivation: The Multi-Transport Collapse — diagnoses the O(protocols × transports × spokes) mess the hub crate faces and shows how channels collapses it to one connection per leg with channel-by-channel byte forwarding, reusing the call protocol's auth/forwarded-for model. - Channel Open Negotiation — concrete channel/open, channel/close, channel/control, channel/resources operation payloads with field tables, error codes as CallError strings, bidirectional open semantics, and the end-to-end ACL flow for browser→hub→spoke. No new wire framing; all four operations register on the call protocol's existing OperationRegistry. - Channel Manager and Connection Internals — the ChannelsAdapter/ ChannelManager split, ChannelManager state sketch, ChannelsAdapter::handle read/demux loop with channel 0 preinstall, the channel/open handler closure threading into OperationRegistry, ChannelConnection as a Connection via the existing from_stream path, the hub relay as ChannelManager-to-ChannelManager byte pumping, and the boundary (ChannelManager holds no handlers, no ALPN parsing, no auth, no transport coupling). Also adds four new open questions (OQ-CH-08 through OQ-CH-11) on resource staleness, responder-to-initiator lifecycle, typed destructure ownership, and hub relay channel_id remapping; two new POC stretch goals (hub relay, channel/resources); and updates the opening to note the revision scope.
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.