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

# Trust model, TEE assumptions, audits, disclosure

Fast Poker's security model is simple to state: funds live in protocol vaults, game rules live in code, hole cards live inside the TEE, and settlement is verifiable on Solana.

## Mainnet Beta risk notice

Fast Poker is in Mainnet Beta. On-chain custody and verifiable settlement reduce some trust assumptions, but they do not remove all risk. Players, legacy table creators, dealers, and stakers should assume they can lose funds through bugs, bad signatures, infrastructure outages, network conditions, token volatility, liquidity changes, or their own operational mistakes.

Do not treat Mainnet Beta as a claim that the protocol is risk-free. Use only funds you are prepared to risk, verify wallet prompts before signing, and rely on official links from `https://fast.poker`.

## What you do not have to trust

| Party             | Why                                                                                 |
| ----------------- | ----------------------------------------------------------------------------------- |
| Fast Poker team   | The team does not hold player balances in a house wallet.                           |
| Dealers           | Dealers can move games forward, but the program validates payouts and rake routing. |
| Other players     | They cannot read your hole cards through the protocol.                              |
| A single frontend | The protocol state lives on chain.                                                  |

## What you still trust

| Surface       | Trust assumption                                                                |
| ------------- | ------------------------------------------------------------------------------- |
| Solana        | Solana provides settlement, custody, and durable state.                         |
| Program code  | The on-chain programs enforce table, vault, reward, and payout rules.           |
| TEE           | The TEE protects hole-card secrecy during live play.                            |
| RPC providers | Bad RPC can show stale state, so critical checks should use reliable endpoints. |

## TEE assumptions

The TEE is the privacy boundary for hole cards. It is designed so the dealer and team cannot peek while a hand is live.

TEE risk model:

* A real-time TEE compromise could leak cards during a hand.
* Player collusion outside the app is still possible.
* Verification catches deck inconsistency after the fact; it does not stop players from sharing their own cards.

## Smart contract security

Fast Poker is designed around permissionless calls with strict account validation.

Important properties:

* Player funds move by program rules, not team discretion.
* Cashout and payout flows are on chain.
* Dealer rewards are credited by real work, not by a self-reported "I dealt this" endpoint.
* Admin functions use multisig governance and timelocks where applicable.
* `ProtocolGuard` can pause selected high-risk ingress and fund-flow paths for a bounded slot window.
* Legacy private cash tables retain on-chain whitelist state for recovery; new cash gameplay is retired.
* Delegation paths use `ValidatorRegistry` to restrict TEE delegation to approved validators.
* Flat Bounty point supply is conserved: one point per 6/9-max entrant, with a point moving only to side-pot-eligible winner(s) on an actual knockout.
* Duel-mode and record-enabled SNGs fail closed when their required sidecar or settlement record is missing or invalid.
* Per-game records bind final SOL/$FP amounts to the table/game nonce and block replay; reusable-table reset waits for payout, jackpot, reward, duel, and cleanliness gates.
* Emission control and jackpot base odds are governed on-chain values. Dealers pass those accounts but cannot replace them with local configuration.

## Responsible disclosure

If you find a security issue, disclose it privately.

Email: `security@fast.poker`

You can also open a private ticket in the official Fast Poker Discord.

Do not post exploit details in public channels before the team has time to triage and patch.

## Security assumptions

* TEE privacy is a real trust assumption.
* Poker collusion is still a social and behavioral risk.
* RPC outages can make the UI look stale even when on-chain funds are safe.
* Upgrade authority exists until frozen; users should watch governance actions.

## Official links

Use links from `https://fast.poker`. Fast Poker will never ask for your seed phrase, DM you first with a wallet link, or ask you to install unknown software to claim funds.