- CallAdapter struct with registry, identity_provider, session_source, default_timeout (30s) - new(), with_session_source(), with_timeout() constructors - SessionOverlaySource trait defined (overlay_for) for agent-crate integration - ProtocolHandler::alpn() returns b"alknet/call" - handle() sets connection identity from AuthContext, spawns accept_bi loop, reads EventEnvelope frames via FrameFramedReader, dispatches call.requested to the operation registry, writes ResponseEnvelope as EventEnvelope via FrameFramedWriter - Per-request identity resolution: AuthContext.identity used by default, auth_token in payload overrides via IdentityProvider::resolve_from_token(); resolution failure falls back to connection-level identity - build_root_context sets internal: false, deadline (now + default_timeout), capabilities and scoped_env from registration bundle, parent_request_id: None - compose_root_env builds CompositeOperationEnv (Layer 0 curated base + Layer 2 connection overlay + optional Layer 1 session overlay) - operationId leading slash stripped before registry lookup - ResponseEnvelope -> EventEnvelope conversion (Ok -> call.responded, Err -> call.error) - PendingRequestMap sweeper runs every 10s, evicts expired wire entries - Connection drop: fail_all pending with INTERNAL "connection closed", return Ok(()) - Stream reset: FrameFramedReader error closes stream; other streams unaffected - Handler panic: stream task isolated via tokio::spawn, sweep cleans entry - Tests: alpn, constructors, slash strip, identity resolution (override/fallback), root context (internal=false, deadline, capabilities, scoped_env), env composition (layers aggregate, session overlay), dispatch round-trip, internal op from wire -> NOT_FOUND, ACL denied -> FORBIDDEN, auth_token overrides connection identity, unknown op -> NOT_FOUND, no-slash resolution, ResponseEnvelope -> EventEnvelope conversions
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.