← the record

Proof: Why Dangote refinery project risks straining unity in EAC

The record — the exact bytes that were hashed

{"first_seen":"2026-09-29T21:02:48Z","headline":"Why Dangote refinery project risks straining unity in EAC","kind":"front-page-headline","rank":1,"source":"standardke","url":"https://www.standardmedia.co.ke/national/article/2001558988/why-dangote-refinery-project-risks-straining-unity-in-eac","v":1}

Download headline-c7b16cc8847c.json

SHA-256

c7b16cc8847c500dbc8b6a2841c6b1a2495c1f823f3abcfbc342c6c81e9bb173

OpenTimestamps

Submitted to the OpenTimestamps calendars 2026-09-29 21:07 UTC; waiting for a Bitcoin block (usually a few hours).

Download headline-c7b16cc8847c.json.ots

Wayback Machine

• The record pageCaptured 2026-09-29 21:09 UTC — view the capture.
• The story pageCaptured 2026-09-29 22:35 UTC — view the capture.

Check it yourself — none of this needs this site

1. Hash the record: sha256sum headline-c7b16cc8847c.json prints c7b16cc8847c500dbc8b6a2841c6b1a2495c1f823f3abcfbc342c6c81e9bb173. Its first twelve characters are the end of this record's address.
2. Drop headline-c7b16cc8847c.json and headline-c7b16cc8847c.json.ots onto opentimestamps.org, which checks the receipt against the Bitcoin block chain. Or, with the OpenTimestamps client and a Bitcoin node: ots verify headline-c7b16cc8847c.json.ots (ots upgrade first while the receipt is pending).
3. Open the Wayback Machine's captures above: the capture of the record page shows this hash as it stood then, and the capture of the story page shows the newsroom's own page.

Sealed automatically, 4 min after it was first seen.