Proof of Reserves

Each bridged token is backed by the same amount of its asset, locked in the bridge's vault on the asset's origin chain: each SOLx by SOL in the vault on Solana. The app reads the locked and issued figures for each asset live from both chains and from RedStone, and you can reproduce the comparison without relying on us.

Live figures

The bridge app's Proof of reserves panel reads the figures live from both chains and from RedStone for the network you have selected. For each network they are:

• Locked is the asset held in the bridge's vault on its origin chain.
• Issued is the bridged token across all holdings on Canton.
• Pending has been issued on Canton and is waiting for its recipient to accept the transfer in their wallet. It is already counted in Issued.
• RedStone's reading is the vault balance as RedStone's own signers report it, with the slot of the vault's last change and that block's time.

For each asset, locked must be at least issued.

Why the figures match

Fees are removed on the origin chain before funds enter the vault, so the vault locks the net amount, and Canton issues exactly the same amount. Each redemption burns the token on Canton before the vault releases funds, so if the two figures diverge briefly during a transfer, issued is lower than locked, never higher. The bridge is not over-collateralized and does not need to be. The fee accounts are separate accounts the vault authority does not own and are not counted as collateral.

Each asset is reconciled on its own. SOL locked on Solana is compared only with SOLx issued on Canton.

Origin chain

Locked

• the vault's balance

Canton

Issued

• the token's live supply

Compared continuously

• by Memora's reconciliation monitor
• and independently by RedStone

Locked covers issued

• deposits and redemptions run

A shortfall

• new issuance halts
• vault releases are frozen

Halting is a cost to availability, taken deliberately to protect the reserves.

Under normal operation the difference between locked and issued is the pending amount plus rounding dust from settlement. Any other gap is abnormal and triggers the circuit breakers described in the Security Model.

Two independent checks

RedStone

RedStone reads the vault on the origin chain itself and publishes what it finds as signed data packages: the vault balance, the slot of its last change and that block's time, each signed by RedStone's own signers. The packages are public and anyone can fetch and verify them. See Verify it yourself. The bridge's relayer checks its own reading against RedStone's on every reconciliation and pauses issuance if the feed goes silent. RedStone's attestation on Canton itself, through its CAPS product, is planned and will join this page when it is live.

Our reconciliation monitor

The bridge continuously compares issued supply against the vault balance. Because each bridged token is one to one with its asset, this is a direct comparison with no price feed to trust. A sustained deficit, or an inability to compute the figure at all, halts new issuance.

Verify it yourself

You need the identifiers for the asset's origin chain on Verified Deployments.

1. Read the vault balance by opening the vault on any explorer for the origin chain. On Solana, open the vault token account. Its balance is the SOL locked.
2. Read the issued supply on Canton, where bridged tokens are standard CIP-56 holdings under the token's instrument ID and admin party. Sum them using a Canton explorer or your own participant's ledger API. Explorer link: Coming soon. Your Canton wallet shows your own holding's instrument ID and admin party, which must match the published values.
3. Compare them: locked must be at least issued, and the difference should equal the pending figure above plus settlement dust.
4. Check RedStone's reading on RedStone's feed page by comparing its balance feed with the vault balance you read in step 1. To verify the packages themselves, fetch the gateway listed on Verified Deployments, take the packages under the bridge's package ID, recover each one's signer from its signature with RedStone's protocol library, and accept a reading only when at least three of the listed signers have signed the same balance, slot and block time. RedStone's page shows the values with a currency sign. They are lamports, a slot number and a Unix time, not dollar amounts.

If your figures disagree with this page, email inquiries@memora.systems.

What is not shown

Individual users' balances and transactions are not shown. Holdings on Canton are private to the parties involved. The fee accounts are not shown, because they are not collateral. The figures are not a substitute for the audited vault logic that enforces the invariant. They are the public evidence that the logic is holding.