| Requirement | Intaglio | Alternatives |
|---|---|---|
| MiCA Art. 68 — AI decision audit trail | ✓ Yes | ✗ No |
| EU AI Act Art. 12 — high-risk system logging | ✓ Yes | ✗ No |
| DORA — financial system resilience records | ✓ Yes | ✗ No |
| OFAC sanctions list enforcement | ✓ Yes | ✗ No |
| Tamper-proof on-chain record | ✓ Yes | ✗ No |
| Open standard (auditor-readable policy) | ✓ Yes | ✗ No |
| Deterministic (no LLM in enforcement path) | ✓ Yes | ✗ No |
| Human approval workflow | ✓ Yes | ✗ No |
← Return to public ledgerRegulatory coverage
MiCA CASP obligations take effect July 1, 2026.
Every AI agent operator processing financial transactions in Europe is affected. Intaglio is the only open-standard solution that addresses these requirements today — deterministic enforcement plus a tamper-evident on-chain record regulators can verify without trusting us.
01 Policy before execution02 Deterministic verdict03 Hash-linked evidence
What each regulation actually requires.
MiCA Art. 68Effective July 1, 2026
Crypto-asset service providers must keep records of every decision affecting client assets in a form that is tamper-evident and reconstructable. A database log the provider can edit does not satisfy this — a Solana-anchored hash chain does.
EU AI Act Art. 12High-risk systems
Automated decision systems classified high-risk must keep automatic logs of events over their lifecycle. Every Intaglio decision is logged with its policy version, inputs hash, and outcome — by construction, not as an add-on.
DORAIn force
Digital Operational Resilience requires financial entities to maintain reconstructable records of operational events. Intaglio's append-only audit records and on-chain anchor give a resilience record no single party can rewrite.
Stop unauthorized transactions
before they execute.
Inspect the policy. Run a local decision. Keep the proof.
See enforcement live ↗