🐦 Archived X post

A tamper-evident, on-chain timestamp of what this post said. Captured 2026-10-04 22:08 UTC.

@YaffaRazon X · 2026-10-04

The CDC and FDA were well aware of the cardiac safety signal when the vaccine was authorized for 12-year-olds in May 2021. But that signal, as our study shows, did not disappear. Reports continued to accumulate, and the signal remained prominent. Yet vaccination of adolescents continued, and the vaccine was subsequently authorized for even younger children. Why didn’t they at least stop this snowball? And why on earth, now that these data are public, has the CDC AGAIN recommended vaccination for healthy children through shared decision-making, outside even the FDA-approved indications? Watch my coauthor, Dr. @YaakovOphir, explain the signal and what regulators already knew. And please share. Parents still need this information to make an informed decision and protect their children.
quotesthe post below (author id 914350363259613186)
So how on earth was the COVID vaccine authorized for children as young as 12 back in May 2021? In this first of two videos about my new study with Dr. @YaffaRaz, I focus on the cardiac safety signal itself – why it was so striking, and what the FDA and CDC already knew by then. https://t.co/8cioOhDGxG

This post quote-tweets the one above. Its text and identity are anchored (one level, no deeper); any media it showed is anchored with this post's media. Quoted text may be truncated for a long-form original — the anchored hash covers exactly the text shown here.

posthttps://x.com/YaffaRaz/status/2106776481720369196
author id1270202503158693888
posted2026-10-04T16:00:29.000Z
manifest sha256d8694ed3c0783ac8e3c2a9962cedc40e0aafac55f6f64c0a88cfc4e01572dd33
text sha25692220fb549398b07ff323765e7f6407f20ea826d7c8950c65ff9b84439ec2c24
quoted text sha256731a78f20ba5de7cc54fb2054aa8f9bf277910cae29e6a490ebe14e2486c4a38 (quoted post 2106772820831138002, author id 914350363259613186)
media sha2560420f3a9c435fd70859b02e1d6abd0e5b79400d3dfdb5a9f8cb8a0050f4f5d34 (video, 162932202 bytes)
on-chain⛓ anchored — cf381c2460f35a0853a81cfecc42e92d5310415497dd0d28af26a1ffb2330be8

Verify it yourself: the manifest is the exact JSON whose SHA-256 is d8694ed3c0783ac8e3c2a9962cedc40e0aafac55f6f64c0a88cfc4e01572dd33; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match 92220fb549398b07ff323765e7f6407f20ea826d7c8950c65ff9b84439ec2c24, plus the quoted post's id, author, and text hash 731a78f20ba5de7cc54fb2054aa8f9bf277910cae29e6a490ebe14e2486c4a38, and read the anchor transaction's OP_RETURN bsv.cx / x1 / d8694ed3c0783ac8e3c2a9962cedc40e0aafac55f6f64c0a88cfc4e01572dd33 — the block's timestamp proves the post said this at or before that time, with no trust in bsv.cx. Content archived via the X API.

← bsv.cx · JSON · ⚠ Report