> 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/dashboards-and-live-data.md).

# Dashboards and live data

Where the live numbers are, and how to read them.

Live Canary DVN statistics are published on a public Dune dashboard, so anyone can check the figures in these docs without asking for them.

{% embed url="<https://dune.com/canaryone/canary-layerzero-dvn-statistics-v2-foundation>" %}
Canary LayerZero DVN statistics on Dune
{% endembed %}

## What the dashboard shows

| Section                           | What it tells you                                                                                              |
| --------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| Overview counters                 | Cumulative secured volume, messages verified, and applications active in the last 90 days                      |
| Secured volume over time          | Volume per transaction by date, and cumulative volume by week                                                  |
| Weekly secured volume             | Volume each week with week-over-week change in dollars and percent; the latest week is partial until it closes |
| Run rate                          | Secured volume over the last 7 and 30 days, and the average value per message                                  |
| Application adoption and activity | Messages and volume by application                                                                             |
| Chain adoption and activity       | Messages and volume by chain                                                                                   |
| Source and destination            | The top source and destination chains by secured volume                                                        |
| Pathway concentration             | The busiest source-to-destination routes                                                                       |
| Message and volume mix            | Average value per message by application, separating larger tickets from retail flow                           |
| New-application cohorts           | When applications first used Canary, and how often they return month to month                                  |
| Volume size buckets               | The share of messages and of volume by ticket size                                                             |

## Reading the figures correctly

* **Volume is flow, not a balance.** Secured volume is the cumulative value of transfers Canary verified. It is not value locked, and it should always be quoted with its period and date.
* **Dune indexes a subset of chains.** Totals across all chains Canary supports are higher than the dashboard shows.
* **Application names are labels.** Names on the dashboard are LayerZero project labels on secured transfers, not a verified record of each application's DVN configuration.
* **The latest week is partial** until it closes.

## Per-asset transparency

[Canary Collateral Proofs](/canary/the-assurance-layer/collateral-proofs.md) are designed to add a transparency view for each asset. It shows what backs the asset, who controls the backing, where each record came from, how it was verified, how current it is, and what users still need to trust. Stale records, unavailable sources and disagreements between sources are shown rather than hidden.

When reading it, weigh each record by where it came from. A directly observed onchain balance is stronger evidence than an issuer-supplied statement, and an independent confirmation of the same assets is not a second pool of reserves.

## Per-protocol transparency

Cipher and Cosigner customers receive transparency surfaces for their own deployments: supply per chain, reconciliation status, verification throughput, and refusal and hold events.