> For the complete documentation index, see [llms.txt](https://docs.ethena.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ethena.fi/backing-custody-and-security/overview/copper-clearloop-case-study.md).

# Copper Clearloop Case Study

Ethena initially launched using [Copper’s Clearloop](https://copper.co/products/clearloop) solution before onboarding additional OES providers. Copper is a UK-based custodian that has been the bedrock of institutional digital asset trading since 2018.

### Key Points

1. Copper has never been hacked or lost users’ funds in contrast to the $7bn lost in DeFi.
2. Copper users’ funds were wholly available within days of Coinflex’s (exchange) failure.
3. Copper users’ funds are held within a bankruptcy-remote trust, meaning in the event of Copper’s failure, users’ funds are not expected to be part of Copper's estate.
4. Exchanges are also required to post collateral with Copper as to ensure frictionless settlement with each two or four hour cycle.
5. Ethena retains the ability to dispute erroneous exchange settlement requests.

Here is a deck that provides even more detail about Copper's specific solution for Ethena:

{% file src="/files/aq9cWOmjVgQy0ddE5npZ" %}


---

# 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.ethena.fi/backing-custody-and-security/overview/copper-clearloop-case-study.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.