EU Data Act Smart Contract Audit (Article 36)

EU Data Act Smart Contract Audit — An EU Data Act smart contract audit is a security and conformity review of smart contracts used to execute data sharing agreements, testing them against the essential requirements of Article 36 of Regulation (EU) 2023/2854 — robustness and access control, safe termination and interruption, data archiving and continuity, and consistency with the agreement the contract executes — and producing evidence the vendor can rely on in its conformity assessment.

What a eu data act smart contract audit covers

The EU Data Act (Regulation (EU) 2023/2854) has applied since 12 September 2025. Article 36 is the first EU-level rule that places technical requirements directly on smart contracts. It applies to the vendor of an application using smart contracts, or to the person whose trade, business or profession involves deploying smart contracts for others, in the context of executing an agreement or part of an agreement to make data available. That person must ensure the contracts meet a set of essential requirements, carry out a conformity assessment and issue an EU declaration of conformity.

The requirements are written as outcomes, not as code rules: a very high degree of robustness and access control to avoid functional errors and withstand manipulation by third parties; a mechanism to safely terminate and interrupt the continued execution of transactions, including internal functions that can reset or stop the contract to avoid future accidental executions; archiving of transactional data, contract logic and code so past operations can be audited; and consistency with the terms of the data sharing agreement the contract executes. Turning those outcomes into testable properties is the work of the audit.

Scope matters. Article 36 targets smart contracts that execute data sharing agreements; it is not a general licensing regime for every DeFi protocol, and MiCA (Regulation (EU) 2023/1114) does not contain an equivalent smart-contract requirements list. If your contracts sit near the line — tokenised data marketplaces, IoT data access, data-for-payment settlement — the first deliverable is a written scoping opinion on which contracts the requirements plausibly attach to, which your counsel can then confirm.

Audit di smart contract e Regolamento europeo sui dati (Data Act, art. 36)

Il Regolamento (UE) 2023/2854, il cosiddetto Data Act, si applica dal 12 settembre 2025. L'articolo 36 stabilisce requisiti essenziali per gli smart contract utilizzati per eseguire accordi di condivisione dei dati: robustezza e controllo degli accessi, per evitare errori funzionali e resistere alla manipolazione da parte di terzi; un meccanismo per terminare o interrompere in sicurezza l'esecuzione delle transazioni; archiviazione dei dati transazionali, della logica e del codice per garantire la verificabilità; e coerenza con i termini dell'accordo che il contratto esegue.

Il fornitore dell'applicazione che utilizza smart contract, o chi li implementa per conto di terzi, deve garantire il rispetto di questi requisiti, effettuare una valutazione della conformità e rilasciare una dichiarazione di conformità UE. Safe Edges verifica i vostri contratti rispetto a ciascun requisito con revisione manuale del codice, test di invarianti e prove di exploit su rete forkata, e consegna un rapporto con le evidenze tecniche da allegare al fascicolo di conformità. Lavoriamo in inglese; il rapporto finale può includere un riepilogo in italiano. Questa pagina non costituisce consulenza legale.

Vulnerability classes we look for

Robustness: functional errors and third-party manipulation

Reentrancy, accounting and rounding errors, unchecked external calls, oracle and input manipulation, and denial-of-service paths — the classic smart contract bug classes, now framed as the "very high degree of robustness" Article 36 requires.

Access control at contract and governance level

Who can call what, who can upgrade, who can pause, and what a compromised key achieves. Missing or bypassable role checks, initialisers callable twice, and admin powers broader than the agreement allows.

Safe termination and interruption

Whether a stop or interrupt mechanism actually exists, who can trigger it, whether it halts every execution path (including queued and scheduled transactions), and whether it can itself be abused to freeze counterparties outside the agreement.

Reset and accidental re-execution

Internal functions that reset state or prevent future accidental executions: whether they work, whether they leave funds or data rights stranded, and whether replay or duplicate execution is possible after a reset.

Archiving, logging and auditability

Events and records sufficient to reconstruct past operations on data, verified source and bytecode retention, and upgrade histories that keep old logic auditable after a proxy upgrade.

Consistency with the data sharing agreement

The gap between the legal terms and the code: access windows, permitted purposes, pricing and compensation, termination triggers and data deletion obligations that the contract enforces differently, or not at all.

In scope

Not in scope unless agreed

How the engagement runs

  1. Scoping and threat modelling

    We fix a commit hash, agree the in-scope contracts and read your architecture docs, then build a threat model: who the actors are, what the trust boundaries are, and which invariants must never break. Nothing is reviewed against assumptions we have not written down.

  2. Manual review

    Line-by-line review by at least two auditors working independently, focused on authorisation, accounting, upgrade paths, external integrations and the gap between what the code does and what the documentation claims it does. Most critical findings come from this phase, not from tooling.

  3. Static and dynamic analysis

    Static analysers appropriate to the language, plus property-based fuzzing and invariant testing to push the system into states no unit test covers. Tooling is used to widen coverage, never to replace the manual pass.

  4. Exploit-path simulation

    Candidate findings are proven on a forked network with a working proof of concept. We report what an attacker can actually do and what it costs them, not a theoretical severity label.

  5. Reporting

    Every finding gets a severity rating, reproduction steps, the affected code, the impact in concrete terms and a specific remediation. You get a draft for discussion before anything is finalised.

  6. Fix review and re-test

    We re-test every remediation against the original proof of concept and check that the fix has not opened a new path. The final report is yours to publish.

What you receive

How we rate severity

SeverityWhat it means
CriticalDirect loss of funds or permanent freezing of assets, exploitable by any actor.
HighLoss of funds or protocol insolvency under realistic conditions, or requiring a privileged actor to misbehave.
MediumBroken protocol behaviour, denial of service, or value leakage that does not directly drain the contract.
LowEdge-case incorrectness with limited impact, or an issue requiring implausible preconditions.
InformationalCode quality, gas efficiency, documentation mismatch and defence-in-depth suggestions.

Pricing

Single token contract: starts from $999, report in 24–48 hours. dApp, GameFi or RWA project: starts from $2,999. DeFi protocol, L2 / rollup, Bridge, ZK circuit, AI agent / MCP: scoped per project after we have seen the code.

EU Data Act Smart Contract Audit: frequently asked questions

What does Article 36 of the EU Data Act require of smart contracts?

That smart contracts used to execute data sharing agreements offer robustness and access control against functional errors and third-party manipulation; can be safely terminated and interrupted, including internal functions to reset or stop them; archive transactional data, logic and code for auditability; are protected by rigorous access control at governance and contract level; and are consistent with the terms of the agreement they execute.

Who has to comply?

The vendor of an application using smart contracts, or the person whose trade, business or profession involves deploying smart contracts for others in the context of executing a data sharing agreement. They must perform a conformity assessment and issue an EU declaration of conformity.

When did the requirements start to apply?

The Data Act applies from 12 September 2025.

Does MiCA require a smart contract audit?

MiCA does not contain a smart-contract essential-requirements list like Data Act Article 36. Crypto-asset service providers and issuers still face ICT risk and operational resilience obligations, including under DORA, and an audit is the usual evidence for the smart contract part of that. Confirm your specific obligations with counsel.

Is an audit the same as a conformity assessment?

No. The vendor performs the conformity assessment and signs the declaration. A security audit produces the technical evidence that assessment rests on: which requirements the code meets, which it does not, what was fixed, and how it was verified.

Do you work with Italian teams?

Yes. Engagements run in English, and the final report can include an Italian executive summary for management and compliance readers.

What do you need from us to start an audit?

A repository or contract address, a commit hash to freeze the scope, whatever architecture or spec documentation exists, and a point of contact who can answer design questions. If documentation is thin we will write our understanding of the system back to you and ask you to confirm it — that step alone catches design-level bugs.

How long does an audit take?

A single token contract is 24–48 hours. A typical dApp or mid-sized protocol runs one to two weeks. Large DeFi systems, L2s, bridges and ZK circuits are scoped per project after we have seen the code. We will give you a fixed timeline with the quote, not an estimate that moves.

Is a re-test included after we fix the issues?

Yes. Fix review is part of the engagement, not an upsell. We re-run the original proof of concept against your patched code and confirm the fix has not introduced a new path.

Related security services

Get a fixed quote in 24 hours

Send the repository and a commit hash through the contact form, message @bugtester25 on Telegram, or book a 30-minute scoping call. 200+ protocols audited · $4B+ secured · 0 hacks post-audit. Prefer email? info@safeedges.in.