Geo-blocking is not KYC or eligibility screening. For RWA investor eligibility, see KYC.
Configure it in the dashboard
Geo-blocking is configured per project, in the project’s Geo-blocking section.- yield.xyz’s mandatory region list is shown read-only, tagged Crypto Ban, OFAC, OFSI, Staking Ban, or Pending Litigation.
- Auto Compliance Mode is a per-project toggle. With it off, only the regions yield.xyz treats as mandatory are enforced automatically. Turning it on extends enforcement to yield.xyz’s complete flagged-region list, across every tag category.
- You can add your own country or region restrictions on top of whatever yield.xyz enforces.
Managing geo-blocking (the mandatory list view, Auto Compliance Mode, and your own restrictions) requires the owner, admin, or operator role. All roles can view the configuration.
Enforcement points
A blocked request returns the detected location in the error message:
Which IP is checked
The check uses theX-Forwarded-For header when present, falling back to the raw connection IP. If you call the Yield API or Perps API from your own backend rather than directly from the end user’s device, forward the end user’s IP in X-Forwarded-For; otherwise geo-blocking evaluates your server’s location instead of the end user’s.
Next steps
Geoblocked countries
The full country and region list, including per-product blocks.
Geoblocked US states
State-level and yield-specific blocks.
Perps
How Perps actions are geo-gated in practice.

