Дослідження з перевіркою джерел: Kraken OKX Bybit Regional

Decision Matrix

Source Map

• Kraken Support: Where is Kraken licensed or regulated? (kraken-licensed-regulated)
• OKX: Terms of Service (okx-terms)
• Bybit Help Center: Service Restricted Countries (bybit-restricted-countries)
• Kraken: Fee Schedule (kraken-fee-schedule)
• OKX: Trading Fee and Fee Tiers (okx-fees)

Control Notes

1. Jurisdiction

Jurisdiction is the part of the decision where a public source has to become an operating rule. In this package, it means availability depends on user and venue location. The practical action is to record residence and product jurisdiction. The unresolved edge is private geolocation flags, so this article keeps that uncertainty visible instead of turning it into a safety claim, reward claim, licensing claim, future-availability claim or product endorsement.

For a reader or operator, jurisdiction should be recorded before funds, account access, wallet recovery, API order flow, whitelists, identity checks, custody decisions, cross-chain transfers or tokenized-asset decisions become material. The record can stay simple: official URL, access date, product surface, account or network scope, source claim, editorial interpretation and a stop condition. Good evidence is non-secret. Bad evidence contains passwords, passphrases, seed phrases, private keys, API secrets, full balances, identity documents, verification codes, support-ticket private content or screenshots that expose account state.

2. Product surface

Product surface is the part of the decision where a public source has to become an operating rule. In this package, it means spot, derivatives, fiat and custody can differ. The practical action is to check the product, not just the brand. The unresolved edge is future product splits, so this article keeps that uncertainty visible instead of turning it into a safety claim, reward claim, licensing claim, future-availability claim or product endorsement.

For a reader or operator, product surface should be recorded before funds, account access, wallet recovery, API order flow, whitelists, identity checks, custody decisions, cross-chain transfers or tokenized-asset decisions become material. Good evidence is non-secret.

3. Terms route

Terms route is the part of the decision where a public source has to become an operating rule. In this package, it means terms carry restrictions that marketing pages may not repeat. The practical action is to read current terms before onboarding. The unresolved edge is legal interpretation, so this article keeps that uncertainty visible instead of turning it into a safety claim, reward claim, licensing claim, future-availability claim or product endorsement.

For a reader or operator, terms route should be recorded before funds, account access, wallet recovery, API order flow, whitelists, identity checks, custody decisions, cross-chain transfers or tokenized-asset decisions become material. Good evidence is non-secret.

4. Identity status

Identity status is the part of the decision where a public source has to become an operating rule. In this package, it means public region pages do not prove account approval. The practical action is to separate public eligibility from private KYC result. The unresolved edge is risk review timing, so this article keeps that uncertainty visible instead of turning it into a safety claim, reward claim, licensing claim, future-availability claim or product endorsement.

For a reader or operator, identity status should be recorded before funds, account access, wallet recovery, API order flow, whitelists, identity checks, custody decisions, cross-chain transfers or tokenized-asset decisions become material. Good evidence is non-secret.

5. Funding route

Funding route is the part of the decision where a public source has to become an operating rule. In this package, it means fiat and crypto rails can differ by region. The practical action is to verify deposit and withdrawal rail before funding. The unresolved edge is bank or network changes, so this article keeps that uncertainty visible instead of turning it into a safety claim, reward claim, licensing claim, future-availability claim or product endorsement.

For a reader or operator, funding route should be recorded before funds, account access, wallet recovery, API order flow, whitelists, identity checks, custody decisions, cross-chain transfers or tokenized-asset decisions become material. Good evidence is non-secret.

6. Source date

Source date is the part of the decision where a public source has to become an operating rule. In this package, it means regional pages change. The practical action is to record access date and recheck before action. The unresolved edge is unannounced edits, so this article keeps that uncertainty visible instead of turning it into a safety claim, reward claim, licensing claim, future-availability claim or product endorsement.

For a reader or operator, source date should be recorded before funds, account access, wallet recovery, API order flow, whitelists, identity checks, custody decisions, cross-chain transfers or tokenized-asset decisions become material. Good evidence is non-secret.

7. Stop rule

Stop rule is the part of the decision where a public source has to become an operating rule. In this package, it means stop when region, product or account scope is unclear. The practical action is to do not fund until official state is clear. The unresolved edge is support response timing, so this article keeps that uncertainty visible instead of turning it into a safety claim, reward claim, licensing claim, future-availability claim or product endorsement.

Known Unknowns

• private geolocation flags
• future product splits
• legal interpretation
• risk review timing
• bank or network changes
• unannounced edits
• support response timing

Practical Takeaway

The safe version of this package stays exact. Regional availability is a current-state evidence problem, not a brand-level assumption. Kraken publishes official material about where it is licensed or regulated; OKX publishes terms of service that define user obligations and restrictions; Bybit publishes a service restricted countries help page. The decision outcome is to check the venue, product surface, jurisdiction, account residence, documentation route and source date before assuming that an account can be opened, funded, traded or withdrawn from a given region. A local draft or old comparison cannot prove present availability, and a public page cannot prove a private account has cleared onboarding. The user outcome is a documented decision boundary and a stop rule, not a promise that a venue, transfer, API, custody path, tokenized asset, stablecoin metric or onboarding flow will work under every future condition.