E04-RT: Yes
Rationale
MeshCam/Clover Hill publishes field delivery timings for Reticulum-over-LoRa probes: 5 KB payloads, gateway-side reception records, quiet/busy-channel conditions and sample counts. Its surveyor build uses the separately maintained attermann/microReticulum library, pinned at c02b6e3d985567cced4450fb65902106ebda5a39 with a disclosed local patch. The measured shared mechanism is Reticulum Resource delivery. Revised E04 accepts this external application team’s quantitative observation of an existing protocol implementation, with the implementation and measurement limits below.
Assessment method
Revised E04 documentary assessment of external Resource delivery measurements
Source context
MeshCam field measurements, surveyor build and microReticulum upstream
Outstanding qualification
These are manufacturer-reported observations of its own application, using a third-party protocol library; no neutral product comparison is claimed. The build applies a transport deadlock patch and disables persistent packet-hash storage. It is not unmodified Python RNS. Published timings cover one radio hop, not multihop routing or global scale. Raw logs were not obtained, experiments were not repeated, and current build settings are not proof of every historical field setting. No camera range, energy, security, interoperability or selected-profile performance certification is inferred. Independence rests on disclosed project provenance, not an exhaustive contributor audit.
Public sources
- https://docs.getmeshcam.com/numbers
- https://github.com/meshcam/meshcam-firmware
- https://github.com/attermann/microReticulum
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round627.html
- round627-sources.json