RESEARCH ROADMAP // A → Z
From board bring-up to validated evidence
Completed foundations lead into controlled security and resilience validation.
01 · COMPLETED
BL602 bring-up
02 · COMPLETED
PQC application-layer protocol
03 · COMPLETED
Structured telemetry and Splunk
04 · COMPLETED
PQC short-run validation
05 · COMPLETED
PQC 24-hour endurance
06 · COMPLETED
DTLS baseline
07 · COMPLETED
DTLS 24-hour endurance
08 · COMPLETED
PQC vs DTLS analysis
09 · COMPLETED
Firmware resource characterization
10 · COMPLETED
Runtime memory characterization
11
IN PROGRESS
PQC security / attack validation
12
IN PROGRESS
Controlled network resilience
13
NEXT
Crypto timing / protocol overhead
14
NEXT
Optional power / energy analysis
15
NEXT
Final evidence consolidation
16
NEXT
Peer review & replication
HOST CHECKS · RELEASE 2.0.0
Python lifecycle, registry, pinning, evidence, TVLA, fault analysis10 passed
Dashboard API endpoints, static frontend, CORS3 passed
CoAP bounds, URI, length and wire layoutPassed
State transitions, CRC, range overflowPassed
KEM seed / randomness failure handlingPassed
KEM core agreement100/100
Modified ciphertext changes secret100/100
Sender & receiver storage with simulated flashPassed
NOT YET SHOWN ON HARDWARE
- ○ BL602 cross-compile / flashed run of release 2.0.0
- ○ Entropy health, stack/heap headroom, flash wear & power-loss
- ○ KEM conformance vectors, constant-time behaviour
- ○ Secure boot, debug locks, side-channel & fault resistance