Fingerprints
When an issue of Hikma Weekly is published, Mizan computes a SHA-256 fingerprint of its full contents and posts it here. If a single word or number changed afterwards, the fingerprint would no longer match.
This is what makes a track record checkable rather than merely claimed. A published call cannot be quietly revised, and a bad call cannot be deleted, because the fingerprint of the issue that contained it is already public.
| No. | Published | SHA-256 |
|---|---|---|
| 1 | 2026-09-13 01:07 UTC | 5ac6eefd1cd755b558f56571412aded9e0a4ba0877ac04a04e0a4dcd9bba37c0 |
| 2 | 2026-10-06 03:33 UTC | 5fe3414fc4f347cbd09513fddd33a616577c545ca5ec450e15d99bed6e12d059 |
Verifying one yourself
The machine-readable list is at /fingerprints.txt, which is also committed to a public repository each week so the history is timestamped somewhere Mizan does not control.
Fingerprints cover the contents of each issue as published. The methodology version behind each one is recorded alongside it, so a change in method is visible rather than silent.