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

# Security, Permissions, and Risk

#### Accounts and transaction authorization

Vigilan Market uses smart-contract accounts and on-chain settlement. Deposited collateral and market positions are held through the relevant account and contract structure; they should not be confused with assets remaining in an external wallet.

Review transaction authorizations, token approvals, and account permissions before signing. Account access depends on its configured signing, co-signing, module, and recovery arrangements. On-chain settlement by itself does not establish that every withdrawal or recovery path is independent of platform infrastructure.

#### What on-chain settlement provides

On-chain records make settled transactions inspectable. They do not imply that every resting order, matching decision, AI analysis, or off-chain operation is recorded on-chain.

Contract enforcement and collateral backing are important parts of the trading mechanism, but neither eliminates software vulnerabilities, compromised permissions, administrative dependencies, or service interruptions.

#### Main risks to understand

| Risk                      | Possible effect                                                       |
| ------------------------- | --------------------------------------------------------------------- |
| Outcome risk              | Purchased shares can settle at zero                                   |
| Basis risk                | An underlying loss may not satisfy the contract's trigger             |
| Liquidity risk            | A desired order or exit may not execute                               |
| Data and resolution risk  | Missing data or disputed interpretation can affect finalization       |
| Collateral risk           | USDT may lose value or face transfer restrictions                     |
| Contract and account risk | Vulnerabilities or compromised permissions can affect assets          |
| Operational risk          | An interface, signer, matching service, or network may be unavailable |
| AI analysis risk          | An alert may be inaccurate, incomplete, delayed, or absent            |

#### Using Vigilan responsibly

For a fully paid purchase of outcome shares, the contract-position loss is the amount paid plus applicable costs. This does not cap losses on your separate investments, liquidity positions, or automated strategies.

Vigilan provides risk information and event-trading tools. A contract pays according to its rules rather than reimbursing a verified personal loss. Examples in these docs are educational and are not personalized investment recommendations.

Review the applicable [Terms](https://vigilan.market/policy/terms) and [Privacy Policy](https://vigilan.market/policy/privacy). Product access remains subject to the terms and eligibility requirements that apply to your use.


---

# 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://docs.vigilan.market/platform/security-permissions-and-risk.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.