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

# Security & Compliance

{% hint style="info" %}
HyperStackz is built with capital safety and execution transparency at its core — not as an afterthought, but as a foundational design principle.\
Every strategy runs through a self-contained agent wallet on Hyperliquid, giving users complete control over their capital at all times.
{% endhint %}

***

### Custody & Wallet Infrastructure

HyperStackz does **not** pool or custody user funds.\
All activity runs directly through your **authorized agent wallet** on **Hyperliquid**.

**Key facts:**

* Each user trades from their own Hyperliquid account.
* HyperStackz only automates execution through signed agent authorization.
* The agent cannot withdraw, transfer, or access funds outside of strategy operations.
* All trades are visible in real time on the **Hyperliquid dashboard** or block explorers.

{% hint style="success" %}
Users always maintain full ownership and custody of their funds.\
HyperStackz never holds or moves capital — it only executes pre-approved orders through your account.
{% endhint %}

***

### Execution Logic & Risk Controls

HyperStackz minimizes directional risk through structured, rules-based logic.\
Every action taken by the agent is verifiable and governed by your configured parameters.

**Risk Control Highlights:**

* No leveraged trading or speculative positions.
* Each strategy operates on spot markets using Strike + TTP logic.
* No rehypothecation or internal fund reuse.
* Trailing Take-Profit (TTP) dynamically protects profits during upward momentum.
* Automated cycle resets prevent exposure drift or long idle periods.

{% hint style="success" %}
HyperStackz replaces emotional execution with precision logic.\
The engine follows structure — not sentiment.
{% endhint %}

***

### Transparency & Compliance

HyperStackz is designed for total operational transparency.\
All strategy activity — orders, fills, TTP events, and resets — is publicly viewable through the user’s Hyperliquid account.

**Transparency Features:**

* On-chain order data visible via **Hyperscan** and **Arbiscan**.
* Strategy parameters (Strike, TTP, Projected APY, Stackz Chance) are fully user-visible.
* No hidden trading logic or off-chain fund routing.
* Real-time PnL and yield tracking accessible through the **Portfolio** dashboard.

{% hint style="warning" %}
HyperStackz operates under a non-custodial, transparent execution model.\
Every order is traceable, verifiable, and tied directly to the user’s wallet.
{% endhint %}

***

### Audit & Testing

While v1 does not rely on pooled smart contracts, HyperStackz still undergoes strict internal testing and continuous monitoring.

**Ongoing Audit Plan:**

* Continuous backend monitoring and transaction simulation
* Internal validation of agent wallet operations
* Third-party code review and integration audits (frontend + backend)

{% hint style="warning" %}
Smart contract audits apply only to pooled custody systems.\
HyperStackz v1 uses a per-user agent model — eliminating most pooled-contract risks but still subject to operational testing and review.
{% endhint %}

***

### User Best Practices

To maximize safety and ensure execution integrity, follow these guidelines:

* Verify the official HyperStackz domain before connecting your wallet.
* Use a dedicated **Hyperliquid wallet** for strategies.
* Avoid using centralized exchange accounts or custodial wallets.
* Regularly monitor your agent activity via **Hyperscan** or the **Portfolio** dashboard.
* Only interact through official links and verified communication channels.

{% hint style="success" %}
Security starts with custody — you always own your funds.\
HyperStackz automates execution, not control.
{% 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://hyperstackz.gitbook.io/hyperstackz-docs/support-and-safety/security-and-compliance.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.