rusty_esp_mid-core 0.1.4

MATA mID on the chip, the pure core: a P-256 device did:mata, the byte-identical DeviceSigner, kms nonce assertions, JWS ES256, the self-issued mID token, capability matching, the owner Adoption grant, a replay window and manifest signing. no_std, forbid(unsafe), no drivers.
Documentation
# rusty_esp_mid-core

[![Remade With Rust](https://img.shields.io/badge/Remade%20With-Rust-000?logo=rust&logoColor=fff)](https://github.com/remade-with-rust) [![By Mata Network](https://img.shields.io/badge/by-Mata%20Network-5b2be0)](https://www.mata.network) [![crates.io](https://img.shields.io/crates/v/rusty_esp_mid-core.svg)](https://crates.io/crates/rusty_esp_mid-core) [![docs.rs](https://docs.rs/rusty_esp_mid-core/badge.svg)](https://docs.rs/rusty_esp_mid-core) [![License: MIT OR Apache-2.0](https://img.shields.io/badge/license-MIT%20OR%20Apache--2.0-blue)](https://github.com/Remade-With-Rust/rusty_esp_mid/blob/main/LICENSE-MIT)

The pure half of the identity package: a P-256 device `did:mata`, the byte-identical signer, signed assertions with a replay window, the self-issued token, capability matching, and the owner adoption grant. `no_std`, `forbid(unsafe)`.

Agreement with the wider MATA stack is a test, not an intention: signatures equal the reference signer for the same key, and the capability check agrees with the reference implementation on **144 of 144 cases**.

New in 0.1.4: the signed status a device answers a hub's nonce with -- `status::StatusProof` (`janus-status-v1`, low-s, with a cross-checked vector) and `status::StatusDocument`, the `/v1/status` body; and `settings_adoption`, an owner's adoption delivered with the settings at boot (`apply`: checked, pinned, stored verbatim, cleared) and read back for the status (`stored`).

New in 0.1.3: `seal::SealedKv` keeps secrets sealed at rest behind the same store seam -- AES-256-GCM, each value bound to its key name, a fresh nonce per write -- under a key the chip derives and never stores. A store provisioned in the clear is sealed where it lies; `inner()` hands the store back so a firmware can scrub what the old values left behind.

## Where the evidence is

This crate is part of [`rusty_esp_mid`](https://crates.io/crates/rusty_esp_mid). The
hardware results, the method lines and the open defects live in that package's
[README](https://github.com/Remade-With-Rust/rusty_esp_mid#readme) and in
[`docs/LEDGER.md`](https://github.com/Remade-With-Rust/rusty_esp_mid/blob/main/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](https://www.mata.network) 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`](https://crates.io/crates/rusty_esp_core) · [`rusty_esp_dsp`](https://crates.io/crates/rusty_esp_dsp) |
| **1 — the functions** | [`rusty_esp_image`](https://crates.io/crates/rusty_esp_image) · [`rusty_esp_video`](https://crates.io/crates/rusty_esp_video) · [`rusty_esp_audio`](https://crates.io/crates/rusty_esp_audio) · [`rusty_esp_signal`](https://crates.io/crates/rusty_esp_signal) · [`rusty_esp_mid`](https://crates.io/crates/rusty_esp_mid) · [`rusty_esp_iroh`](https://crates.io/crates/rusty_esp_iroh) |
| **2 — the surfaces** | [`rusty_esp_arduino`](https://crates.io/crates/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](https://github.com/remade-with-rust) — including
[`rusty_alloc`](https://crates.io/crates/rusty_alloc), the pure-Rust rebuild of
mimalloc that these firmwares run on, and
[`rusty_jpeg`](https://crates.io/crates/rusty_jpeg), the JPEG engine behind the
camera path — and our sister project
[remade_ffmpeg_rs](https://github.com/Remade-With-Rust/remade_ffmpeg_rs), a ground-up Rust rebuild of FFmpeg.

## About Mata Network

[Mata Network](https://www.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](https://github.com/Remade-With-Rust/rusty_esp_mid/blob/main/LICENSE-MIT)
and [LICENSE-APACHE](https://github.com/Remade-With-Rust/rusty_esp_mid/blob/main/LICENSE-APACHE).