rusty_zstd: Pure-Rust Zstandard Compression

Pure-Rust Zstandard (RFC 8878) compressor and decompressor. Zero dependencies, no C, no FFI, no copyleft.

rusty_zstd is a core repository in the Memory band of Remade with Rust. It exists so developers can ship real products on memory-safe primitives instead of babysitting libzstd on every release train. This article is the builder brief: what the crate is for, how it plugs into the constellation, which businesses can form around it, and how it deploys toward MATA.NETWORK.

For the portfolio thesis, read The Importance of Remade With Rust. For the map, open Vision. Filter Learn by Memory to see sibling field notes.

What rusty_zstd Is For

Problem it inherits

Internet products still lean on libzstd in places customers never see: upload forms, firmware, auth callbacks, allocators, model runtimes. Those dependencies decide your CVE inbox and whether wasm32 or ESP targets are even reachable.

What Remade changes

rusty_zstd is maintained at https://github.com/Remade-With-Rust/rusty_zstd as a Remade-with-Rust building block. The doctrine is the same across the org: prefer pure Rust on the hot path, keep formats and protocols familiar, and leave a clean seam for mesh deployment. That is how rebuilding the foundation of the internet becomes a shipping checklist.

Who should adopt it first

Teams that already feel the cost of libzstd: regulated buyers asking about memory safety, embedded devices that cannot carry a C toolchain, and startups that want one codebase from laptop to neighborhood node.

How It Interacts With the Constellation

Inside Memory

Related Learn guides: spacedb, remade-ffmpeg-rs, rusty-erasure. Treat them as composition hints, not a forced monorepo. Most products pick two or three crates and grow.

Across clusters

• Media feeds bytes into Mind engines and Edge sensors.
• Memory stores indexes and replicas beside the user (SpaceDB, rusty_alloc).
• Identity gates who may call your API (mID, Sovereign ID).
• Trust keeps the dependency graph honest (Deputy) before you place a binary on hardware you do not babysit.

That graph is the practical answer to why Digital Freedom needs Rust: ownership fails if any layer still smashes the stack or phones a landlord by default.

Business Opportunities and Implementations

Offer local-first sync, wasm-safe allocation, or compression that does not drag libzstd into regulated environments. Price vaults and replicas, not idle cloud databases.

Concrete implementation patterns

1. Library embed: add rusty_zstd behind a stable facade in your Rust service or firmware; keep HTTP/JSON at the edge.
2. Appliance SKU: ship a NUC or ESP kit where rusty_zstd is the differentiator (safer decode, local ASR, on-chip identity, offline DB).
3. VPC / on-prem mirror: same binary customers run in their network, aligned with NIST SSDF memory-safe guidance.
4. Mesh preview: integrate now against Preview hosting; keep disco placement as a config switch on MATA.NETWORK.

What not to sell

Do not market rusty_zstd as a purple SaaS wrapper around the old C stack. The warranty only holds if the hot path is actually Remade.

Deploying Onto MATA.NETWORK

MATA.NETWORK is the distributed-cloud home for this portfolio: identity, storage, and mesh seams you can build against while hosting is still Preview. rusty_zstd should land as:

1. A placeable artifact (native service, wasm module, or firmware image).
2. Capability-gated with mID so strangers cannot invoke it on a neighborhood node.
3. State nearby in SpaceDB when the crate produces user data.
4. Supply-chain scanned with Deputy before disco place.

External references worth keeping in your design doc: the Remade-With-Rust org, mata.network, and language/memory-safety policy texts such as NIST SSDF. Internal next steps: Vision, Learn filter Memory, and the related articles linked above.

rusty_zstd is not a slide. It is a dependency you can put in Cargo.toml and a story you can put in a procurement appendix. That combination is the business.