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

# security model

This page explains the main security properties of HyperPot.

## Pull Payouts

HyperPot credits winners and refunded users with claimable balances.

This avoids forcing transfers during settlement and protects the draw flow from malicious or incompatible receiver contracts.

## Reentrancy Protection

Critical external functions use reentrancy protection.

This includes deposit, claim, refund, and maintenance flows.

## Pausable Deposits

The contract includes pause support.

When paused, new deposits and expired draw triggers are blocked.

Claims are not paused, so users can still withdraw claimable funds.

## Entropy Reserve

Pyth Entropy requests require fees.

HyperPot keeps a separate entropy reserve so draw requests can be paid.

A small entropy top-up from settled pots helps keep that reserve funded.

## Keeper

The keeper is an off-chain automation process that calls public maintenance functions.

It does not have privileged powers over user funds.

Its job is to help move rounds forward:

* Cancel expired solo rounds.
* Trigger expired draws.
* Cancel stuck draws if needed.

Anyone can call those maintenance functions if conditions are met.

## Owner Controls

The owner can configure operational parameters such as:

* Pot cap
* Fee basis points
* Entropy basis points
* Round duration
* Entropy provider
* Callback gas limit
* Pause/unpause

These controls are useful during the beta, but they are also an important trust assumption.

## Known Beta Risks

{% hint style="warning" %}
This is a mainnet beta deployment.

The code, infrastructure, keeper, indexer, and frontend are still being hardened.

No public audit is claimed for the current deployment.

Use small amounts only if you understand and accept the risk.
{% 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://hyperpot.gitbook.io/hyperpot-docs/security-model.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.