> For the complete documentation index, see [llms.txt](https://docs.bitsafe.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bitsafe.finance/product-suite/assets/cbtc/glossary.md).

# Glossary

**Attestor** - Independent nodes that monitor Bitcoin, verify deposits and burns, and participate in the governance process to approve transactions.

**CBTC** - A 1:1 wrapped Bitcoin token built for secure trading and bridging on Canton.

**Burn** - The process of destroying CBTC tokens on Canton to initiate Bitcoin withdrawal.

**Coordinator** - The service that executes periodic checks, monitors deposits, and coordinates with Attestors.

**DepositAccount (DA)** - A Canton contract template that represents a deposit account, with each DA having a unique ID that deterministically maps to a Bitcoin deposit address.

**Mint** - The process of creating new CBTC tokens on Canton after confirmed Bitcoin deposits.

**Periodic Check (PC)** - A recurring process executed by the Coordinator every 60 to 120 seconds to trigger actions based on Bitcoin and Canton data.

**WithdrawAccount (WA)** - A Canton contract template representing a withdrawal account that stores a user-defined destination Bitcoin address.

**WithdrawRequest (WDR)** - A Canton contract template instantiated during withdrawal processing, containing the withdrawal amount, Bitcoin transaction ID, and destination address.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bitsafe.finance/product-suite/assets/cbtc/glossary.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.