01
Jurisdiction profiles
Each profile records status (open / conditioned / restricted), a regulator note, configured requirements, required disclosures and restricted categories.
Compliance
Compliance is configuration, not an afterthought.
TRVUE does not assume token issuance is legally permissible anywhere. Instead, the platform ships a configurable jurisdiction architecture: legal and compliance professionals define profiles, launch requirements and disclosure sets; the engine applies them deterministically.
- 10 jurisdictions configured
- 7 conditioned
- 2 open · obligations apply
- 1 restricted
The model
Profiles → eligibility → disclosures
Three layers, each independently configurable. Nothing here is generated on the fly by a model or an analyst: results are deterministic rule lookups over the configured registry, reproducible like every other engine output.
02
Launch eligibility
Given a jurisdiction, category and supply model, the engine returns blockers, conditions and review flags. Restricted categories block outright; conditioned profiles always surface their full condition set.
03
Required disclosures
Every profile carries the disclosure set a launch must present in that jurisdiction. Disclosures are configuration too — owned by qualified professionals, versioned with everything else.
TRVUE does not provide legal advice
This registry demonstrates architecture, not answers. Actual launch requirements must be configured and continuously updated by qualified legal and compliance professionals in every relevant jurisdiction. No profile implies token issuance is permissible anywhere.
Verification ≠ regulatory approval
A TRVUE Trust Score reflects evidence quality at a point in time. It never represents regulatory sign-off, licensing status, or a determination that any offering complies with any law. Those conclusions exist only where a competent authority makes them.
Live check
Run a launch-eligibility check
Select a jurisdiction, project category and supply model to see the engine’s exact output: blockers in red, conditions in amber, and the disclosure set the configuration requires. Try an unconfigured jurisdiction to see how absence of a profile degrades.
MANUAL REVIEW REQUIRED
Deterministic output of the compliance engine for this configuration — not legal advice.
Conditions (5)
- REQUIRED · ALL STAGES — Instrument classification: Determine whether the instrument is an asset-referenced token, an electronic-money token, another crypto-asset, or a traditional financial instrument — each follows a different rulebook.
- REQUIRED · LAUNCH — White-paper preparation & notification: Non-exempt offers require a compliant white paper notified to the competent authority before public offering.
- REQUIRED · LAUNCH — Transitional-period verification: Grandfathering/transitional windows differ per member state and expire on set dates — verify current status at launch time, per state of distribution.
- REQUIRED · DISTRIBUTION — Service-authorization analysis: Exchange, custody or trading services require analysis of crypto-asset service provider authorization needs.
- REQUIRED · MARKETING — Marketing-communication standards: Marketing communications must be consistent with the white paper, identifiable as such, and fair/clear/not misleading.
Required disclosures (3)
- Crypto-assets are highly risky and volatile; holders may lose the entire amount invested — this statement accompanies required disclosures.
- White papers are not prospectuses and carry no review endorsement.
- Nothing on this platform is investment advice.
#registry
Configured jurisdiction registry
Status colors are deliberate: green means no jurisdiction-level blocker is configured — attached obligations still apply; amber means conditions always attach; red means blocked outright in this configuration. The same data powers GET /api/v1/jurisdictions.
| Jurisdiction | Status as configured | Regulator note |
|---|---|---|
United States — Delaware us-delaware | CONDITIONED 4 configured requirements | Conditioned: federal + state securities analysis required. Delaware corporate law governs the entity, not the token. |
United States — Wyoming (DAO LLC) us-wyoming | CONDITIONED 4 configured requirements | Conditioned: federal + state securities analysis required. Wyoming offers a DAO LLC statute — a state-law entity form, not a federal clearance. |
Switzerland — Zug (Crypto Valley) switzerland-zug | CONDITIONED 4 configured requirements | Conditioned: token classification and prospectus thresholds drive obligations. The DLT Act provides ledger infrastructure, not blanket permission. |
United Arab Emirates — Dubai uae-dubai | CONDITIONED 4 configured requirements | Conditioned: virtual-asset activities are licensed activity-by-activity; mainland versus financial-free-zone determination comes first. |
Japan japan | CONDITIONED 3 configured requirements · 2 restricted categories | Conditioned: exchange/distribution services are registration-gated and promotional conduct is tightly restricted. Stablecoin and privacy configurations are restricted. |
Singapore singapore | CONDITIONED 3 configured requirements · 1 restricted category | Conditioned: digital-payment-token services are licensed; public solicitation for token offerings is heavily constrained. Privacy configurations are restricted. |
European Union eu | CONDITIONED 5 configured requirements | Conditioned (MiCA transitional framework): instrument classification, white-paper notification and service-authorization analysis required; transitional windows vary by member state. |
Cayman Islands cayman | OPEN · OBLIGATIONS APPLY 3 configured requirements | Open in this configuration: no jurisdiction-level launch blocker is configured for corporate/fund structuring — attached obligations still apply and 'open' is not a legality statement. |
British Virgin Islands british-virgin-islands | OPEN · OBLIGATIONS APPLY 3 configured requirements | Open in this configuration: no jurisdiction-level launch blocker is configured — virtual-asset service scope and substance obligations still apply. Not a legality statement. |
Mainland China china-mainland | RESTRICTED 1 configured requirement · 10 restricted categories | Restricted in this configuration: token issuance and financing activities targeting mainland residents are treated as prohibited; related exchange/pricing services likewise. |
Profiles are deterministic configuration reviewed into source control — any eligibility result can be reproduced from exactly this registry and engine version.
Disclaimer
TRVUE provides configurable compliance architecture, not legal advice. Jurisdiction profiles, eligibility rules and disclosure sets in this registry are placeholders that must be configured and continuously maintained by qualified legal and compliance professionals in each relevant jurisdiction. No output here constitutes, or substitutes for, legal, tax or regulatory advice; no profile implies that token issuance is legally permissible anywhere; and TRVUE verification reflects evidence quality, never regulatory approval.