> 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/quickstart.md).

# Quickstart

Three paths to the Assurance Layer, depending on what you are securing.

Pick the path that matches what you are securing. Most protocols start with the DVN and add Cipher checks later. Issuers add Cosigner to the signing workflow they already run, and Canary Collateral Proofs are designed to show the evidence behind it.

{% tabs %}
{% tab title="Protocols: Canary DVN" %}
**Secure your cross-chain messages with Canary verification.**

1. Set Canary as a required DVN in your application's security stack, alongside LayerZero Labs and Deutsche Telekom.
2. Add two optional DVNs at threshold 1: Horizen, plus one verifier of your own choosing.
3. Wire the configuration for every pathway you operate, in both directions, then read it back onchain and confirm it on LayerZero Scan before you rely on it.

The rationale is on [Recommended DVN sets](/canary/integrate/recommended-dvn-sets.md), and working code is in the [configuration file guide](/canary/integrate/configuration-file.md).

{% hint style="info" %}
Canary is part of the default security configuration on LayerZero, so new deployments that keep the default configuration have Canary verifying their messages from day one on pathways where Canary operates. Setting your own configuration lets you choose a stronger set, and it opts you out of future default changes, so you own keeping it current.
{% endhint %}
{% endtab %}

{% tab title="Protocols: Canary Cipher" %}
**Add the checks your protocol actually needs before a transfer is released.**

1. Start with a working session to agree which conditions matter, which systems should be consulted, at what value thresholds, and how each check should behave on failure.
2. Run the agreed checks in observe mode against your real traffic. Each check records what it would have decided without gating anything.
3. Promote each check to blocking once its accuracy is proven, with thresholds calibrated from evidence. Promotion needs no re-integration.

Details are on [Canary Cipher](/canary/the-assurance-layer/canary-cipher.md) and [Onboard to Cipher](/canary/integrate/onboard-to-cipher.md).
{% endtab %}

{% tab title="Issuers: Cosigner and Collateral Proofs" %}
**Show what backs your asset, and put independent verification in front of every mint and redemption.**

1. Define your approval rules: backing rules, limits, counterparties, timing, and what should place a request on hold.
2. Connect your sources: collateral wallets and token supply onchain, records from custodians, banks and fund administrators, and auditor confirmations. Canary Collateral Proofs are designed to check this evidence and show users where each record came from, how it was checked and what still needs trust.
3. Add Cosigner to your signing workflow, first as an optional signer while the checks prove themselves, then as a required approver so no request can be authorised without its checks.

Details are on [Canary Collateral Proofs](/canary/the-assurance-layer/collateral-proofs.md), [Canary Cosigner](/canary/the-assurance-layer/canary-cosigner.md) and [Onboard to Cosigner](/canary/integrate/onboard-to-cosigner.md).
{% endtab %}
{% endtabs %}

## Before you start

* DVN addresses differ per chain. Use the named configuration in the LayerZero toolbox, or take addresses from the [DVN address registry](/canary/reference/dvn-addresses.md).
* Reach Canary only through official channels. Impersonation attempts increase after major incidents, and direct messages claiming to be Canary should be treated as suspect. See [Security contact and disclosure](/canary/trust-and-transparency/security-contact.md).
* To give an AI assistant or coding agent these docs, connect it to the Canary MCP server at `https://canary-1.gitbook.io/canary/~gitbook/mcp`. [Use these docs with AI](/canary/reference/ai-assistants.md) has the setup for each tool.