Verifying the data
This site tells you what a wine cost on a given day, and what kind of company stands behind the label. Normally you would have to take that on trust: any website can quietly change a number later, or soften what it said about a producer, and nobody would ever notice.
We have made that impossible for ourselves. Every night everything we have recorded is reduced to one short string of characters — a cryptographic fingerprint — which changes completely if even a single digit in a single record changes. That string is published outside this site, in a place we cannot reach afterwards. So if we were to change yesterday's price, or yesterday's verdict about a winery, the fingerprint would stop matching — and anyone could see it.
None of this is our own invention. The fingerprint is sealed into the Bitcoin blockchain through OpenTimestamps, an open standard that has been used for a decade to date documents, archives and research; the same underlying trick — a Merkle tree — is what lets your browser tell a genuine site from a fake one. The program that checks our fingerprints is not ours either: it is free software, and it reads ours exactly as it reads anyone else's.
What this gives you: when a page here says a price has fallen over six months, or that we downgraded a company in March, you can check it rather than believe it. And a winery that disagrees with its category is arguing with a dated decision, not with a database field we are free to edit while the argument is going on.
It proves one thing and no more: that we knew exactly this on exactly that day. It does not make the fact true — a price we recorded may have been wrong in the shop's own catalogue, and a classification may rest on incomplete sources. What is protected here is the history of our statements, not their correctness.
Check a record
This part is for those who want to check a particular record and know its identifier — pages of this site link here with it already filled in. Everything above holds whether or not you ever use it.
Fingerprints
| Day | Records | Root | Proof | File |
|---|---|---|---|---|
| 2026-09-17 | 129,510 | f4042de7d753…26c63442 | in Bitcoin, block 967491 | download |
| 2026-09-16 | 117,629 | 9ce36a373b0f…8f4c9e4f | in Bitcoin, block 967357 | download |
| 2026-09-15 | 116,450 | 0e419351fb9d…caef6886 | in Bitcoin, block 967218 | download |
| 2026-09-14 | 116,450 | 0e419351fb9d…caef6886 | in Bitcoin, block 967056 | download |
| 2026-09-13 | 113,496 | 8ed0e3464c14…0a6a6a15 | in Bitcoin, block 966895 | download |
| 2026-09-12 | 112,225 | aa797c758d06…88acc67f | in Bitcoin, block 966756 | download |
| 2026-09-11 | 112,225 | aa797c758d06…88acc67f | in Bitcoin, block 966598 | download |
| 2026-09-10 | 112,221 | 648d543ae0ca…9ff12e0e | in Bitcoin, block 966436 | download |
| 2026-09-09 | 108,174 | 3cf238c5725c…552e8e09 | in Bitcoin, block 966297 | download |
| 2026-09-08 | 106,999 | 6a3e7dbac908…6b15dbfc | in Bitcoin, block 966136 | download |
| 2026-09-07 | 106,999 | 6a3e7dbac908…6b15dbfc | in Bitcoin, block 966008 | download |
| 2026-09-06 | 103,981 | a9ad8724271a…4c1bd187 | in Bitcoin, block 965870 | download |
| 2026-09-05 | 102,781 | a15c3a3a7287…01ee6240 | in Bitcoin, block 965706 | download |
| 2026-09-04 | 102,211 | 2a19852d003e…6e4fc5dd | in Bitcoin, block 965550 | download |
| 2026-09-03 | 102,205 | 6594e589cb23…d0c75885 | in Bitcoin, block 965500 | download |
| 2026-09-02 | 99,136 | 76b11f22ee89…cd6d4134 | in Bitcoin, block 965276 | download |
How to check this without us
This part is for those who would rather not take our word for it. The proof file is an OpenTimestamps timestamp: the standard client checks the date of a fingerprint against the Bitcoin blockchain itself, asking this site nothing.
pip install opentimestamps-client ots verify --digest <корень> getwine-<дата>.ots
A fresh fingerprint is confirmed within hours, not instantly — until then the proof says only that the calendar servers accepted it.