MiCA Compliance Guide

Markets in Crypto-Assets (MiCA) becomes fully effective in June 2026. This guide covers how Galileo tokens relate to MiCA requirements.

Token Classification

Galileo tokens are classified as utility tokens under MiCA:

• Represent ownership rights to physical goods
• Not designed for investment returns
• Utility is access to product authenticity data

Whitepaper Requirements

MiCA requires a whitepaper for crypto-asset offerings. Galileo's DPP satisfies this requirement:

• Issuer identification (brand DID)
• Rights and obligations (ownership transfer rules)
• Technology description (ERC-3643, identity system)
• Risk disclosure (compliance module descriptions)

CASP Requirements

Crypto-Asset Service Providers must be licensed. Galileo provides:

• Service provider claim type (ONCHAINID topic 11)
• License verification hooks
• Geographic restriction modules

Travel Rule

MiCA implements the Travel Rule for transfers greater than 1,000 EUR:

struct TravelRuleData {
    string originatorName;
    string originatorAddress;
    string beneficiaryName;
    bytes32 originatorIdHash;  // Privacy-preserving
    bytes32 beneficiaryIdHash;
}

Implementation Checklist

• DPP includes MiCA whitepaper fields
• CASP verification implemented
• Travel Rule data exchange configured
• Geographic restrictions active
• Complaint handling process documented

Timeline

• June 2024 — MiCA enters force (stablecoins)
• December 2024 — Full application
• June 2026 — Transition period ends