Every file served from contact.virebent.art is hashed and the set is reduced to a single Merkle root. The root is timestamped on the Bitcoin blockchain via OpenTimestamps, so anyone can prove that the content existed in this exact form at a specific time, and has not been altered since.
This page is the entry point to those proofs.
merkle_metadata.json — current Merkle root and the per-file SHA-256 leaves used to compute itmerkle_metadata.json.ots — OpenTimestamps receipt for the JSON above (Bitcoin anchor)dns.txt — same root mirrored as a _merkle.contact.virebent.art DNS TXT recorddns.txt.ots — OpenTimestamps receipt for the DNS mirror# 1. download the metadata + its OTS receipt
curl -O https://contact.virebent.art/.well-known/mfv/merkle_metadata.json
curl -O https://contact.virebent.art/.well-known/mfv/merkle_metadata.json.ots
# 2. confirm the Bitcoin anchor (needs ots client + a Bitcoin block source)
ots verify merkle_metadata.json
# 3. recompute the root yourself from the live site and compare
# (see the algorithm field in merkle_metadata.json)
If a server I run is seized, replaced, or coerced, the new operator cannot forge an older Bitcoin timestamp. By comparing the live merkle_metadata.json against the timestamped one, you can detect tampering.
If the live root does not match the timestamped root — or no current OTS proof exists — trust the proofs, not the page.
d6507c200eb2ba3561b1fc255f2dbf1d2e6d4a6bafa6f017669a62afc54fc7c7
Generated 2026-08-11T21:32:31Z. Algorithm: SHA-256 of sorted SHA-256 leaf hashes.
DNS mirror: _merkle.contact.virebent.art.