> For the complete documentation index, see [llms.txt](https://docs.world.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.world.inc/getting-started/restrictions.md).

# Restrictions

Customers in the United States are not allowed to trade on World Markets. Similarly, customers in the United Kingdom are blocked. OFAC sanctioned individuals are unconditionally banned.

It's a permissionless protocol, so the smart contracts do not have the ability to detect or ban specific users or specific geographies, nonetheless consumers in restricted jurisdictions are unconditionally banned. Blocking is enforced at the UI level, based on IP addresses and wallet addresses.

Countries with high OFAC-related risks are blocked by the UI; however, users living in those countries, who are not sanctioned by OFAC, may still be allowed to use the product. Here is the list of blocked countries, which we consider high OFAC-related risk, but may still have users who are allowed to use the product:

* Russia
* Venezuela
* Belarus
* Syria
* Myanmar
* Sudan & South Sudan
* Afghanistan

Read the Terms of Service here: <https://world.inc/#/terms-of-service>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.world.inc/getting-started/restrictions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
