What the XIAO mesh note has actually run

What the note measured

The rusty_esp_iroh field note says a Seeed XIAO ESP32-S3 Sense has run the node on silicon, on a Wi-Fi network the board hosted itself. It says the node 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 boards with PSRAM are the relay tier and boards without it are LAN-direct. It says the relay path compiles and has not been dialed on a board. The note is the rusty_esp_iroh field note.

What the note says about flash

The note says the S3 LAN-tier image is 4,660,544 bytes, that turning relays on adds 106,240 bytes, and that the C6 LAN-tier image is 4,575,232 bytes. It says none of these fit a 4 megabyte part, so 8 megabytes is the practical floor, and a board like the ESP32-CAM reaches the mesh through a bridge. A process node, a different hardware fact, is what a process node measures.

What the vendor documents

The silicon result is one board: a XIAO ESP32-S3 Sense, on a network the board hosted, up in 3.2 seconds, 721 camera packets in 60 seconds, none lost and none out of order. The flash figures are the note's as well: 4,660,544 bytes for the S3 LAN image, 106,240 more with relays, 4,575,232 bytes for the C6 LAN image. Those sizes are why the note calls 8 megabytes the practical floor and sends a 4 megabyte board, such as an ESP32-CAM, through a bridge. The bridge sentence is a scope line: sessions, a neighbor's own signed manifest, and never the keys. It is not a recipe. The relay tier is the sentence the note will not upgrade: the path compiles and has not been dialed. Espressif's guide documents the chips and not these counts. Maia's 2027 schedule is a different piece of silicon and a different document. Until a second board is in the note, the measured tier is the XIAO on the LAN. A compile is not a session. The note is careful about that, and this page stays as careful. The 721 packets are a LAN result on one board. They are not a relay result, and they are not a promise about a 4 megabyte module. Espressif's programming guide documents the chip families the note is sorting into tiers. The guide does not contain the 721-packet count or the image sizes. Those are the field note's measurements on a firmware the vendor did not ship. The desk is Hardware.

Why it matters on this desk

The dependency is a board that has actually run, and a path that has only compiled. The XIAO measurement is a silicon result. The relay is a plan with a byte cost and no dialed session. A reader who buys a 4 megabyte board because the headline said mesh has skipped the floor the note printed. A thermal limit, which this flash floor is not, is what a thermal limit stops.

What this page will not describe

Read together, the filed pages are the record, and a later paraphrase would not replace them. The note says a bridge relays a neighbor's signed manifest, holds sessions, and never holds keys. That is a scope sentence. It is not a build guide, and this page will not add commands. Maia 300, a different silicon schedule from the same day, is what Microsoft's October 12 Maia post schedules.

Where the documents split

The field note has the timings, the image sizes, and the undialed relay. The chip guide has the vendor's description of the parts. A public mesh project can explain the protocol the firmware is using and still not contain this board's packet count. The overlap is the chip. The measurement is the note. The front of the paper is Futureweb.

What to watch next

A dialed relay session on a PSRAM board would replace the compiles-but-not-dialed sentence. A C6 or a 4 megabyte part that runs the image would replace the floor. Another restatement of the 721 packets would not. The XIAO result stands until the note revises it. A figure that is not in those pages is not in this brief.

What would change the record

If the note revises 3.2 seconds or 721 packets, those figures move. If it reports a dialed relay, the plan becomes a measurement and this page's caution expires. The vendor guide can stay stable through both, because it never hosted the firmware result. That is why the byte counts stay attributed.

What stays a silicon result

What stays specific is one board. The field note says a XIAO ESP32-S3 Sense ran the node, was up 3.2 seconds after boot, and delivered 721 camera packets in 60 seconds with none lost and none out of order, on a network the board hosted. It says the S3 LAN image is 4,660,544 bytes, relays add 106,240, the C6 LAN image is 4,575,232 bytes, and 8 megabytes of flash is the practical floor. It says the relay path has not been dialed on a board, and that a bridge holds sessions and never keys. Espressif's guide documents the chips and not these counts. This page does not add a command, a second board result, or a claim that a 4 megabyte module can host the image. The measured tier is the XIAO on the LAN. The relay is still a compile.