The Steam Dossier Corrections log
Corrections log
A public record of corrections and decisions.
This is the public record kept under the dispute procedure. Procedural entries are appended with the hash of the preceding entry. Your browser checks this chain below. A retained earlier head helps detect later alterations; a valid chain alone does not establish that a statement is true.
Verifying the chain in your browser…
Entries
Loading…
Check it yourself
How the chain works
Each entry has four fields: seq, body — the exact JSON text committed to — prev, the hash of the previous entry, and hash = SHA-256 of prev, a newline, and body. Entry #0 (genesis) has 64 zeros as prev and commits to the SHA-256 of the signed policy. Nothing is re-encoded before hashing, so any tool gets the same result:
curl -s 'https://phishdestroy.io/steam_dossier/dispute/api.php?action=log' | python3 -c '
import sys, json, hashlib
log, prev = json.load(sys.stdin), "0" * 64
for e in log["entries"]:
assert e["prev"] == prev, ("prev mismatch", e["seq"])
assert hashlib.sha256((e["prev"] + "\n" + e["body"]).encode()).hexdigest() == e["hash"], ("hash mismatch", e["seq"])
prev = e["hash"]
print("chain OK:", len(log["entries"]), "entries, head", prev)'
Keep the head hash you see today. If an entry you saw is ever altered or removed, your saved head will no longer appear in the chain. The system does not submit new heads or requests to the Internet Archive. Only material cleared for public release belongs in this log.
New requests and their timelines are private, including their identifiers, dates and status. They do not create automatic public entries. Publication requires a separate privacy, rights and restriction review (policy v3 §7.2). This log shows deliberately released entries and policy notices, not the total number of private requests. Earlier entries remain part of the historical record. Released public entries are under CC0.