Tamper-evident track record uses SHA-256, git and Bitcoin timestamps
A team needed a way to show its forecasts were made before outcomes were known, without requiring readers to take its word for it. Each night, the day's scores are saved to a CSV file before the next market open, and the file's SHA-256 fingerprint is logged with a publication time. The file and ledger are pushed to a public git repository, and the file is also timestamped via OpenTimestamps, which anchors its hash in a Bitcoin transaction independent of GitHub. Any alteration to the file would change its fingerprint, while corrections are added as new entries in a public log rather than edits to existing data. The article notes a practical pitfall, where git line-ending normalisation can alter file bytes, and suggests a .gitattributes rule to prevent this. The approach is presented as an educational, not investment-advice, transparency method.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in