# What the $2,000 bitcoin bounty actually proves: what changed in v1.1.0, sgit.ai > The changes to the article "What the $2,000 bitcoin bounty actually proves" in v1.1.0, paragraph by paragraph. *Source: · sgit.ai v0.7.87 · this file is generated from the same content as the page, so the two cannot drift. Every page on this site has a `.md` twin; internal links below point at them.* --- [Home](../../../index.md) / [Articles](../../index.md) / [What the $2,000 bitcoin bounty actually proves](../../what-the-bitcoin-bounty-actually-proves.md) / [Versions](../what-the-bitcoin-bounty-actually-proves.md) / v1.1.0 # What the $2,000 bitcoin bounty actually proves: what changed in v1.1.0 From v1.0.0 (2026-10-26, `77f353ae5`) to v1.1.0 (2026-10-27, `db67c5ce1`), paragraph by paragraph. 0 paragraphs added, 0 removed, 3 changed in place, 53 unchanged. About 0 words added and 117 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names. [all versions](../what-the-bitcoin-bounty-actually-proves.md) 2 unchanged paragraphs !shot dt-timeline.webp | images/ | The real timeline:timeline of the challenge launched at 08:21 UTC onfrom 21 October with no page that executed PHP at all, so the flaw could not be reached; the operator added one at 22:00 JST on 25 October; it was solved about three hours later, at 00:47 JST onto 26 October, notagainst the "19.28 hours" the site's own counter and most press reports gave. | chart 26 unchanged paragraphs, under In short {#in-short}, What actually happened {#bounty}, The real timeline is three hours, not nineteen {#timeline}… !shot dt-waf.webp | images/ | CouldDetectionacoveragefirewallforhavephp2shellseen it coming?from Cloudflare, AWS WAF, Azure Front Door, Emerging Threats and Sophos each publish detection coverage for php2shell,Sophos, and each names its own gap: request-only inspection, header amplification under a size cap, a rule disabled by default, signatures a reshaped request can dodge, or no specific rule at all.gap. | chart 8 unchanged paragraphs, under Hardening without patching: what actually holds {#hardening} !shot dt-harden.webp | images/ | Hardening without patching: session.upload_progress=0,fourmemory_limit=-1,measuresblocking multipart requests at the edge, and a container or cgroup memory cap are each described bythat their own authors ascallpartial.partial, and what GrapheneOS deployeddidand tested the first three, decided not to trust them, and took its only PHP service offline instead, patching and returning within about seven hours.instead. | chart 17 unchanged paragraphs, under What a defender would actually see {#logs}, What this does not claim {#limits}, Where this comes from {#sources} [all versions](../what-the-bitcoin-bounty-actually-proves.md) --- *[Site index for agents](../../../llms.txt) · [HTML version](https://newsroom.sgit.ai/articles/versions/what-the-bitcoin-bounty-actually-proves/v1.1.0.html)*