- Author
- @otaliptus
- Organisation
- independent
- Evidence role
- independent-analysis
- Posted
- 1 Aug 2026, 01:32 UTC
- Capture status
- capture held
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 a locally held capture. The original remains the canonical publication. Last checked .
This post is held twice: here, with this project's own note on why it matters, and again as part of the conversation captured at , which is polled for changes. Both copies are the same post; neither is a separate event.
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 the addresses of people who published nothing themselves. Capture times and reviewed change summaries remain available below.
Held captures
0 presentation-noise differences. Sidebar, ticker and other page chrome churn that our review classified as not being changes to what the source says.
The excerpts and plain unified diffs above show the text this project held and how it changed. 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.
Compare the screenshot or a quotation against the original while it is available.