Interaction between two fixes in this series. The host now tells the client when
a rebuild re-resolves an Automatic rate, and that rate can legitimately sit ABOVE
the client's climb ceiling — the ceiling is the negotiated start rate until the
capacity probe raises it, while the host's re-resolve answers "what do these
pixels actually need" (a 1080p session mirroring a 4K panel resolves ~3× higher).

Left alone, the client would learn the new rate, notice it was above a stale
ceiling, and step the host straight back down off the rate it had just chosen
for itself. So an ack raises the ceiling to meet it. `set_ceiling` only ever
raises and still clamps to PUNKTFUNK_ABR_MAX_MBPS, which is the one limit that
should bind here. No effect on ordinary acks: a climb is never requested above
the effective ceiling to begin with.

2026-08-03 18:53:02 +02:00

benches

feat(core+host): negotiate ChaCha20-Poly1305 as the session cipher for soft-AES clients

2026-07-21 22:50:00 +02:00

src

fix(client/abr): let the ceiling follow a host-initiated re-target

2026-08-03 18:53:02 +02:00

tests

feat(core+host): negotiate ChaCha20-Poly1305 as the session cipher for soft-AES clients

2026-07-21 22:50:00 +02:00

vendor/fec-rs

fix(core): remaining 15 sweep lows — client, clipboard, C ABI (v10), FEC, GSO, GTK

2026-07-20 18:26:43 +02:00

build.rs

chore(core): fix build.rs + crate-doc drift left by the W7/W8 splits

2026-07-20 18:08:39 +02:00

Cargo.toml

chore(unsafe): the workspace adopts the drivers' unsafe discipline

2026-07-28 21:31:41 +02:00

cbindgen.toml

fix(core,host): make the native data plane survive real Wi-Fi links

2026-07-07 07:35:08 +02:00

README.md

docs: repo-wide housekeeping — sync README & docs with the code as shipped

2026-07-10 09:13:42 +02:00

README.md

punktfunk-core

The shared protocol core — the one place where punktfunk's transport, forward error correction, and crypto live. It's linked into the host and every native client, so there's exactly one implementation of the wire format everywhere.

Written in Rust with no async on the per-frame path (native threads only). It exposes both a normal Rust API and a stable, versioned C ABI, so the Swift and Kotlin clients — and any C embedder — link the same code as the Rust ones.

What's in here

Transport & session (session.rs, transport/, packet.rs) — the punktfunk/1 data plane over raw UDP: packetization, reassembly (with attacker-bounded limits), pacing, and socket tuning.
FEC (fec/) — the wall-breaker. Two codes:
- GF(2⁸) classic Reed–Solomon with the Cauchy generator matrix — byte-identical to the nanors library Moonlight uses, so our parity is decodable by a stock Moonlight client.
- GF(2¹⁶) Leopard-RS (SIMD, O(n log n)) — up to 65535 shards/block, which removes the ~1 Gbps FEC ceiling. punktfunk/1 negotiates this one.
Crypto (crypto.rs) — AES-128-GCM session encryption with per-direction nonce salts and sequence-as-AAD; SPAKE2 PIN pairing lives behind the quic feature.
QUIC control plane (quic.rs, client.rs, feature quic) — the Hello/Welcome/Start handshake, cert pinning/TOFU, reverse audio, and the embeddable NativeClient connector. This is the only place tokio/quinn are allowed; the feature is off by default so the core stays runtime-free.
C ABI (abi.rs) — the versioned surface (punktfunk_abi_version(), PunktfunkConfig carrying its own struct_size) that generates include/punktfunk_core.h via cbindgen at build time.

Build outputs

The crate builds three ways at once (crate-type = ["lib", "cdylib", "staticlib"]):

Output	Used by
`lib` (rlib)	the host, probe, and tools link it as a normal Rust crate
`cdylib` (`.so`/`.dylib`)	the Swift / Kotlin clients via the C ABI
`staticlib` (`.a`)	the C test harness and static embedding

Test

cargo test -p punktfunk-core                 # unit + proptest + loopback
cargo run  -p loss-harness                   # FEC loss-resilience sweep (no network needed)
bash crates/punktfunk-core/tests/c/run.sh    # standalone C-ABI link + round-trip proof

Design invariants (do not regress)

One core, linked everywhere — protocol/FEC/crypto live only here, behind the stable C ABI.
No async on the hot path — the per-frame pipeline is native threads only; quic (tokio/quinn) is control-plane only, feature-gated, off by default.
Security hardening stays intact — the reassembler bounds attacker-controlled fields before allocating; AES-GCM keeps per-direction nonce salts + seq-as-AAD; the ABI checks struct_size. Regression tests exist — keep them green.

punktfunk-host — the streaming host built on this core
Clients — the apps that link this core over the C ABI (or directly, in Rust)
punktfunk-planning: implementation-plan.md (internal planning repo) — why GF(2¹⁶) FEC, the latency budget, and the architecture thesis

README.md Unescape Escape

punktfunk-core

What's in here

Build outputs

Test

Design invariants (do not regress)

Related

README.md