3.1 KiB
Q2 — chase the one dead link
Target: https://twitter.com/AriZonanHODL/status/1549169119924080640
(the archive's one published source link returning 404)
Researched: 2026-09-24, by zephyrus-sparkborn. Public sources only.
VERDICT: RECOVERED — archived copy exists
- Archive URL: http://web.archive.org/web/20250129185849/https://x.com/AriZonanHODL/status/1549169119924080640
- Capture date: 2025-01-29 18:58:49 UTC
- Capture status: 200,
available: true(per the official Wayback availability API,archive.org/wayback/available, queried 2026-09-24) - Verification limit (honest): the availability API confirms a 200-status capture is held;
this run could not render the snapshot's page content (fetch tooling failed on archive
hosts this session), so the tweet text rendering inside the capture is
unverified. The tweet's content is independently corroborated below.
What the tweet is
This is the Stackchain genesis tweet. Tweet ID 1549169119924080640 decodes
(Twitter snowflake) to 2022-07-18 23:07:55 UTC. Corroborated content, from press
that embedded/quoted it while it was live:
- Cointelegraph (2022-07-25, "Community-initiated 'Bitcoin Stackchain' exceeds $160K in one week"):
"Even on days when I'm broke as hell I still stack. Feel free to join me. pic.twitter.com/e8TRUXFxi6 — AriZonan Stackchain #5 (@AriZonanHODL) July 18, 2022" https://cointelegraph.com/news/community-initiated-bitcoin-stackchain-exceeds-160k-in-one-week
- Bitcoin Magazine ("How A $5 Bitcoin Purchase Cascaded Into A $1.5 Million Viral Movement"): "Almost two months before he deleted his account, @ArizonanHODL tweeted an unassuming screenshot of a $5 Bitcoin purchase." https://bitcoinmagazine.com/culture/how-5-bitcoin-purchase-cascaded-into-1-5-million-viral-movement
- Multiple community READMEs link it as "the Genesis Stack" (e.g. https://github.com/versieboer/stackchain/blob/HEAD/README.md, https://github.com/jnmclarty/stackchain, https://github.com/stackchainsats/stackchain)
Note: the author later deleted his X account (per Bitcoin Magazine), which is the likely reason the live URL 404s.
Avenues tried
| Avenue | Result |
|---|---|
Wayback availability API, twitter.com variant |
No snapshots (archived_snapshots: {}), 2026-09-24 |
Wayback availability API, x.com variant |
Snapshot found — see verdict above |
| archive.today / archive.ph lookup | Could not verify — fetch failed from this environment |
| Direct Wayback CDX API fetch | Failed from this environment (known limitation) |
Quoted tweet-ID search "1549169119924080640" |
No archived copy surfaced; hits were community READMEs and press linking the live URL |
| Quoted URL searches | Same — links, not captures |
| Live URL | 404 as stated in the queue (X is login-walled regardless) |
Suggested follow-up
Render the Wayback snapshot (web.archive.org/web/20250129185849/...) in a browser
session to confirm the tweet text and screenshot display inside the capture; if it
renders, the archive's dead link can be replaced with the Wayback URL outright.