Geoblocking & Access Restrictions
Relevant source files
The following files were used as context for generating this wiki page:
- src/app/[locale]/(platform)/tos/page.tsx/tos/page.tsx)
- src/app/[locale]/admin/(general)/_actions/update-general-settings.ts/_actions/update-general-settings.ts)
- src/app/[locale]/admin/(general)/_components/LegalSection.tsx/_components/LegalSection.tsx)
- src/app/[locale]/(platform)/settings/sdks/page.tsx/settings/sdks/page.tsx)
- src/app/[locale]/admin/integrations/_components/AdminIntegrationsForm.tsx
- src/i18n/messages/en.json
The Geoblocking & Access Restrictions system is a critical compliance and security module within the platform. Its primary purpose is to restrict access to specific platform features—particularly "Technology Features" like on-chain trading—based on the user's geographical location. This ensures the platform adheres to local laws, international sanctions, and regulatory requirements in jurisdictions where event-based contracts are prohibited.
The system encompasses administrative configuration, where operators can define blocked countries, and enforcement mechanisms that trigger during wallet connection or SDK utilization. Users are legally prohibited from using VPNs or similar tools to circumvent these access controls, as outlined in the Terms of Use.
Administrative Configuration
Platform administrators manage geoblocking through the Admin Dashboard. The configuration allows for selecting specific countries to be restricted from accessing the platform's trading features.
Blocked Countries Management
Administrators can search and select countries via a dedicated UI component. If no countries are selected, the platform remains available globally by default.
The administrative flow for managing restrictions.
Sources: src/app/[locale]/admin/(general)/_components/LegalSection.tsx:109-150, src/app/[locale]/admin/(general)/_actions/update-general-settings.ts:634-640
Key Administrative Components
| Component | Description |
|---|---|
LegalSection | React component providing the UI for selecting blocked countries and uploading Terms of Use PDFs. |
updateGeneralSettingsAction | Server action that persists the blocked countries list to the database. |
syncGeoblockSettings | Function that synchronizes the saved settings with the external geoblocking service. |
Sources: src/app/[locale]/admin/(general)/_components/LegalSection.tsx:32-45, src/app/[locale]/admin/(general)/_actions/update-general-settings.ts:616-641
Enforcement Mechanisms
Enforcement occurs at multiple levels of the application, including the web interface and the SDK distribution system.
SDK and Trading Restrictions
When users attempt to download SDKs for automated trading (CLOB or Relayer clients), the system checks the geoblock status. If geoblocking is active in the settings, this parameter is passed to the download service to ensure compliance is enforced within the generated SDK bundles.
Data flow for enforcing geoblocking during SDK downloads.
Sources: src/app/[locale]/(platform)/settings/sdks/page.tsx:47-66
Frontend Blocking
If a user is detected as accessing from a restricted region, the platform displays a blocking notice.
- Message: "This platform is not currently available in your region."
- Key:
HvSrFRin localization files.
Sources: src/i18n/messages/en.json:1152
Legal Framework and TOS
Geoblocking is legally supported by the platform's Terms of Use (TOS). The TOS explicitly lists restricted jurisdictions and prohibits the use of Technology Features (trading contracts) by persons residing in those areas.
Restricted Jurisdictions
The following regions are explicitly identified as Restricted Jurisdictions in the default TOS:
- United States of America
- United Kingdom
- France
- Ontario (Canada)
- Singapore
- Poland
- Thailand
- Australia
- Belgium
- Taiwan
- Comprehensively sanctioned regions (Iran, Syria, Cuba, North Korea, Crimea, Donetsk, Luhansk)
Sources: src/app/[locale]/(platform)/tos/page.tsx:107-116
Prohibited Conduct
The TOS specifically prohibits the following regarding access restrictions:
- Accessing Technology Features from a Restricted Jurisdiction.
- Using VPNs, proxy servers, or similar tools to circumvent geoblocking controls.
- Providing false or misleading information to evade eligibility verification.
Sources: src/app/[locale]/(platform)/tos/page.tsx:162-164
Identity Verification (Sumsub)
In addition to country-level geoblocking, the platform integrates with Sumsub for individual identity verification (KYC). This serves as a secondary layer of access restriction.
| Feature | Description |
|---|---|
| Enforcement Levels | Can be set to disabled, observe (monitoring only), or required (blocking access until verified). |
| Verification Level | Customizable level names within the Sumsub dashboard. |
| Integration | Managed via App Token and Secret Key in the Integrations settings. |
Sources: src/app/[locale]/admin/integrations/_components/AdminIntegrationsForm.tsx:288-340
Summary
The Geoblocking & Access Restrictions system provides a multi-tiered approach to regulatory compliance. It combines administrative country-level blocking, automated enforcement in SDKs and trading interfaces, and an optional identity verification layer via Sumsub. All restrictions are governed by the platform's Terms of Use, which explicitly prohibit circumvention via technical means like VPNs.