> 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/beth/concepts-and-reference/security.md).

# Security

[BETH architecture and trust boundaries](/beth/concepts-and-reference/architecture-and-trust-boundaries.md)

### Security model

BETH combines ETH custody in a threshold-signed Ethereum bridge contract, independent event verification, Canton authorization and privacy, versioned Daml packages, authenticated service integrations, and reserve evidence. No single control should be presented as the entire security model.

### Security layers

| Layer              | Primary control                                                           | Review focus                                                                                  |
| ------------------ | ------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- |
| ETH custody        | Bridge contract that releases ETH only with threshold attestor signatures | Contract code, upgrade governance, limits, pause, attestor key lifecycle, and correlated risk |
| Event verification | Attestor Network policy and evidence                                      | Duplicate prevention, transaction validity, and authorization                                 |
| Canton contracts   | Daml authorization and party rights                                       | Package versions, choices, privacy, and migration                                             |
| Client integration | Authentication, least privilege, validation, and idempotency              | Secrets, wrong-party risk, retries, and logs                                                  |
| Backing evidence   | Proof of Reserve and reconciliation                                       | Scope, cadence, stale data, and exclusions                                                    |
| Operations         | Monitoring, change control, incident response, and support                | Ownership, escalation, and recovery testing                                                   |

### Integrator responsibilities

Integrators must verify parties, deposit account IDs, and Ethereum destination addresses, pin compatible releases, protect credentials, validate contract state, reconcile ambiguous submissions, and use approved support channels. BETH infrastructure cannot protect an application that sends an authorized command with incorrect inputs.

### Privacy boundary

Canton limits contract visibility through sub-transaction privacy. Ethereum transactions remain visible on Ethereum. Application logs, support exports, and external systems can reveal information if operators do not protect them.

### Audits

Each audit report identifies the contracts, services, release tags, and dates within its scope. An audit is evidence about reviewed components at a point in time. It is not a guarantee that every deployment or future release is secure.

### Vulnerability reporting

Report suspected vulnerabilities through the private security contact listed in [Security and trust index](https://docs.bitsafe.finance/security-and-trust/). Do not post unpatched vulnerabilities in public issues. Include the affected release, impact, reproduction steps, and safe contact details.

### Known limitations

Check [BETH compatibility and release notes](/beth/concepts-and-reference/compatibility-and-release-notes.md) for supported versions, operational dependencies, known issues, and applicable audit scope.

### Related pages

* [BETH architecture and trust boundaries](/beth/concepts-and-reference/architecture-and-trust-boundaries.md)
* [BETH Attestor Network](/beth/concepts-and-reference/attestor-network-and-ethereum-signing.md)
* [BETH Proof of Reserve](/beth/concepts-and-reference/proof-of-reserve.md)
* [BETH authentication](/beth/get-started/authentication.md)
* [BETH compatibility and release notes](/beth/concepts-and-reference/compatibility-and-release-notes.md)
* [Security and trust index](https://docs.bitsafe.finance/security-and-trust/)

### Next step

👉 **Confirm the evidence and reporting path:** [Security and trust index](https://docs.bitsafe.finance/security-and-trust/).


---

# 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/beth/concepts-and-reference/security.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.