> For the complete documentation index, see [llms.txt](https://linkary.gitbook.io/linkary-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://linkary.gitbook.io/linkary-docs/linkary-wallet/wallet-security.md).

# Wallet Security

<figure><img src="https://1087592013-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGcspr3cyfJvCi6NzTi8U%2Fuploads%2FHpR9DhUmGV4z0EI8L5pm%2FWallet%20Security.png?alt=media&amp;token=1abb502b-0f67-4439-a8f2-f8cccd11460c" alt=""><figcaption></figcaption></figure>

Linkary does not model auction bids as an internal custodial USDC balance.

For supported settlement, backend verification is designed to validate:

* The expected network
* The official Base USDC contract
* The correct auction and winner
* The expected payer wallet
* The snapshotted seller payout destination
* The exact amount
* Successful receipt
* Transaction replay protection
* Prevention of double settlement

{% hint style="danger" %}
Never share a private key, recovery phrase, or secret credential in support conversations or public documentation examples.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://linkary.gitbook.io/linkary-docs/linkary-wallet/wallet-security.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.