Skip to main content
Compliance
Legal-layer and regulatory-posture updates. Each entry documents a specific change to how Areal operates within applicable legal frameworks — entity structure, jurisdictional restrictions, disclosure commitments, decentralization milestones, or regulatory interactions. The compliance changelog serves two purposes:
  1. Operational clarity — participants can see every change that affects who can access what, when restrictions apply, and how legal posture has evolved.
  2. Forensic record — regulators, auditors, and legal counsel can reconstruct the protocol’s compliance posture at any historical point.
Every entry includes: effective date, reason for change, affected parties, and links to any governance proposal or on-chain transaction that implemented it.
No compliance entries yet. The first entries will be added as the protocol publishes:

Quarterly Decentralization Reports

Published at the end of each calendar quarter following mainnet launch. See the Decentralization Roadmap for metrics and reporting scope.

Restricted Jurisdiction Updates

Updates to the list of jurisdictions denied front-end access. See Geographic Restrictions for the current list and update mechanism.

Entity Structure Changes

Any formation, dissolution, or restructuring of legal entities within the Areal ecosystem — including project-level DAO Ownership Companies onboarded to the protocol.

Regulatory Interactions

Material engagement with regulators, safe harbor applications, sandbox participation, or enforcement action — disclosed to the extent permitted by the relevant authority.

​
Why a separate compliance log

Compliance changes differ from feature, update, fix, and breaking-change entries in three ways:
  • Backward-looking as well as forward. A compliance entry often documents what has already been true (e.g., a legal opinion received months earlier) rather than announcing a new feature.
  • Non-technical audience. Participants reading compliance entries often include lawyers, regulators, and institutional allocators — not only developers.
  • Append-only forensic value. Compliance logs should be reliably complete. The separate tag ensures nothing compliance-relevant is buried in unrelated technical changelog entries.