The public audit layer
Why a shared record that no single party controls is worth more than a record you are asked to trust, and what that buys you.
A record everyone can check is worth more than a record everyone is asked to trust. That is the whole argument for anchoring an exchange to a shared, append-only, tamper-evident record that no single party controls or can rewrite.
Every record that leaves the platform is anchored to that layer. The anchor binds the record to an ordered position, which is what lets somebody establish later that a record existed in a given form at a given moment.
No single party owns it
The absence of an owner is not a philosophical position, it is the mechanism. An anchored proof can be verified by anyone precisely because no operator sits between the proof and the person checking it, and because no operator can withdraw or amend what has already been recorded.
mintBlue writes anchors to that layer on your behalf, and holds no privileged position on it. Another implementation writing anchors for another organisation uses the same layer on the same terms.
What it buys you
Three properties follow, and they are the ones worth putting in an architecture review.
There is no central honeypot. The layer carries anchors, not your data. There is no single store holding everyone's records to breach, because no such store is created in the first place.
Keys stay with the holder. Verification does not require handing anyone your keys, and anchoring does not require handing anyone your content. Non-custodial keys sets out exactly what mintBlue holds in each deployment model.
Nobody can quietly amend a record. Records are appended rather than edited. A changed record is a new record, and the previous state stays visible. What the mechanism gives you is tamper-evidence, which means a change is detectable, not that a change is impossible.
What this page deliberately does not do
It does not describe how anchoring or settlement work underneath. Those mechanics are specified by the SDX Protocol, and a second description of them, written here and maintained by nobody, would drift.
Specified by the SDX Protocol. mintBlue implements this concept; the SDX Protocol specifies it. Read the specification
For what "verifiable" means precisely, rather than loosely, the protocol side sets it out at data integrity and verification.
What it does not promise
Permanence is not one of the properties. The layer makes a record tamper-evident and independently verifiable, and neither of those is a guarantee that any particular byte will be retrievable forever from any particular place. Storage and retention are product questions, and they are answered per deployment rather than by the layer.