- Author
- @otaliptus
- Organisation
- independent
- Evidence role
- independent-analysis
- Posted
- 1 Aug 2026, 01:32 UTC
- Capture status
- capture held
- Artefacts held
- 3
A deliberately tentative independent Mk4 model. Assuming a remote attacker does not know the UID, otaliptus estimates about 20 to 21 bits from the wafer-coordinate word, narrows practical SysTick positions, and isolates the unresolved RTC term. The post reports roughly 52 to 63 bits if Mk4 RTC behaviour is problematic and roughly 75 to 88 bits if it is not. The author labels this brainstorming and lists assumptions that may be wrong, so it is preserved as reported analysis rather than a measured bound.
This post is registered as evidence and has locally held capture artefacts. The original remains the canonical publication; hashes below identify the files held by this project. Last checked .
Snapshot and diff bodies for this chain monitor are held in the local evidence archive but withheld from the public site because they can contain victim addresses. Integrity hashes, capture times and reviewed change summaries remain available below.
Each copy above is identified by the SHA-256 of its extracted text, shown beside it, and the diffs are plain unified diffs. To verify a quotation, compare it against the page itself or against the Internet Archive's copies, which are independent of this project.
Complete captures are held offline rather than mirrored here, so this page shows diffs and excerpts. If a quotation is ever disputed, the full copy can be produced. Ask.
The SHA-256 prefixes above identify each held copy without turning this page into a mirror of somebody else's post. Compare a quotation against the original. If the post has since been edited or deleted, ask and the held copy can be produced.