CLUE Legal and Compliance References
Updated: June 30, 2026
This page is kept as a compatibility route for CLUE legal and compliance references. It helps users, integrators, and operators navigate the non-custodial prediction markets compliance perimeter, risk disclosure stack, KYC/AML references, operator responsibilities, and protocol-level legal framing without changing legacy links.
Use the canonical pages below for the current policy, disclosure, and protocol references:
- Compliance
- Risk Disclosure
- Protocol Legal Aspects
- Risk Model and Safeguards
- DAO Governance and Management
Legal and Compliance Reference Snapshot
| Reference area | Canonical source | Why it matters |
|---|---|---|
| Compliance perimeter | Compliance | Defines operator responsibilities, KYC/AML framing, sanctions perimeter, and jurisdiction review |
| Risk disclosure | Risk Disclosure | Sets expectations for software, market, governance, infrastructure, and legal risk |
| Protocol legal framing | Protocol Legal Aspects | Separates protocol infrastructure from service-layer obligations |
| Protocol safeguards | Risk Model and Safeguards | Connects compliance-adjacent controls to technical and operational safeguards |
| Governance controls | Governance and Management | Documents DAO controls for parameter changes, treasury limits, and execution discipline |
Regulatory principles
Use: Compliance / Regulatory principles
KYC/AML
Use: Compliance / KYC-AML and sanctions perimeter
Structure
Use: Compliance / Legal structure and responsibility split
Disclaimers
Use: Risk Disclosure / General disclosure scope
Related Protocol References
Legal and Compliance FAQ
Why keep this route? -> To preserve legacy links
Older references may point to this path. The page now acts as a compact legal and compliance reference hub while directing readers to canonical documents.
Does this page replace the compliance policy? -> No
The canonical compliance source is Compliance. This page is a navigation and reference layer for prediction market compliance topics.
Where should operators start? -> Compliance, legal aspects, and risk disclosure
Operators should review the compliance perimeter, protocol legal framing, risk disclosures, and service-layer obligations before exposing user-facing interfaces.