Status

What is built in matter-kit and what is not, layer by layer, mapped to the sections of Matter 1.6 that define it.

On this page

Under construction and pre-1.0. A device can be commissioned into a fabric end to end — over IPv6, Bluetooth LE, Wi-Fi PAF or NFC — answer Reads, Writes and Invokes against a const data model, hold subscriptions, record and report events, take part in groupcast, and move a firmware image over TCP. What is missing is most of the application clusters’ behaviour.

✅ built and tested · 📐 designed, not written

Transport and secure channel

LayerSpecificationState
TLV wire formatCore Appendix A✅
Message frame, counters, replayCore §4.4, §4.6✅
Message security and privacyCore §4.8, §4.9✅
Exchanges, Message Reliability ProtocolCore §4.10, §4.12✅
Cryptosuite, SPAKE2+, key custodyCore ch. 3✅
PASE, StatusReportCore §4.11, §4.14.1✅
CASE, with resumptionCore §4.14.2✅
Secure sessionsCore §4.13✅
Session eviction, and CloseSession in both directionsCore §4.11.1.1, §4.11.1.4✅
Session parameters, all nine fieldsCore §4.13.1✅
BTP: segmentation, receive window, keep-aliveCore §4.19✅
BLE GATT service, commissionable advertisementCore §4.19.4.2, §5.4.2.5✅
TCP transport: stream framing, no MRP, large payloadsCore §4.5, §4.15✅
BDX: negotiation, block ordering, synchronous transfersCore §11.22✅
Groupcast: keys, sessions, the peer tableCore §4.16, §4.17✅
Message Counter Synchronization ProtocolCore §4.18✅
PAFTP over Wi-Fi Public Action FramesCore §4.20✅
NTL: Matter over NFCCore §4.21✅

Credentials and commissioning

LayerSpecificationState
Onboarding payload (QR, manual code)Core §5.1✅
Fabrics and derived identifiersCore §4.3.2.2, §4.17.2✅
DER, CMS and PKCS#10RFC 5280, 5652, 2986✅
Operational certificates, X.509, chainsCore §6.1, §6.4.5, §6.5✅
Attestation: DAC chain, CD, NOCSRCore §6.2, §6.3, §6.4.6✅
The fail-safeCore §11.10.7.2✅
Descriptor, Basic Information, General CommissioningCore §9.5, §11.1, §11.10✅
Operational CredentialsCore §11.18, §6.4.10✅
Network CommissioningCore §11.9✅
General Diagnostics, Software DiagnosticsCore §11.12, §11.13✅
Ethernet, Wi-Fi and Thread Network DiagnosticsCore §11.14–11.16✅
Administrator CommissioningCore §11.19✅
Network RecoveryCore §5.9, §11.10✅
Joint Fabric: the CATs, cross-signing, the datastoreCore ch. 12, §11.24, §11.25✅
Revocation sets, distributed compliance ledgerCore §6.2.4📐

Data and interaction models

LayerSpecificationState
Interaction model encodingCore §8.10, ch. 10✅
Data model, wildcard expansionCore §7.6, §7.10–7.13, §8.2.1.6✅
Identifier ranges (MEI) for clusters, device types, attributesCore §7.21.2✅
Read, Write, Invoke processingCore §8.4.3.2, §8.7.3.2, §8.8.2.3✅
Subscriptions, reporting engineCore §8.5, §8.6✅
Event store, event reportsCore §7.14, §10.6.9✅
Timed transaction windowCore §8.7.4, §8.8.2.3✅
Chunked reports, oversized-list splittingCore §10.2.3, §10.6.4.3.1✅
List writes: replace versus appendCore §10.6.4.3.1, §8.7.3.3✅
Access control algorithm, CASE Authenticated TagsCore §6.6✅
Access Control clusterCore §9.10✅
Message processing: sessions, exchanges, MRP composedCore §4.7✅
Interaction model client: chunk reassemblyCore §10.2.3✅
Atomic writesCore §7.15✅
Binding, Fixed Label, User LabelCore §9.6, §9.8, §9.9✅
Check-In ProtocolCore §4.22✅
ICD Management clusterCore §9.16✅
Subscription persistence across rebootCore §8.5✅
Generated cluster library: ids, features, enums, conformanceApplication Cluster, Device Library✅
Conformance engine, descriptor validation, derived descriptorsCore §7.3✅
Device-type validationDevice Library §9.2✅
On/Off, with its state machineApplication Cluster §1.5✅
Identify, Groups, Scenes Management, Level ControlApplication Cluster §1.2–§1.6✅
Mode Base, once, for every cluster derived from itApplication Cluster §1.10✅
Device Energy Management, Energy EVSE, Water Heater ManagementApplication Cluster §9.2, §9.3, §9.5✅
Electrical Power and Energy Measurement, Power TopologyApplication Cluster §2.12–§2.14✅
Multi-endpoint nodes: routing, PartsList, bridgesCore §9.2, §9.12✅
Bridged Device Basic InformationCore §9.13✅
TLS Certificate Management, TLS Client ManagementCore §14.4, §14.5✅
Group Key ManagementCore §11.2✅
Groupcast cluster (provisional)Core §11.27✅
Thermostat suggestionsApplication Cluster §4.3.7✅
Generated ToTlv/FromTlv structures and command payloadsApplication Cluster✅
The remaining clusters’ behaviourApplication Cluster📐
Endpoints added and removed while the node runsCore §9.2📐

Controllers

LayerSpecificationState
The fabric’s certificate authority: RCAC, ICAC, NOCCore §6.5✅
A development attestation chain: PAA, PAI, DACCore §6.2.2✅
The commissioner’s side of the commissioning flowCore §5.5, §6.2.3✅
Client subscriptions: intervals, keep-alives, livenessCore §8.5✅
Fabric Synchronization’s Commissioner ControlCore §11.26✅
OTA Software Update ProviderCore §11.20.6✅
OTA Software Update RequestorCore §11.20.7✅
Multi-threaded controllers (sync-mutex)—✅
Device attestation revocation sets, the DCLCore §6.2.4📐

Discovery and platform

LayerSpecificationState
DNS-SD records, TXT keys, mDNS responderCore §4.3✅
mDNS probing, announcing, conflict resolution, rate limitsRFC 6762 §6, §8, §9✅
Platform seams, simulator, std backends—✅
Compile-time sizingCore §2.11✅
Operating-system mDNS backends, Thread SRP clientCore §4.3📐
ICD sleep scheduling and radio integrationCore §9.15📐
Per-chip BLE, Wi-Fi and Thread drivers—📐

Verification

A light linked for an nRF52840 occupies 88 KiB of flash and 39 KiB of RAM — .text 85 744, .rodata 4 516, .bss 40 576 — measured by ./footprint/run.sh, which builds the image, reads the sections out of it and writes them where cargo xtask stats can check this page against them. No radio is in that image.

1823 tests, 27 fuzz targets clean, builds for thumbv7em-none-eabihf and riscv32imac-unknown-none-elf, and a full feature powerset. See Testing for what each of those actually checks.

Separately from all of it, interop/chip/run.sh has the CHIP SDK’s own chip-tool commission the light example in a container, with device attestation verified rather than bypassed. It is the only check here with somebody else’s implementation on the other end, and it is the one that has found what the rest could not.