> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wen.network/llms.txt
> Use this file to discover all available pages before exploring further.

# Custody and risk

> Understand authority, asset ownership and failure paths.

A connected wallet should never provide its private key to WEN or a keeper. Program-controlled accounts enforce admitted actions; the owner authorizes funding and terms. Keepers use their own transaction fee payer.

Program control does not by itself prove immutability or security. Deployment acceptance must disclose program identities, upgrade authority, permitted operators, oracle and conversion routes, spending limits and recovery behavior.

Risks include token and BTC price changes, fees, limited fills, thin exit liquidity, oracle/conversion failures, keeper delays and contract defects. The protocol BTC Reserve, staker BTC claims, operating vaults and Team funds have different owners and must not cover one another's obligations without an accepted rule.

A funded prize proves its payout capacity, not business profitability. A local test proves only the tested case; an older SAT deployment does not establish successor compatibility.

Use [status](/status) for the release boundary and [claims and recovery](/claims-and-exits) for the intended recovery model. No general audit certification is asserted by this page.