Remade with Rust
rusty_esp_mid: device identity on the chip
mID on the chip — device DID, encrypted NVS or eFuse keys, owner adoption as a signed grant
Replaces: Vendor provisioning / cloud device claiming
What is rusty_esp_mid, device identity on the chip?
rusty_esp_mid is mID on the chip. A device DID, keys in encrypted NVS or eFuse, and owner adoption as a signed grant replace vendor provisioning and cloud device claiming.
What rusty_esp_mid replaces
rusty_esp_mid is device identity on the chip. The device has a DID, keys live in encrypted NVS or eFuse, and an owner adopts it with a signed grant.
Why rusty_esp_mid is a device identity on the chip
What rusty_esp_mid keeps from Vendor provisioning / cloud device claiming
rusty_esp_mid keeps claiming a device as a signed act. Vendor provisioning and cloud device claiming are what it replaces.
Where rusty_esp_mid fits
rusty_esp_mid is the chip half of mID and Sovereign ID. rusty_esp_iroh carries the mesh. A frame from the other ESP crates can be signed because this crate exists.
Read more about rusty_esp_mid
- All Remade with Rust rebuilds
- Freedom Guide
- Vision
- mID — server-side Sovereign ID verifier
- rusty_esp_iroh — iroh mesh on ESP32
- Learn article on rusty_esp_mid
- rusty_esp_mid on GitHub