rusty_esp_mid-esp 0.1.4

Chip backends for rusty_esp_mid: the WRAP crate. `esp-idf` (Track A) gives the device key a home in NVS behind the Kv seam, with the encryption check the plan demands, and the TRNG behind Rng; `esp-hal` (Track B) lands with its drivers. The only crate in the workspace allowed a fenced unsafe block, and only at an FFI boundary.
Documentation

rusty_esp_mid-esp

Remade With Rust By Mata Network crates.io docs.rs License: MIT OR Apache-2.0

The chip backends for the identity package: the device key's home in the chip's key-value partition behind the store seam, with the encryption check the plan demands, and the hardware entropy source behind the entropy seam. On Track A (esp-idf) that is ESP-IDF's NVS and TRNG; on Track B (esp-hal) it is the same identity partition read and written by rusty_esp_core::nvs — Espressif's NVS format in pure Rust — over esp-storage, and esp-hal's TRNG. A key minted on one track is read on the other.

New in 0.1.4: nothing of its own; it moves with mid-core 0.1.4, the set released together.

New in 0.1.3: hal::seal_key (feature seal-hmac) derives the sealing key from the HMAC peripheral and an eFuse key block, so the key never sits in flash; the partition table is read where the build put it (ESP_BOOTLOADER_ESP_IDF_CONFIG_PARTITION_TABLE_OFFSET), and through the cache under flash encryption.

New in 0.1.2: EspNvsKv reads a value written as an NVS string as well as a blob (what the owner's settings image holds), and hal::shared keeps several partitions open on one flash at once -- the owner's settings and the identity, as the Janus setup session holds them.

The entropy source is named in the code rather than assumed: without the analogue-backed path, the chip's generator is a pseudo-random register, and this crate refuses rather than pretending.

Where the evidence is

This crate is part of rusty_esp_mid. The hardware results, the method lines and the open defects live in that package's README and in docs/LEDGER.md, where no number appears without the run that produced it.

Part of Janus

Janus rebuilds the Espressif ESP32 and Arduino application portfolio as independent, memory-safe Rust packages — so a hardware maker can ship a device that the MATA home computer discovers, catalogs honestly, adopts under its own identity, and pays for. Ten packages, three layers, and the dependency direction never reverses.

layer packages
0 — the vocabulary rusty_esp_core · rusty_esp_dsp
1 — the functions rusty_esp_image · rusty_esp_video · rusty_esp_audio · rusty_esp_signal · rusty_esp_mid · rusty_esp_iroh
2 — the surfaces rusty_esp_arduino — the sketch facade · espino — the maker's CLI (not published)

Every package is host-verified against an external oracle and keeps a ledger in which no number appears without the run that produced it. Five of seven device profiles have now run their kill tests on real silicon, three of them over a Wi-Fi network the board hosts itself.

Also check out the rest of Remade With Rust — including rusty_alloc, the pure-Rust rebuild of mimalloc that these firmwares run on, and rusty_jpeg, the JPEG engine behind the camera path — and our sister project remade_ffmpeg_rs, a ground-up Rust rebuild of FFmpeg.

About Mata Network

Mata Network builds sovereign, self-hostable infrastructure. Remade With Rust is our open-source home for the permissively-licensed building blocks that work depends on.

License

MIT OR Apache-2.0, at your option. See LICENSE-MIT and LICENSE-APACHE.