Trust & transparency
Update History
This page lists the most recent changes recorded in our internal change log — who (or which automated process) made the change, what was changed, and why. It is generated directly from our database, not written by hand, so it cannot fall out of date with what actually happened.
| Date | Actor | Action | Target | Reason |
|---|---|---|---|---|
| 2026-10-20 | cto | update_fact | coinbase__security__hhs0mp | Sếp OK 20/10 19:02: chỉ có PoR cho token wrapped (coinbase.com/cbbtc/proof-of-reserves), /proof-of-reserves toàn sàn = 404 (Chrome 20/10) |
| 2026-10-20 | cto | insert_fact | mexc__security__1020 | Sếp OK 20/10 19:02: MEXC chưa có fact security → video/bài suy ra "không có PoR"; blog.mexc.com PoR 07/2026 audited by Hacken (R&D 10/10 + curl 20/10) |
| 2026-10-20 | cto | update_fact | kraken__security__5rq4gf | Sếp duyệt 20/10 19:0x: R&D research-261020-0830 xác minh kraken.com/proof-of-reserves (200, nhắc PoR 244 lần) — fact cũ false gộp nhầm với phí rút |
Why we publish this
Part of building trust without named authors is showing our work. Every meaningful change to exchange data or published content is logged with a before/after value, which lets us roll changes back if something turns out to be wrong. We would rather show a short or empty log than a padded one — this page reflects exactly what our database contains, nothing more.
What counts as a logged change
Not every internal action produces a row here — only changes with outward effect: updating a data field that a page renders (like a fee or a country restriction), publishing or unpublishing a page, and corrections made in response to reader reports. Routine infrastructure work, like deploying a code change that does not alter what a reader sees, is tracked separately in our engineering logs rather than mixed into this reader-facing history.