Three rules carry most of the weight.
- Every withdrawal passes through the multi-approval payout pipeline.
- Every balance change is a ledger entry that says why.
- Every change near custody, identity or the ledger ships with the tests that keep earlier defects closed.
They are enforced in code, and a change that breaks one of them fails before it ships.
Separation of Duties
The platform enforces independent approvals on every payout.
Operator actions are recorded against the operator who took them.
A release is produced by a script from a known commit, deployed one node at a time, and verified against the checksum of the binary that is running.
Every node is verified against the release the process produced.
The Standard for Published Statements
The value of a published claim rests on the standard it is held to.
- Every reserve figure is published with the method that produced it.
- Company assets and customer assets are always described separately.
- Internal records are presented as internal records, and evidence is attributed to its true source.
- Statements about the platform describe the release that is running.
That standard is why the statements on these pages can be read exactly as written.
Corrections
Corrections follow one transparent procedure.
A correction is a ledger entry, visible in the account it affects, with its reason recorded beside it.
The register of closed defects is part of the codebase, and each entry names the test that keeps it closed.
Every correction is made through the ledger.
A user who asks what happened to a balance receives the entry itself.
