Compliance (Off-chain Decisioning, On-chain Enforcement)

Compliance in Goldie is intentionally split:

• Decisioning is off-chain (KYC/KYB providers, internal compliance teams, investigations)
• Enforcement is on-chain (issuance/transfer checks that cannot be bypassed)

This design keeps personal data off-chain while ensuring that policy enforcement is auditable and consistent.

Commodity-mode compliance (common baseline)

In the most common configuration, the protocol enforces eligibility gates using minimal on-chain state (e.g., approved/denied) and optional allowlist/blocklist controls.

At enforcement points (issuance and/or transfers), the token ecosystem consults a compliance module. If policy fails, the transaction is rejected on-chain.

Securities-mode compliance (deployment-dependent)

In deployments that require securities-style constraints, the protocol can be extended to enforce additional rules (e.g., lockups, accreditation gating, jurisdiction-specific constraints). These rules are deployment- and jurisdiction-dependent and should be documented explicitly per deployment.

What users observe

When a compliance rule blocks an action, the transaction reverts on-chain. Applications built on top of the protocol typically display a generic eligibility error and a next-step message (e.g., complete verification or contact support). Detailed reasons are usually kept off-chain.

Privacy

The protocol is designed so that on-chain compliance state remains minimal and privacy-preserving. Identity documents and PII are handled off-chain.

Diagrams

Off-chain decisioning, on-chain enforcement

Rendering diagram…