README.md update build repro steps (were misordered before)
What changed, and why it matters
This commit only updates the README.md file to correct the order of steps for building a reproducible copy of the COLDCARD firmware. It changes documentation text: adding a step to change into the firmware directory, updating the example release tag and binary filename, and moving the directory change to stm32 after the checkout. There are no code changes and no security implications.
No security action needed. This is a routine documentation fix.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is a documentation-only change in README.md. It reorders the build reproduction instructions so users first clone, then cd into the firmware directory, download a firmware binary, checkout the matching tag, then cd into stm32 before running make. The example tag and binary filename are updated from 2023-12-21T1526-v5.2.2 to 2026-03-05T2052-v5.5.0. No source code, build scripts, or cryptographic logic is modified.
Changed components
README.md documentationInspect captured patch +5 / −3
diff --git a/README.md b/README.md
index d5d985d..6029f5d 100644
--- a/README.md
+++ b/README.md
@@ -28,9 +28,11 @@ has been automated using Docker. Steps are as follows:
```shell
git clone https://github.com/Coldcard/firmware.git
- git checkout 2023-12-21T1526-v5.2.2
- # get a copy of that binary into ./releases/2023-12-21T1526-v5.2.2-mk4-coldcard.dfu
- cd firmware/stm32
+ cd firmware
+ # DOWNLOAD https://coldcard.com/downloads
+ # get a copy of binary into ./releases/2026-03-05T2052-v5.5.0-mk-coldcard.dfu
+ git checkout 2026-03-05T2052-v5.5.0
+ cd stm32
make -f MK4-Makefile repro
```
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.