> For the complete documentation index, see [llms.txt](https://canary-1.gitbook.io/canary/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://canary-1.gitbook.io/canary/trust-and-transparency/track-record.md).

# Track record

What nearly two years in production looks like, in figures anyone can check.

For nearly two years, Canary has held one standard in production, proving before signing and refusing anything it cannot prove. Every message is checked inside trusted execution environments, with a k-of-n quorum, certificate-pinned sources across independent providers, confirmation floors and chain state, before anything is signed. Operating at scale without a single incident was the proof of concept. This page is the record.

## The record

Figures as of 7 October 2026. Definitions and sources are on [Figures and sources](/canary/reference/figures-and-sources.md).

| Measure                            | Figure                                                  |
| ---------------------------------- | ------------------------------------------------------- |
| In production                      | Since January 2025, nearly two years                    |
| Uptime                             | 100%                                                    |
| Security incidents                 | Zero                                                    |
| Misverified messages               | Zero                                                    |
| Cross-chain volume secured         | $53.4B+ cumulative                                      |
| Messages verified                  | 1.6M+                                                   |
| Applications                       | 440+ active in the last 90 days                         |
| Volume secured in the last 30 days | $13.3B+                                                 |
| Average value per message          | About $33,000                                           |
| Coverage                           | 140+ chains                                             |
| Ecosystem position                 | Part of the default security configuration on LayerZero |

Canary stayed fully operational through a major AWS outage that degraded much of the ecosystem.

## Growth in secured volume

<figure><img src="https://2589044420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpsBN7WLVynXZJOLD5eCk%2Fuploads%2FN71AoATH8aRowD2RbgUs%2Fchart-cumulative-volume-2026-10-07.png?alt=media" alt="Area chart of cumulative cross-chain volume secured by Canary, by week, from March 2025 to October 2026. Volume grows slowly to about $3.4B by mid-April 2026, then rises steeply to $53.44B by 7 October 2026."><figcaption><p>Cumulative volume secured by week, March 2025 to 7 October 2026. Source: Canary DVN statistics on Dune.</p></figcaption></figure>

Secured volume passed $3.4B in mid-April 2026 and has grown by more than $50B since, at a run rate of about $13B a month. Weekly secured volume has been above $2B in each of the last seven complete weeks, and the week of 28 September 2026 set a new high of $5.91B.

<figure><img src="https://2589044420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpsBN7WLVynXZJOLD5eCk%2Fuploads%2FYMOV3o8LNiNXKYsHxwKf%2Fchart-weekly-volume-2026-10-07.png?alt=media" alt="Column chart of weekly cross-chain volume secured by Canary from March 2025 to October 2026. Weekly volume stays below $200M until April 2026, then runs between about $1B and $3.6B a week, before reaching $5.91B in the week of 28 September 2026. The last, paler bar is the partial week of 5 October."><figcaption><p>Weekly volume secured, March 2025 to 7 October 2026. The latest week is partial. Source: Canary DVN statistics on Dune.</p></figcaption></figure>

## Selected applications secured by Canary

USDT0, Ethena, Ether.Fi, wBTC, Stargate, MegaETH, PayPal, Theo, Agora, Kraken, Ondo Finance, Midas, Morpho, Euler, Puffer, GMX, Orderly, Hemi, Lagrange and Tempo.

Canary typically sits in an application's verifier set as one of several independent DVNs, which is the point of a well-built set.

## Independent review

The DVN code was audited with zero security findings, and auditing continues on the latest version with different firms. See [Audits](/canary/trust-and-transparency/audits.md).

## Check it yourself

Live figures are on the public Dune dashboard, described on [Dashboards and live data](/canary/trust-and-transparency/dashboards-and-live-data.md). Refusals are recorded with their reasons, as described on [Refusal transparency](/canary/trust-and-transparency/refusal-transparency.md).