| Requirement | Intaglio | Alternatives |
|---|---|---|
| MiCA Art. 68(9) — record-keeping | ✓ 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-evident hash-chained record (optional Solana devnet anchor) | ✓ Yes | ✗ No |
| Open standard (auditor-readable policy) | ✓ Yes | ✗ No |
| Deterministic (no LLM in enforcement path) | ✓ Yes | ✗ No |
| Human approval workflow | ✓ Yes | ✗ No |
MiCA’s transitional period for CASPs ended on 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.
What each regulation actually requires.
MiCA Art. 68(9) requires crypto-asset service providers to keep records of every service, activity, order, and transaction for 5 years — up to 7 on regulator request — and to produce them on demand. When an autonomous agent places the order, conventional application logging does not produce a record that survives an audit. Intaglio produces one at decision time.
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.
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 ↗