Reserve accounting
The first Cipher check live in production, in detail, with real log entries.
Reserve accounting answers a question that no signature should precede, which is whether this transfer would push issued supply beyond verified backing on this pathway. Where the DVN protects assets in transit, reserve accounting protects assets at rest, and the two together close the loop that historically made unbacked releases possible.
What is monitored, continuously
Assets locked on the source chain.
Total issued supply across all destination chains.
The real-time collateralisation ratio between the two.
All computation happens inside the same TEE environment as the DVN, with the same certificate pinning guarantees, so the inputs cannot be spoofed and the results are hardware-attested.
Two sets of thresholds
Each protocol defines its own minimum collateral thresholds, and Canary enforces its own baseline limits on top. Even a misconfiguration on the protocol side cannot weaken the floor.
What happens on breach
If collateral falls below threshold, Canary stops signing immediately. The pathway is paused at the verification layer automatically, with no governance vote and no manual intervention. Alerts fire for both Canary and the protocol team, and transfers resume only once the invariant is restored.
In the signing path
For in-scope transfers above a configured threshold, the DVN asks the Cipher security engine for the current reserve state before signing. Thresholds are custom per chain and pathway, so the routine path stays fast and depth arrives exactly where value does. The check is live in production for a major stablecoin.
What the logs look like
Two entries from one production deployment, with figures as observed.
Below the threshold, no engine query is needed.
Above the threshold, the engine is queried and reserves are sufficient.

The fields tell the whole story.
amount
The value being moved by this message
backing
Current verified backing for the asset
minted
Issued supply before the transfer
postMinted
Issued supply if the transfer is signed
ratio
Backing divided by supply after the transfer
observedAt
When the reserve state was observed
In the second entry, postMinted is exactly minted plus amount, and the resulting ratio stays above one, so the check passes. Had the ratio fallen below the protocol's threshold or Canary's baseline, the DVN would not have signed.
For the highest-value transfers
Reserve attestations can additionally be wrapped in zero-knowledge proofs and verified onchain, so that, where the contract requires it, funds release only if the proof is valid. Even if every private key in the system were compromised, an attacker could not forge a valid proof without executing the correct code inside a genuine enclave. Keys alone are not enough.
Observe first, then enforce
Every check starts in observe mode. It runs against real traffic and records what it would have decided, without gating anything. Once accuracy is proven, it is promoted to blocking, with thresholds calibrated from evidence rather than guessed. Promotion requires no re-integration. This is the adoption model for every Cipher capability, described on Onboard to Cipher.
Reserve accounting and Collateral Proofs
Reserve accounting reconciles what a cross-chain pathway can prove, which is locked assets against issued supply. Canary Collateral Proofs supply the wider evidence about an asset's backing, including custodian, bank and administrator records with their limits stated. That evidence is designed to be used by Canary Cosigner at mint and redemption, and by checks on the DVN path for cross-chain movement. The two are compared on Collateral Proofs verification.