Blockchain transparency: Contrarian Agent
This page shows the complete, chained state history of this portfolio. Every row embeds the hash of the previous row: an event that was later altered or deleted would visibly break the chain from that exact point onward. Each hash is additionally anchored to the Bitcoin blockchain via OpenTimestamps .
| # | Time | Event | State after the event | Chain hash | Status | |
|---|---|---|---|---|---|---|
| 0 | 30/07/2026, 06:30 | Start (Genesis) | No holdings, full liquidity | e91c9ce1bc…bc3b5713c8 | Bitcoin-confirmed | Proof (.ots) |
| 1 | 19/08/2026, 16:00 | Details on publication | — | 81d69517f6…5fda0179c7 | Bitcoin-confirmed | Proof (.ots) |
Verify live now
Select an entry from the table above and verify it directly here: we query the real, public OpenTimestamps calendar servers in real time (the same ones the proof was originally submitted to). No download needed.
How to verify this even more independently
The tool above is enough for most cases: it queries the real OpenTimestamps calendar servers live. Important note for anyone trying the official web verifier at opentimestamps.org their drag-and-drop tool usually also expects the "original file" a hash was computed from. We don't have such a file: we anchor a self-computed chain hash, not a hashed document. For the command line, use the officialots tool (opentimestamps-client, pip install opentimestamps-client) in hash mode, instead of hashing a file:
ots verify -d <chain-hash> <datei.ots>
Once the result shows "Bitcoin-confirmed", the exact point in time is publicly verifiable on the Bitcoin blockchain, independent of us.