What dldeploy's MATA Home seam does not show yet

What the note is claiming

On October 12, 2026, dldeploy described a MATA Home integration that is being built, not a switch that already places every ESP32 on the Home screen. The claim is that a local board can speak a protocol the home computer already understands, so Home does not need a second cloud account to notice it. The note names that protocol mata-oem-sidecar/rpc/1, a JSON seam over iroh. Cataloging the device is the sentence the note says it can carry. Playing a camera inside Home is a later sentence, and the note says that wire is still open. The paper filing the limit isFutureweb.

What has been measured, and on which board

The note's measured mesh run used a laptop as the subscriber. It says a Seeed XIAO ESP32-S3 Sense was up 3.2 seconds after boot and delivered 721 camera packets in 60 seconds, with none lost and none out of order. It says the C6 firmware builds and has not had that run. It says a board with 4 MB of flash, such as the ESP32-CAM, does not run iroh and instead reaches the mesh through a bridge on a neighboring machine. The bridge holds the session and does not hold the neighbor's key. The desk for a home computer that is the system of record isDistributed Cloud.

What identity the seam assumes

The note says the device mints a P-256 did:mata on first boot and that the owner pins a key. It says that on a real chip a stranger presenting the owner's own record was refused, and so was an older record a key rotation had replaced. That is the ownership half. It also says development firmware can still store the identity key in a plaintext partition, and that after adoption a device can still advertise itself as free to claim because that record is composed once at boot. A content address, the standing distributed-systems identifier, iswhat a content address is.

Why it matters on this desk

The dependency is whether the household computer, not a vendor account, is the thing that lists the device. The note's answer is that the listing seam is named and the picture inside Home is not finished. Reach from outside the house is not a measured row. The note says a relay path is written and that no relay has been dialed from a board. What local control requires, on the device side of the same house, iswhat local control requires.

What this page will not import

This page does not say every ESP32 runs the node. The note draws a flash-size line at 8 MB for the std-track node and a bridge for 4 MB and for bare-metal boards. It also says there is no C in the house crates, and that the Wi-Fi radio is still Espressif's binary blob, so a promise of a C-free radio would be false. The mechanism note isdldeploy's MATA Home note.

Where the public record sits

The integration note is one source. The DID Core recommendation is the public definition of a decentralized identifier as an identifier the subject can control without a central registry. Espressif's Wi-Fi guide is the vendor description of the radio the note says it does not replace. None of those three documents shows a finished Home media view. The note says so in its own status. Turn the WAN off and leave the LAN up, the note says, and the measured path still has an owner. That is the LAN test it is willing to claim. Turn the WAN off and leave the LAN up, the note says, and the measured path still has an owner. That is the LAN test it is willing to claim.

What to watch next

A measured run where the home computer's media controller receives the stream, or a relay dialed from a board, would replace the open rows. Another paragraph that repeats the 721 packets would not. What a process node measures is a different hardware fact,what a process node measures.

What would change the record

A retraction of the plaintext-key limit, or a silicon run on a board other than the XIAO ESP32-S3 Sense, would change it. A claim that 4 MB boards run iroh themselves would contradict the note. A screenshot of a laptop client would not become the Home screen. The note says a camera page answers 403 without a token tied to the device identity. Sharing the Wi-Fi password is not the same as an invitation to the camera. Presence builds compile, the note says, and have not run as a verified device, so they are not part of the measured claim. The note says a camera page answers 403 without a token tied to the device identity. Sharing the Wi-Fi password is not the same as an invitation to the camera.

What stays unfinished on purpose

What stays specific is an October 12 status: protocol seam named, Home picture not wired, one board measured on silicon, 4 MB boards behind a bridge, off-LAN reach unmeasured, identity key still plaintext on current development firmware. The household computer is the intended catalog. It is not yet the viewer. Presence builds compile, the note says, and have not run as a verified device, so they are not part of the measured claim. The note says a camera page answers 403 without a token tied to the device identity. Sharing the Wi-Fi password is not the same as an invitation to the camera.