The claim under examination is that Europe mandated a kill switch in every smart contract. Its legislative basis is Regulation (EU) 2023/2854, the Data Act, dated 13 December 2023 and published in the EU’s Official Journal on 22 December 2023. The disputed provision is Article 36. The question is whether the printed regulation actually contains that universal command.
It does not. Article 36 requires termination and interruption mechanisms for smart contracts executing agreements to make data available. It identifies the commercial actors responsible. Removing those limits changes the law being described.
What did Europe actually adopt?
The Council announced its final approval on 27 November 2023. Its account described rules governing access to data, switching between data-processing providers and safeguards against unlawful transfers. Smart contracts sit within that wider data-access framework. They are not its entire subject.
Article 50 sets 12 September 2025 as the Data Act’s general application date. Under Article 288 of the Treaty on the Functioning of the European Union, a regulation is binding in its entirety and directly applicable in Member States. Article 36 is therefore not a voluntary design suggestion.
But legal force and legal scope are different questions. A binding requirement for a specified application does not become a requirement for every application using similar technology.
The Commission’s Data Act explanation also describes a reach beyond companies established inside the EU. The relevant provisions can apply to businesses serving the Union market. Calling this merely a rule for European programmers understates its commercial reach. Calling it a rule for every smart contract overstates its subject matter.
Which smart contracts are covered?
Article 36’s heading supplies the first boundary: “Essential requirements regarding smart contracts for executing data sharing agreements.” Its operative text supplies the more important one.
Paragraph 1 addresses the vendor of an application using smart contracts. In the absence of that vendor, it addresses a person whose trade, business or profession involves deploying smart contracts for others. The relevant context is executing an agreement, or part of one, to make data available.
Those words identify both an activity and a responsible actor. They do not say that every program deployed on a blockchain must acquire a termination function.
Article 2 defines a smart contract through its function: automated execution of an agreement or part of one, using electronic data records with integrity and chronological ordering. The definition does not depend on a cryptocurrency label.
The sensible reading cuts both ways. Blockchain use alone does not establish coverage. Equally, calling an application decentralised finance does not establish an exemption if its actual activity satisfies Article 36. A particular application requires examination of its agreement and the vendor or deployer behind it. The label cannot settle that question.
What must the stop mechanism do?
Article 36(1)(b) expressly requires “safe termination and interruption.” A mechanism must exist to terminate the continued execution of transactions.
The smart contract must include internal functions capable of resetting it, stopping it or interrupting its operation. The provision specifically identifies avoiding future accidental execution of transactions as a purpose.
This is the factual core behind the kill-switch description. For a covered application, the requirement is real. Describing Article 36 as nothing more than interoperability guidance would be equally misleading.
The paragraph also requires clearly and transparently defined conditions for resetting, stopping or interrupting the contract. In particular, the circumstances permitting non-consensual termination or interruption must be assessed.
That last requirement matters. The legislation contemplates circumstances in which stopping execution need not depend on fresh agreement from everyone involved. But it does not name the Commission, a national authority or a blockchain developer as the universal holder of a shutdown key.
Nor does the paragraph order anyone to erase a blockchain’s transaction history. Its stated target is continued execution, including future accidental transactions. Stopping a program and rewriting its historical record are different operations.
Is stopping the only requirement?
Article 36(1) contains five sets of essential requirements. Termination is one of them.
The others address robustness and access control, data archiving and continuity, further access-control protections, and consistency with the data-sharing agreement being executed.
The archiving requirement is particularly useful when reading the termination provision. If a smart contract is terminated or deactivated, the transactional data, logic and code must remain capable of being archived so that past operations can be audited.
The law therefore pairs the ability to stop future execution with the ability to examine previous execution. A switch that destroys the relevant evidence would not satisfy that combination merely because it successfully stopped the program.
Consistency also matters. Article 36 requires the smart contract to match the terms of the data-sharing agreement it executes. The legal object is an automated agreement with specified safeguards, not a general-purpose government control over blockchain infrastructure.
Who carries the compliance obligation?
Article 36(2) requires the relevant vendor or professional deployer to conduct a conformity assessment. Meeting the essential requirements leads to an EU declaration of conformity.
Under paragraph 3, drawing up that declaration makes the actor responsible for compliance. The obligation is attached to an identifiable commercial role, not assigned indiscriminately to everyone who writes code or validates transactions.
Article 36 also provides routes through harmonised standards and Commission common specifications. Compliance with qualifying harmonised standards can establish a presumption of conformity for the requirements those standards cover.
Regulation (EU) No 1025/2012 supplies the European standardisation framework that Article 36 invokes. The Data Act authorises a standards process; that authorisation is not itself proof that any particular implementation has passed assessment.
Article 37 leaves Member States to establish penalties for infringements, subject to requirements that they be effective, proportionate and dissuasive. There is an enforcement structure behind the design obligations.
Did the requirement appear at the last minute?
No. The Commission’s proposal of 23 February 2022, COM(2022) 68 final, already contained essential requirements for data-sharing smart contracts in Article 30. They included safe termination and interruption.
The European Parliament’s amendments adopted on 14 March 2023 also addressed smart-contract requirements under Article 30. The enacted regulation places the provision in Article 36.
That history matters because an argument built around an earlier article number can sound current while quoting a different legislative stage. The final text controls. The proposal documents the origin of the requirement, not the complete obligation ultimately enacted.
Termination was part of the legislative project from the proposal stage. Universal coverage was not established by changing the provision’s number.
Is this cryptocurrency regulation by another name?
The EU adopted a separate Markets in Crypto-assets Regulation, Regulation (EU) 2023/1114. Its Article 1 addresses crypto-asset offers, admission to trading, issuers and service providers. Those are not the activity-based terms used in Data Act Article 36.
There are also separate rules for personal data and data intermediaries. Article 1 of the Data Act preserves the applicable personal-data protection framework, including the GDPR. The Data Governance Act, Regulation (EU) 2022/868, addresses matters including certain data-intermediation services and data altruism.
These distinctions do not make Article 36 harmless or optional. They establish which document supplies which obligation. A cryptocurrency transaction, a personal-data processing operation and an agreement to make data available are not interchangeable legal categories.
Does every smart contract need a kill switch?
No. The Data Act mandates genuine stopping capabilities for the smart contracts and commercial actors within Article 36’s data-sharing scope. It also requires defined stopping conditions, auditability and conformity assessment. Calling that a universal blockchain kill switch removes the limits that determine who must comply. Calling it no termination mandate at all removes the requirement that covered actors must meet.
