> For the complete documentation index, see [llms.txt](https://support.cregis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.cregis.com/3.-wallet-and-risk-control/shard.md).

# Shard

Cregis utilizes advanced <mark style="color:green;">**MPC (Multi-Party Computation)**</mark> shard technology to enhance the security of private keys by dividing them into multiple shards. In a <mark style="color:green;">**single-signature wallet**</mark>, these MPC shards are securely stored across both the local device and a <mark style="color:green;">**Trusted Execution Environment (TEE)**</mark>, ensuring that no single entity holds the complete key. For <mark style="color:green;">**multi-signature wallets**</mark>, the shards are distributed across different local devices, further enhancing security by decentralizing control. Each time a transaction is made, the MPC shards are computed in various locations and combined with those stored in the cloud, ensuring a highly secure and efficient signing process.


---

# 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://support.cregis.com/3.-wallet-and-risk-control/shard.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.