<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.2 20190208//EN" "http://jats.nlm.nih.gov/publishing/1.2/JATS-journalpublishing1.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="1.2" xml:lang="en">
    <front>
        <journal-meta>
            <journal-id journal-id-type="pmc">F1000Research</journal-id>
            <journal-title-group>
                <journal-title>F1000Research</journal-title>
            </journal-title-group>
            <issn pub-type="epub">2046-1402</issn>
            <publisher>
                <publisher-name>F1000 Research Limited</publisher-name>
                <publisher-loc>London, UK</publisher-loc>
            </publisher>
        </journal-meta>
        <article-meta>
            <article-id pub-id-type="doi">10.12688/f1000research.182069.1</article-id>
            <article-categories>
                <subj-group subj-group-type="heading">
                    <subject>Research Article</subject>
                </subj-group>
                <subj-group>
                    <subject>Articles</subject>
                </subj-group>
            </article-categories>
            <title-group>
                <article-title>Smart Contracts and Blockchain Technology: From Paper to Code, Paving the Way for the Reshaping of Traditional Contract Theory in E-Commerce &#x2013; A Comparative Study</article-title>
                <fn-group content-type="pub-status">
                    <fn>
                        <p>[version 1; peer review: awaiting peer review]</p>
                    </fn>
                </fn-group>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author" corresp="yes">
                    <name>
                        <surname>mahmoud</surname>
                        <given-names>Doaa</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <role content-type="http://credit.niso.org/">Investigation</role>
                    <role content-type="http://credit.niso.org/">Resources</role>
                    <role content-type="http://credit.niso.org/">Supervision</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Review &amp; Editing</role>
                    <uri content-type="orcid">https://orcid.org/0009-0007-8410-8367</uri>
                    <xref ref-type="corresp" rid="c1">a</xref>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Hammad</surname>
                        <given-names>Hayssam</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Data Curation</role>
                    <role content-type="http://credit.niso.org/">Formal Analysis</role>
                    <role content-type="http://credit.niso.org/">Methodology</role>
                    <role content-type="http://credit.niso.org/">Project Administration</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Original Draft Preparation</role>
                    <xref ref-type="aff" rid="a2">2</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Adnan Sulaiman</surname>
                        <given-names>Suzali</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Investigation</role>
                    <role content-type="http://credit.niso.org/">Resources</role>
                    <role content-type="http://credit.niso.org/">Software</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Original Draft Preparation</role>
                    <xref ref-type="aff" rid="a3">3</xref>
                </contrib>
                <aff id="a1">
                    <label>1</label>College of Law, Capital University, Helwan, Egypt</aff>
                <aff id="a2">
                    <label>2</label>private law, Abu Dhabi University, Abu Dhabi, Abu Dhabi, United Arab Emirates</aff>
                <aff id="a3">
                    <label>3</label>public law, Abu Dhabi University, Abu Dhabi, Abu Dhabi, United Arab Emirates</aff>
            </contrib-group>
            <author-notes>
                <corresp id="c1">
                    <label>a</label>
                    <email xlink:href="mailto:doaa.droit@gmail.com">doaa.droit@gmail.com</email>
                </corresp>
                <fn fn-type="conflict">
                    <p>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>8</day>
                <month>7</month>
                <year>2026</year>
            </pub-date>
            <pub-date pub-type="collection">
                <year>2026</year>
            </pub-date>
            <volume>15</volume>
            <elocation-id>1106</elocation-id>
            <history>
                <date date-type="accepted">
                    <day>2</day>
                    <month>6</month>
                    <year>2026</year>
                </date>
            </history>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2026 mahmoud D et al.</copyright-statement>
                <copyright-year>2026</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access article distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <self-uri content-type="pdf" xlink:href="https://f1000research.com/articles/15-1106/pdf"/>
            <abstract>
                <title>
</title>
                <sec>
                    <title>Background</title>
                    <p>Smart contracts depending on blockchain technology have emerged as a transformative mechanism for the execution of contractual obligations in electronic commerce and digital transactions. Their growing adoption in commercial practice has generated significant legal debate concerning their compatibility with traditional contract theory and existing civil and commercial legal frameworks. Smart contracts raise complex questions relating to contractual consent, interpretation, defects of will, allocation of liability, electronic signatures, judicial intervention, and the enforceability of court decisions within decentralized and immutable blockchain environments.</p>
                </sec>
                <sec>
                    <title>Methods</title>
                    <p>This study adopts a doctrinal and comparative legal methodology to examine the legal nature of smart contracts as code-based agreements operating through blockchain technology. It analyses the relationship between smart contracts and classical contract principles by comparing traditional legal rules governing contract formation and enforcement with the technological characteristics of blockchain systems, including automation, decentralization, immutability, and self-execution. The study further evaluates selected legislative and regulatory approaches relating to electronic contracts, electronic signatures, and digital transactions in comparative legal systems.</p>
                </sec>
                <sec>
                    <title>Results</title>
                    <p>The study demonstrates that smart contracts should not be regarded as mechanisms existing outside traditional contract law, but rather as hybrid instruments combining legal commitment with automated execution through computer code. It further finds that the traditional elements of contract formation, including offer and acceptance, lawful subject matter, contractual intention, form requirements, and electronic signatures, may generally be satisfied within smart-contract environments. Nevertheless, the research identifies several legal and practical challenges associated with smart contracts, particularly coding errors, security vulnerabilities, informational asymmetries, immutability, defects of consent, difficulties of contractual interpretation, and obstacles to judicial enforcement on decentralized ledgers.</p>
                </sec>
                <sec>
                    <title>Conclusions</title>
                    <p>The paper concludes that smart contracts can be effectively integrated into existing legal frameworks through hybrid contractual documentation, targeted legislative regulation, and adaptive judicial interpretation. Such integration would allow legal systems to benefit from the efficiency, certainty, transparency, and reduced transaction costs offered by blockchain technology while simultaneously preserving contractual justice, legal certainty, and consumer protection.</p>
                </sec>
            </abstract>
            <kwd-group kwd-group-type="author">
                <kwd>Smart contracts; blockchain; distributed ledger technology (DLT); contract formation; electronic signature; consent and defects of will; DeFi; DAOs; regulation</kwd>
            </kwd-group>
            <funding-group>
                <funding-statement>The author(s) declared that no grants were involved in supporting this work.</funding-statement>
            </funding-group>
        </article-meta>
    </front>
    <body>
        <sec id="sec5" sec-type="intro">
            <title>Introduction</title>
            <p>Contemporary legal reality is undergoing a profound transformation driven by the digital revolution and distributed ledger technologies, foremost among them blockchain, which was initially developed as the underlying infrastructure for the Bitcoin cryptocurrency and has since expanded into the fields of finance, real estate, supply chains, insurance, government services, and other economic sectors. This evolution has provided a fertile technological environment for the emergence of new forms of transactions, most notably smart contracts, which operate through self-executing code deployed on a distributed network rather than being embodied in a paper instrument or even in a traditional electronic document.
                <xref ref-type="bibr" rid="ref1">
                    <sup>1</sup>
                </xref>
                <sup>,</sup>
                <xref ref-type="bibr" rid="ref2">
                    <sup>2</sup>
                </xref>
                <sup>,</sup>
                <xref ref-type="bibr" rid="ref3">
                    <sup>3</sup>
                </xref>
            </p>
            <p>In this context, the contract is no longer merely an agreement drafted in natural language and enforcement is entrusted to courts, arbitral tribunals, or enforcement authorities.
                <xref ref-type="bibr" rid="ref4">
                    <sup>4</sup>
                </xref>
                <sup>,</sup>
                <xref ref-type="bibr" rid="ref5">
                    <sup>5</sup>
                </xref> It has become possible to translate contractual intent into a strict computational logic such as &#x201c;if condition (X) is fulfilled, effect (Y) is executed&#x201d;, without any human intervention at the stage of performance. This development has sparked intense debate over the accuracy of the well-known claim that &#x201c;code is law&#x201d; and over the limits of party autonomy when it is locked into a code-based framework that is, in practice, barely reversible or amendable, given the characteristics of blockchain in terms of decentralization, transparency, and the difficulty of altering the ledger once entries have been recorded.
                <xref ref-type="bibr" rid="ref2">
                    <sup>2</sup>
                </xref>
                <sup>,</sup>
                <xref ref-type="bibr" rid="ref6">
                    <sup>6</sup>
                </xref>
                <sup>,</sup>
                <xref ref-type="bibr" rid="ref20">
                    <sup>20</sup>
                </xref>
            </p>
            <p>Before the advent of blockchain, the automation of contractual performance was typically carried out through software programs operating under the supervision of one of the parties or an external intermediary. In such a setting, it was possible to suspend performance or correct it and to refer the dispute to the courts whenever an error occurred or a breach of contractual obligations was alleged. This mechanism allowed a degree of control over performance, helped strike a balance between efficiency and fairness, and preserved a margin of discretion for judges or arbitrators when exceptional circumstances, exploitation, or ambiguity in the interpretation of terms arose.
                <xref ref-type="bibr" rid="ref7">
                    <sup>7</sup>
                </xref> By contrast, in the environment of smart contracts operating on blockchain, the logic of automatic self-execution upon satisfaction of the programmed conditions substantially reduces, in principle, the possibility of having an effective &#x201c;emergency stop button&#x201d;. This places the traditional rules governing civil and commercial contracts before a genuine challenge, requiring a rethinking and development of their concepts and tools if smart contracts are to be integrated into the existing contractual framework rather than left in a legal grey area at its margins.
                <xref ref-type="bibr" rid="ref7">
                    <sup>7</sup>
                </xref>
                <sup>,</sup>
                <xref ref-type="bibr" rid="ref8">
                    <sup>8</sup>
                </xref>
                <sup>,</sup>
                <xref ref-type="bibr" rid="ref46">
                    <sup>46</sup>
                </xref>
            </p>
            <p>Admittedly, smart contracts significantly reduce the possibility that one of the parties will unilaterally default on the performance of its obligations, since the code-based architecture renders performance automatic so long as the party has consented to the contract and accepted its operational logic. From this perspective, smart contracts may be seen as a tool for strengthening legal certainty, promoting faithful performance, and limiting opportunistic breach by contracting parties an issue of fundamental importance in commercial transactions.
                <xref ref-type="bibr" rid="ref9">
                    <sup>9</sup>
                </xref>
            </p>
            <p>However, the environment in which such contracts are expected to flourish is one of high-volume, cross-border, and rapidly concluded and executed transactions, which may involve digital platforms and decentralized autonomous organizations (DAOs) operating through interlinked bundles of smart contracts. In such a setting, any programming error or security vulnerability as illustrated by several high-profile incidents on blockchain platforms may lead to substantial financial losses or to contractual outcomes that were never contemplated by the parties, while the technical ability of judicial and regulatory authorities to intervene and correct the course of performance appears inherently limited, unless these contracts are redesigned ex-ante with a clear legal consciousness and safeguards in mind.
                <xref ref-type="bibr" rid="ref6">
                    <sup>6</sup>
                </xref>
                <sup>,</sup>
                <xref ref-type="bibr" rid="ref20">
                    <sup>20</sup>
                </xref>
            </p>
            <p>Considering the above, the classical questions of contract law concerning the very notion of the contract, its essential elements, and the conditions for its validity are being revisited. A central issue arises with respect to the requirement of consent in a contractual framework where party autonomy is expressed through digital interfaces or cryptographic keys: to what extent can one legitimately presume that the contracting party has sufficient knowledge of the underlying code and its legal and economic implications, given the technical complexity that creates a structural information gap between the programmer or platform, on the one hand, and the ordinary contracting party or even the moderately sophisticated trader on the other? This, in turn, calls for a renewed examination of the traditional doctrines on defects of consent, such as mistake, misrepresentation, duress and unconscionability/exploitation, in the context of contracts whose performance is carried out automatically by a &#x201c;machine&#x201d;. It raises further question whether, and under what conditions, a smart contract may be set aside once it has already been executed on-chain, and how such avoidance can be operationalized in practice given the inherent difficulty of unwinding transactions recorded on a blockchain.
                <xref ref-type="bibr" rid="ref7">
                    <sup>7</sup>
                </xref>
            </p>
            <p>The discussion also extends to the form of the contract, writing and signature. While many legal systems have recognized electronic writing and electronic signatures for the purposes of civil and commercial transactions, smart contracts introduce a more complex architecture based on public-private key cryptography and the linkage of such keys to parties&#x2019; digital identities, and in some public chains a degree of pseudonymity or anonymity remains possible. This raises intricate questions regarding legal capacity, the identification of the &#x201c;person&#x201d; who ultimately bears rights, obligations and risks, as well as the determination of the applicable law and competent forum in transactions that are distributed both geographically and technologically.
                <xref ref-type="bibr" rid="ref42">
                    <sup>42</sup>
                </xref> In addition, smart contracts give rise to refined issues relating to the performance of obligations and civil liability: the self-executing nature of the code constrains the traditional role of courts in directing, suspending or adapting performance, and the occurrence of a coding error or the exploitation of a vulnerability prompts difficult questions as to who should bear responsibility; the programmer, the platform operator, the parties who accepted the code without adequate understanding, or some combination thereof and according to which criteria. These are issues that legal doctrine and case law will need to address and systematize in the coming years.
                <xref ref-type="bibr" rid="ref6">
                    <sup>6</sup>
                </xref>
            </p>
            <p>Moreover, a further concern relates to the potential use of the self-executing mechanism as a means of circumventing mandatory rules or of giving an ostensibly &#x201c;automatic&#x201d; character to arrangements which, in substance, operate to pre-emptively seize the debtor&#x2019;s assets or to erode the legal safeguards granted to him by the legislature. This, in turn, calls upon legislative, judicial and regulatory authorities to develop appropriate tools to ensure that such contracts do not become an instrument for evading public-order constraints in commercial transactions, while at the same time avoiding excessive intervention that might stifle innovation and hinder the adoption of new technologies.
                <xref ref-type="bibr" rid="ref8">
                    <sup>8</sup>
                </xref>
                <sup>,</sup>
                <xref ref-type="bibr" rid="ref11">
                    <sup>11</sup>
                </xref>
                <sup>,</sup>
                <xref ref-type="bibr" rid="ref7">
                    <sup>7</sup>
                </xref>
                <sup>,</sup>
                <xref ref-type="bibr" rid="ref1">
                    <sup>1</sup>
                </xref>
                <sup>,</sup>
                <xref ref-type="bibr" rid="ref2">
                    <sup>2</sup>
                </xref>
                <sup>,</sup>
                <xref ref-type="bibr" rid="ref10">
                    <sup>10</sup>
                </xref>
                <sup>,</sup>
                <xref ref-type="bibr" rid="ref20">
                    <sup>20</sup>
                </xref>
                <sup>,</sup>
                <xref ref-type="bibr" rid="ref47">
                    <sup>47</sup>
                </xref>
            </p>
            <sec id="sec6">
                <title>Significance of the study</title>
                <p>Against this backdrop, the present study undertakes an examination the smart contract from two interrelated angles: the angle of definition and theoretical grounding, and the angle of legal regulation and the practical issues arising from its characterization within the system of civil and commercial contracts.</p>
                <p>It seeks, first, to formulate a precise legal definition of the smart contract that reconciles technical requirements with the concepts of contract law, and that highlights it as a contractual model distinct from forms of electronic contracting or traditional automation, in terms of self-execution, its original non-susceptibility to human suspension or modification, and its reliance on a distributed architecture.</p>
                <p>Secondly, it seeks to elucidate its legal nature and to determine whether it can be included within existing models (such as the electronic contract or the automated management contract), or whether it constitutes a special model that calls for distinct legislative regulation. Thirdly, it aims to identify and analyze the issues related to the element of consent and its defects in a complex digital environment, the limits of knowledge of the content of the code, and the possibility of applying the doctrines of mistake, fraud, duress and exploitation, in addition to interpretative problems when there is a conflict between the logic of the code and the true intention of the parties, and the problems of compulsory enforcement, liability, and the determination of the applicable law and judicial jurisdiction in distributed, cross-border transactions.
                    <xref ref-type="bibr" rid="ref6">
                        <sup>6</sup>
                    </xref>
                </p>
                <p>On this basis, the study adopts a problem-oriented framework centered on a set of principal questions, including: How can the smart contract be defined in precise legal terms that take account of its technical elements without undermining the fundamental concepts of contract law? To what extent can the smart contract be accommodated within the general rules governing civil and commercial contracts, or is it necessary to acknowledge that it has a special nature of its own? What is the effect of the self-executing mechanism on the element of consent and on the possibility of applying the doctrines of defects of will in cases of mistake, misrepresentation, duress or exploitation? How can the practical issues relating to the interpretation of smart contracts, their performance and their suspension where necessary be addressed, and to whom liability should be attributed in the event of coding errors or the exploitation of vulnerabilities? And are judicial interpretation and doctrinal development within the framework of existing texts sufficient to integrate smart contracts into the traditional contractual regime, particularly in the field of commercial transactions and e-commerce, or does the matter require legislative amendments and qualitative additions?.
                    <xref ref-type="bibr" rid="ref19">
                        <sup>19</sup>
                    </xref>
                </p>
                <p>Taken together, these questions are intended to guide the analysis towards constructing an integrated vision for defining, characterizing and regulating the smart contract, in a manner that reconciles, on the one hand, the promotion of technological innovation and, on the other, the requirements of contractual justice, the protection of contracting parties and the stability of commercial transactions, with a view to making smart contracts an instrument that complements, rather than conflicts with, the existing contractual system.
                    <xref ref-type="bibr" rid="ref3">
                        <sup>3</sup>
                    </xref>
                </p>
            </sec>
            <sec id="sec7">
                <title>History of smart contracts</title>
                <p>Smart contracts existed long before they were designated by that name. Contracting parties had long been searching for mechanisms to reduce enforcement costs, without necessarily adopting any specific legal or academic framework in doing so. Contemporary examples of such mechanisms include subway ticketing systems, bike-sharing programmes, and electronic toll collection systems on highways.
                    <xref ref-type="bibr" rid="ref24">
                        <sup>24</sup>
                    </xref>
                </p>
                <p>The expression &#x201c;smart contracts&#x201d; first appeared in 1997, when they were defined as contractual clauses embedded in hardware and software in a manner that makes breach more costly. At that time, the concept was illustrated by two key examples: vending machines and devices used to repossess cars pledged as security for a loan.
                    <xref ref-type="bibr" rid="ref3">
                        <sup>3</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref29">
                        <sup>29</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref23">
                        <sup>23</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref25">
                        <sup>25</sup>
                    </xref>
                </p>
                <p>Smart contracts came to represent a fundamental shift away from paper-based arrangements towards digital systems by reducing intermediation costs in enforcement, enabling self-execution, and limiting the need for arbitration or litigation, for instance, in banking services supported by computers and digital databases. Naturally, this shift could not occur overnight, given the long history and deep entrenchment of paper-based contracting practices.
                    <xref ref-type="bibr" rid="ref25">
                        <sup>25</sup>
                    </xref>
                </p>
                <p>The true emergence of smart contracts, in their modern sense, coincided with the advent of Bitcoin and the spread of blockchain technology from 2008 onwards. The success of the Bitcoin protocol as a large-scale experiment in the use of decentralised databases provided a crucial foundational infrastructure for the development and deployment of smart contracts.
                    <xref ref-type="bibr" rid="ref25">
                        <sup>25</sup>
                    </xref>
                </p>
            </sec>
        </sec>
        <sec id="sec8" sec-type="methods">
            <title>Methods</title>
            <sec id="sec9">
                <title>Study design</title>
                <p>This study adopts a doctrinal and comparative legal research design. It focuses on the analytical examination of smart contracts as hybrid legal-technical instruments within the framework of traditional contract law. The research is qualitative in nature and does not rely on empirical or quantitative data, but rather on legal reasoning and interpretation.</p>
            </sec>
            <sec id="sec10">
                <title>Data sources</title>
                <p>The study is based on primary and secondary legal sources. Primary sources include legislation, regulatory instruments, and international legal texts such as European Union regulations, UNCITRAL model laws, and national legal frameworks. Secondary sources consist of academic books, peer-reviewed journal articles, and authoritative reports addressing blockchain technology and smart contracts.</p>
            </sec>
            <sec id="sec11">
                <title>Analytical approach</title>
                <p>The research employs a doctrinal method to interpret and evaluate legal rules governing contract formation, consent, liability, and enforcement. In addition, a comparative approach is used to examine different legal systems, particularly the European Union and the United States, to identify similarities, divergences, and emerging regulatory trends.</p>
            </sec>
            <sec id="sec12">
                <title>Reproducibility and transparency</title>
                <p>The methodology ensures transparency and reproducibility by relying exclusively on publicly available and properly cited legal materials. All sources are clearly referenced, allowing other researchers to verify and replicate the analytical process.</p>
            </sec>
        </sec>
        <sec id="sec13" sec-type="results">
            <title>Results</title>
            <p>smart contracts and blockchain-based architectures do not abolish the traditional law of obligations; rather, they expose its fault lines and force a reconsideration of several of its core assumptions. The study has shown that, despite their technical sophistication, smart contracts can at least in a large subset of their uses be analysed within the existing conceptual framework of civil and commercial contracts. Offer and acceptance, subject-matter, intention to create legal relations, and certainty of terms can all be identified in code-based transactions, even when these are expressed through cryptographic keys and executed automatically on a decentralised ledger. At the same time, the features that render smart contracts innovative self-execution, immutability (in &#x201c;strong&#x201d; forms), and reliance on distributed consensus have significant implications for consent, defects of will, interpretation, performance, and remedies, especially where there is an asymmetry of information between coders, platforms and users.</p>
            <p>The research has further demonstrated that blockchain is not a neutral &#x201c;background&#x201d; technology. Its consensus mechanisms, cryptographic guarantees and governance models (public, consortium, private) shape the risk allocation between parties, the possibility and cost of unwinding transactions, and the extent to which courts and regulators can intervene ex post. In this sense, the slogan &#x201c;code is law&#x201d; is both overstated and revealing overstated because smart contracts ultimately derive their legal effects from the surrounding legal order, but revealing because, in practice, the technical design of code and infrastructure often determines which legal remedies remain realistically available. The challenge for contemporary contract law is therefore not whether to recognise smart contracts as &#x201c;real&#x201d; contracts, but how to integrate them coherently into the general regime while preserving contractual justice, the protection of weaker parties and the stability of commercial transactions.</p>
        </sec>
        <sec id="sec14">
            <title>Main findings</title>
            <p>

                <list list-type="order">
                    <list-item>
                        <label>1-</label>
                        <p>

                            <bold>

                                <italic toggle="yes">Definitional and conceptual clarity</italic>:</bold> A smart contract is an agreement implemented in code on a distributed ledger, rather than &#x201c;code alone&#x201d;; its dual character as legal undertaking and technical execution layer distinguishes it from ordinary electronic contracts and simple automation tools.</p>
                    </list-item>
                    <list-item>
                        <label>2-</label>
                        <p>

                            <bold>

                                <italic toggle="yes">Continuity of contractual elements</italic>
</bold>: In both common-law and civil-law systems, the core requirements of contract formation can in principle be satisfied in a smart-contract environment: offer and acceptance may be expressed through code deployment and interaction, the subject-matter typically consists of digital or tokenised assets, intention to create legal relations may be inferred from participation in the protocol, and the deterministic nature of code generally enhances certainty as to terms and performance.</p>
                    </list-item>
                    <list-item>
                        <label>3-</label>
                        <p>

                            <bold>

                                <italic toggle="yes">Consent and defects of will in a digital environment</italic>
</bold>: The technical complexity of smart contracts and the information gap between programmers/platforms and ordinary users raise acute concerns regarding informed consent, mistakes, misrepresentation, duress and exploitation. While the performance layer is automated, the underlying will remain that of human or corporate parties, which calls for a cautious transposition of the classical doctrines on defects of consent to on-chain transactions.</p>
                    </list-item>
                    <list-item>
                        <label>4-</label>
                        <p>

                            <bold>

                                <italic toggle="yes">Form, signature and identification</italic>
</bold>: The spread of electronic signatures and public-key infrastructures has facilitated the attribution of cryptographic acts to legal people. Instruments such as the U.S. Uniform Electronic Transactions Act and the EU EIDAS Regulation support the functional equivalence between qualified electronic signatures and handwritten signatures, thereby providing a doctrinal bridge for treating blockchain-based signatures as evidence of consent, subject to appropriate identity-linking mechanisms.</p>
                    </list-item>
                    <list-item>
                        <label>5-</label>
                        <p>

                            <bold>

                                <italic toggle="yes">Conditional logic and self-execution:</italic>
</bold> Smart contracts operationalize, in code, the conditional structure already familiar to contract law (&#x201c;if condition X occurs, effect Y follows&#x201d;). Their &#x201c;smartness&#x201d; lies less in any form of artificial intelligence than in the systematic application of Boolean logic to performance. This greatly reduces ex post opportunism and many traditional forms of breach but also displaces a substantial part of judicial and arbitral discretion to the ex-ante design stage.</p>
                    </list-item>
                    <list-item>
                        <label>6-</label>
                        <p>

                            <bold>

                                <italic toggle="yes">Interpretation and the gap between code and intent</italic>
</bold>: The study highlights a structural tension between the aspiration to treat code as the final arbiter of the transaction and the persistent need to interpret contractual intent where code behaves unexpectedly, contains bugs, or embeds economic allocations that parties did not fully understand as illustrated by incidents such as the DAO attack. Hybrid models (legal prose + parameters + code) and the possibility of relying on expert evidence suggest that classical interpretative tools will continue to play a role, although their operation is constrained by the technical architecture.</p>
                    </list-item>
                    <list-item>
                        <label>7-</label>
                        <p>

                            <bold>

                                <italic toggle="yes">Regulatory embedding rather than legal vacuum:</italic>
</bold> Distributed ledger technologies and smart-contract platforms increasingly operate under specific regulatory regimes: crypto-asset and DLT-market regulations, AML/CFT frameworks, data-protection law (e.g. GDPR), and specialized virtual-asset regulations at national level (such as those adopted in the UAE). These regimes recognize the supervisory value of transparent, auditable ledgers while simultaneously imposing obligations concerning licensing, governance, disclosure and customer due diligence.
                            <xref ref-type="bibr" rid="ref20">
                                <sup>34</sup>
                            </xref>
                            <sup>,</sup>
                            <xref ref-type="bibr" rid="ref40">
                                <sup>40</sup>
                            </xref>
                            <sup>,</sup>
                            <xref ref-type="bibr" rid="ref42">
                                <sup>42</sup>
                            </xref>
                            <sup>,</sup>
                            <xref ref-type="bibr" rid="ref45">
                                <sup>45</sup>
                            </xref>
                        </p>
                    </list-item>
                    <list-item>
                        <label>8-</label>
                        <p>

                            <bold>

                                <italic toggle="yes">Differentiation between &#x201c;strong&#x201d; and &#x201c;weak&#x201d; smart contracts:</italic>
</bold> In practice, many smart contracts remain &#x201c;weak&#x201d; in the sense that they can be modified or overridden by the parties, platform operators or courts at acceptable cost. Truly &#x201c;strong&#x201d; contracts, whose alteration would entail prohibitive technical or economic consequences, pose the most acute challenges for private law and enforcement, and thus demand particular attention from doctrine and regulators.</p>
                    </list-item>
                </list>
            </p>
        </sec>
        <sec id="sec15" sec-type="discussion">
            <title>Discussion</title>
            <sec id="sec16">
                <title>Definition and legislative regulation of smart contract</title>
                <p>

                    <bold>

                        <italic toggle="yes">First: Definition of Smart Contract</italic>
</bold>
                </p>
                <p>According to the simplest definition, a smart contract is an agreement that is executed automatically. It may also be defined as transaction code created through a computer program, which implements the terms of the contract.
                    <xref ref-type="bibr" rid="ref30">
                        <sup>30</sup>
                    </xref> However, this definition does not draw a clear distinction between &#x201c;smart&#x201d; contracts and certain already known contractual arrangements that perform automatic execution, such as vending machines.
                    <xref ref-type="bibr" rid="ref30">
                        <sup>30</sup>
                    </xref>
                </p>
                <p>Smart contracts are likewise defined as agreements existing in the form of an electronic program deployed on a particular blockchain, whereby this program ensures the autonomy and self-executing nature of the provisions of the smart contract based on a set of predetermined factors.
                    <xref ref-type="bibr" rid="ref26">
                        <sup>26</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref14">
                        <sup>14</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref18">
                        <sup>18</sup>
                    </xref>
                </p>
                <p>Some authors consider human intervention to be an element in the operation of smart contracts, and therefore define them as an agreement that is capable of automatic execution and operation by computer, even though certain parts may require human input or control, and that is enforceable either through the legal enforcement/compulsion of rights and obligations or through the secure execution of the computer program.
                    <xref ref-type="bibr" rid="ref16">
                        <sup>16</sup>
                    </xref>
                </p>
                <p>Smart contracts are defined as agreements in which performance is carried out automatically, usually by computers. They are designed to ensure performance without recourse to the courts. This automatic performance ensures that human discretion is excluded from the framework of contract execution. A smart contract is a set of code instructions stored on a decentralised electronic database (blockchain) and executed/activated by the transactions that take place.
                    <xref ref-type="bibr" rid="ref25">
                        <sup>25</sup>
                    </xref>
                </p>
                <p>

                    <bold>

                        <italic toggle="yes">Second: Legislative Regulation of Smart Contracts</italic>
</bold>
                </p>
                <p>Many U.S. states have enacted legislation specifically addressing smart contracts, which may not, in fact, be particularly &#x201c;smart&#x201d;, given that they have created a hybrid system of inconsistent ideas and principles, resulting in further confusion.
                    <xref ref-type="bibr" rid="ref21">
                        <sup>21</sup>
                    </xref>
                </p>
                <p>For example, in the State of Arizona, a smart contract has been defined as: &#x201c;an event-driven program, that runs on a distributed, decentralised, shared and replicated ledger and that can take custody over and instruct transfer of assets on that ledger.&#x201d; (Arizona Revised Statutes Annotated &#x00a7; 44&#x2013;7061).
                    <xref ref-type="bibr" rid="ref21">
                        <sup>21</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref35">
                        <sup>35</sup>
                    </xref>
                </p>
                <p>Outside the United States, in 2017 Belarus became the first country to legislate for the smart contract, defining it in a presidential decree as: &#x201c;a computer program designed to function on a shared distributed platform for the purposes of automatic performance and/or execution of transactions or the performance of other legal acts.&#x201d;
                    <xref ref-type="bibr" rid="ref36">
                        <sup>36</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref26">
                        <sup>26</sup>
                    </xref>
                </p>
                <p>Based on the features mentioned above, it is possible to define the smart contract as an electronic program executed on a blockchain platform, which embodies the self-executing and autonomous nature of its provisions that are triggered by pre-defined conditions and applied to assets recorded on the blockchain platform. From a technical perspective, it is defined as a self-executing program operating on a shared decentralised distributed platform, namely the blockchain.
                    <xref ref-type="bibr" rid="ref26">
                        <sup>26</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref44">
                        <sup>44</sup>
                    </xref>
                </p>
                <p>

                    <bold>

                        <italic toggle="yes">Advantages of Smart Contracts</italic>
</bold>
                </p>
                <p>There are many advantages of smart contracts, which can be summarized in:</p>
                <p>

                    <italic toggle="yes">
Self-Executing Nature of Smart Contracts</italic>
                </p>
                <p>What renders smart contracts genuinely innovative is that their performance is carried out automatically using computers; this innovation makes it possible for declarations of intent to be formulated and expressed in the form of self-executing computer code. Once a smart contract has been concluded, its performance no longer depends on the will of the parties or of any third person, and it does not require any further consent or additional steps on the part of any of them. All that occurs is that the relevant computer program verifies that all the conditions have been satisfied, then transfers the assets and makes specific entries in the blockchain database concerning the asset transfer that has taken place.
                    <xref ref-type="bibr" rid="ref31">
                        <sup>31</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref37">
                        <sup>37</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref38">
                        <sup>38</sup>
                    </xref>
                </p>
                <p>Accordingly, the smart contract is, from a technical standpoint, binding on all the parties to it and no longer relies on a human intermediary who may be prone to error or subjective judgment. Any change in circumstances, or in the intention of either party after the date of conclusion of the contract, becomes irrelevant. There is thus no room for opportunistic behavior such as breaching the terms of the contract to maximize the benefit of the breaching party (efficient breach).
                    <xref ref-type="bibr" rid="ref26">
                        <sup>26</sup>
                    </xref>
                </p>
                <p>A smart contract does not require any legal institutions for its existence: no enforcement agencies, and no supplementary or mandatory legal rules to fill gaps in the contract, as is the case with classical contracts when they are incomplete. This is referred to as the self-sufficiency of the smart contract.
                    <xref ref-type="bibr" rid="ref26">
                        <sup>26</sup>
                    </xref> It is important to note that self-sufficiency is particularly significant in cross-border transactions, as it precludes reliance on differences in language, national laws and their interpretation [including various forms of geopolitical economic sanctions]; the same rules are, in principle, capable of being applied uniformly worldwide.
                    <xref ref-type="bibr" rid="ref25">
                        <sup>25</sup>
                    </xref>
                </p>
                <p>

                    <italic toggle="yes">Reliance on Algorithmic Execution versus Reliance on Personal Trust in Contract Performance</italic>
                </p>
                <p>Given that, once a smart contract has been concluded, the contracting party is no longer able to influence its performance, a substantial degree of trust is required to sustain this type of &#x201c;fiduciary&#x201d; relationship within the smart contract. However, unlike the classical contract, where trust is placed in the personality and good faith of the other party, in smart contracts such trust is reallocated and placed in the computer algorithm that underpins the agreement.
                    <xref ref-type="bibr" rid="ref26">
                        <sup>26</sup>
                    </xref>
                </p>
                <p>

                    <italic toggle="yes">Aggregation and Allocation of Funds through Smart Contracts</italic>
                </p>
                <p>Smart contracts make it possible to create aggregations of resources and to allocate them in accordance with agreed criteria, which may be particularly suitable for activities such as crowdfunding or insurance contracts.
                    <xref ref-type="bibr" rid="ref26">
                        <sup>26</sup>
                    </xref>
                </p>
                <p>

                    <italic toggle="yes">Example:</italic> A smart contract may track the amount of funds contributed to a crowdfunding project and, once the total required amount has been reached, that sum is transferred to the beneficiary; otherwise, the funds are returned to the contributors.
                    <xref ref-type="bibr" rid="ref26">
                        <sup>26</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref16">
                        <sup>16</sup>
                    </xref>
                </p>
                <p>

                    <italic toggle="yes">Immutability/Stability of Smart Contracts</italic>
                </p>
                <p>The immutability of smart contracts deprives them of the flexibility characteristic of traditional contractual relationships and prevents the parties from adjusting their positions in response to changing circumstances. This problem was revealed in June 2016 during the hack of the Decentralised Autonomous Organization (DAO) a fundraising vehicle that had raised USD 168 million when it was launched on the Ethereum platform in 2016.
                    <xref ref-type="bibr" rid="ref21">
                        <sup>21</sup>
                    </xref>
                </p>
                <p>

                    <bold>

                        <italic toggle="yes">What happened to Ethereum in 2016?</italic>
</bold>
                </p>
                <p>first, Ethereum is commonly described as an open blockchain-based infrastructure that enables the development and operation of decentralized applications within a distributed environment. Unlike the Bitcoin protocol, Ethereum was intentionally designed to be adaptable and flexible, functioning as a general-purpose platform aimed at supporting the execution of smart contracts in a trust less setting. The platform itself is functionally neutral and does not prescribe specific uses in advance, leaving developers and entrepreneurs free to determine its applications.</p>
                <p>Nevertheless, Ethereum is particularly well suited to use cases that automate direct peer-to-peer interactions or facilitate coordinated collective activity across decentralized networks, especially in the context of peer-to-peer marketplaces and complex financial arrangements. While Bitcoin primarily enables the transfer of value without intermediaries, Ethereum, in theory, extends this capability by allowing highly sophisticated financial and organizational transactions to be executed automatically through self-executing code.
                    <xref ref-type="bibr" rid="ref14">
                        <sup>14</sup>
                    </xref>
                </p>
                <p>When the attacker exploited a flaw in a smart contract to withdraw more than USD 50 million from the DAO, the Ethereum community began to question the principle of immutability of the Ethereum platform. The Ethereum Foundation decided to intervene on behalf of the DAO investors in effect, to &#x201c;bail them out&#x201d; by rewriting the core Ethereum code to invalidate the attacker&#x2019;s transactions and recover the funds.
                    <xref ref-type="bibr" rid="ref21">
                        <sup>21</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref14">
                        <sup>14</sup>
                    </xref>
                </p>
                <p>To do so, the Foundation, influenced by the heavily invested founders of the platform, persuaded most users to agree to its decision. To reverse the transfers, a fork was created which altered the Ethereum protocol and returned the stolen tokens as if the hack had never occurred.</p>
                <p>However, this breach of the platform&#x2019;s immutability/stability was highly controversial and led to a split within the Ethereum community, as a minority of participants chose to continue with the original, unmodified code. As a result, Ethereum split into two parallel crypto &#x201c;worlds&#x201d;, identical in most respects but with one key difference: the forked Ethereum world effectively treated the DAO smart contracts as voidable by all participants on the basis of mutual mistake, whereas the unforced Ethereum world continued to treat the attack as a valid transaction under the terms of the DAO smart contract.
                    <xref ref-type="bibr" rid="ref14">
                        <sup>14</sup>
                    </xref>
                </p>
                <p>The DAO incident illustrates a fundamental disjunction between legal remedies and technical execution in smart contracts. While a court may declare a contract void or rescinded as a matter of law, such a declaration cannot be directly implemented at the technical level of an immutable blockchain. Unlike traditional contracts, where nullity retroactively eliminates legal effects, the execution of a smart contract produces irreversible transactions that remain permanently recorded on the ledger. Any attempt to &#x201c;reverse&#x201d; such effects through technical means whether by offsetting transactions or protocol-level intervention does not replicate the legal consequence of treating the contract as if it had never existed but rather substitutes it with a new set of transactions. This structural mismatch exposes the limits of judicial remedies when confronted with self-executing, immutable contractual architectures.
                    <xref ref-type="bibr" rid="ref14">
                        <sup>14</sup>
                    </xref>
                </p>
                <p>A further problem arising from the immutable nature of smart contracts concerns the way a court decision declaring a smart contract void is to be implemented. It is evident that &#x201c;replacing&#x201d; the transaction with a new one that fully offsets the existing transaction and neutralises its effects will not lead to the same result as treating the contract as though it had never existed in the first place.</p>
                <p>

                    <italic toggle="yes">Limited Modifiability and Irrevocability of Smart Contracts:</italic>
                </p>
                <p>In traditional contracts, the need to amend contractual terms frequently arises, and, when smart contracts are examined, several new issues likewise emerge that would, in principle, call for contractual modification. As a basic rule, once a smart contract has been coded and deployed on the blockchain, it continues to run until performance is completed; this is precisely what enables the smart contract to attain a high degree of certainty.</p>
                <p>Smart contracts are characterised by their non-revocability. Their performance is guaranteed by the cryptographic functions employed within the decentralised environment known as the blockchain. Once a smart contract has been concluded between the parties, its performance and enforcement are ensured by an immutable computer program. This allows the parties to place less trust in one another and instead to rely on the automated machinery of the blockchain to execute their obligations, irrespective of any subsequent change of mind that may occur after the contract has been formed.
                    <xref ref-type="bibr" rid="ref27">
                        <sup>27</sup>
                    </xref>
                </p>
                <p>

                    <bold>

                        <italic toggle="yes">How Smart Contracts Operate</italic>
</bold>
                </p>
                <p>Smart contracts operate by recording the ownership of digital assets or the digital representation of off-chain assets on a blockchain platform. This electronic contractual form provides an embedded activation mechanism, enabling the parties to trigger performance based on specific electronic events written into the blockchain. Furthermore, because smart contracts rely on cryptographic techniques, every interaction with the contract requires the use of a digital signature or cryptographic key associated with the relevant party.
                    <xref ref-type="bibr" rid="ref15">
                        <sup>15</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref38">
                        <sup>38</sup>
                    </xref>
                </p>
                <p>

                    <italic toggle="yes">Smart Contracts, Algorithms and Blockchain (Contract ware)</italic>
                </p>
                <p>Some commentators consider that, with the rapid development of technology, software-based equations (code) will be created to govern all types of contractual transactions.
                    <xref ref-type="bibr" rid="ref30">
                        <sup>30</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref29">
                        <sup>29</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref15">
                        <sup>15</sup>
                    </xref>
                </p>
                <p>The spread of distributed ledger technologies (DLT) has prompted renewed discussion about the use of technology to enforce agreements between individuals without recourse to third parties. New companies and protocols have assembled core code libraries for drafting smart contracts. This code exists independently of the Bitcoin system. These new entities are working to build an ecosystem for experimenting with the implementation of smart contracts, and a substantial body of literature has emerged on the subject, most of it from a technical or financial perspective.
                    <xref ref-type="bibr" rid="ref25">
                        <sup>25</sup>
                    </xref>
                </p>
                <p>The implication of the smart contract is that the terms of the agreement, as well as the factual elements relating to its performance, can be coded into a decentralised blockchain that cannot be overridden or bypassed by any malicious or erroneous behaviour on the part of any computer on the network. Thus, if millions of computers verify that A has paid B one thousand pounds at a specific date and time, one may be certain that A has in fact paid B that amount at the stated date and time.
                    <xref ref-type="bibr" rid="ref25">
                        <sup>25</sup>
                    </xref>
                </p>
                <p>Decentralised distributed ledgers (DLT), also known as blockchains, are essentially information databases created and maintained by a network of interconnected computers without a central authority. For example, instead of a public registry system relying on paper files stored in a municipal records office, a blockchain-based system would maintain electronic databases online on every computer connected to the network. On this basis, it has become easier to construct and enforce secure contracts without recourse to the state, by means of decentralised consensus mechanisms.
                    <xref ref-type="bibr" rid="ref25">
                        <sup>25</sup>
                    </xref>
                </p>
                <p>One of the most promising fields for the deployment of blockchain technology is its use in creating fully automated contracts, which are performed without human intervention.
                    <xref ref-type="bibr" rid="ref26">
                        <sup>26</sup>
                    </xref>
                </p>
                <p>

                    <italic toggle="yes">Distributed Ledger Technology (DLT)</italic>
                </p>
                <p>Awareness of the term &#x201c;smart contract&#x201d; began to grow with the spread of knowledge about distributed ledger technology (DLT), of which blockchain is one type.
                    <xref ref-type="bibr" rid="ref21">
                        <sup>21</sup>
                    </xref> While smart contracts can, in principle, exist entirely independently of DLT, the advent of DLT has made it possible to deploy smart contracts more efficiently between parties across the globe. Unlike vending machines, a smart contract can be concluded without the parties being physically present. Instead, the parties may remotely agree on the computer program embodying the smart contract, deploy it on the desired DLT, and then allow it to execute automatically when the agreed trigger event occurs. This reduces disputes in the transfer of value between entities and opens the door to a greater degree of automation in the conclusion and completion of transactions
                    <xref ref-type="bibr" rid="ref21">
                        <sup>21</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref22">
                        <sup>22</sup>
                    </xref>
                    <sup>,2</sup>).</p>
                <p>

                    <italic toggle="yes">Decentralised Finance (DeFi):</italic>
                </p>
                <p>Decentralised finance (DeFi) refers to a series of platforms and applications developed by programmers to facilitate a wide range of banking and financial activities on the blockchain within the cryptocurrency ecosystem. It may be regarded as the financial infrastructure of the crypto-asset system. Proponents of cryptocurrencies envisage, over time, the construction of a DeFi ecosystem capable of competing with traditional banking and financial systems.
                    <xref ref-type="bibr" rid="ref14">
                        <sup>14</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref16">
                        <sup>16</sup>
                    </xref>
                </p>
                <p>The DeFi system relies heavily on cryptography, blockchain technology and smart contracts. Smart contracts can encapsulate all the functionalities offered by DeFi technologies. At present, most DeFi applications are built on the Ethereum network, owing to its powerful programming language, Solidity.</p>
                <p>

                    <bold>

                        <italic toggle="yes">Types of Smart Contracts</italic>
</bold>
                </p>
                <p>Smart contracts may take different structural forms, ranging from pure code to hybrid arrangements that combine programming and natural language. In practice, they may:
                    <list list-type="roman-lower">
                        <list-item>
                            <label>(i)</label>
                            <p>be fully encoded in computer software.</p>
                        </list-item>
                        <list-item>
                            <label>(ii)</label>
                            <p>exist as a coded contract with a separate, matching natural language version.</p>
                        </list-item>
                        <list-item>
                            <label>(iii)</label>
                            <p>consist of a natural-language contract whose performance is implemented through a separate coded or programmed layer; or</p>
                        </list-item>
                        <list-item>
                            <label>(iv)</label>
                            <p>take the form of a natural-language contract that relies on a coded payment or settlement mechanism. These variants illustrate that the &#x201c;smartness&#x201d; of the contract may lie either in the entirety of the agreement or in specific functional components, such as execution or payment.
                                <xref ref-type="bibr" rid="ref21">
                                    <sup>21</sup>
                                </xref>
                            </p>
                        </list-item>
                    </list>
                </p>
                <p>For legal purposes, it is useful to distinguish between &#x201c;strong&#x201d; and &#x201c;weak&#x201d; smart contracts. Strong smart contracts are those for which modification or cancellation after deployment entails significant technical or economic costs, such that judicial intervention to alter their operation is, in practice, difficult to justify.
                    <xref ref-type="bibr" rid="ref25">
                        <sup>25</sup>
                    </xref>
                </p>
                <p>Weak smart contracts, by contrast, can be amended or overridden with relative ease whether by the parties, the platform operator, or a court so that their legal treatment does not fundamentally depart from that of traditional contracts supported by automated tools. From an innovation perspective, this differentiation is realistic, as current technologies and social practices remain far removed from a fully &#x201c;strong&#x201d; model of smart contracting, particularly in areas such as contracts for personal services, which resist full computer control and cannot be entirely reduced to code.
                    <xref ref-type="bibr" rid="ref25">
                        <sup>25</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref27">
                        <sup>27</sup>
                    </xref>
                </p>
                <p>

                    <italic toggle="yes">Smart Contracts and the Internet of Things (IOT)</italic>
                </p>
                <p>From a technological standpoint, the meaningful deployment of smart-contract applications was hardly feasible before the widespread diffusion of networked computing, which left courts and their agents as the primary mechanisms for contract enforcement. With ongoing digitalization and the proliferation of the so-called Internet of Things (IoT), however, the practical viability of embedding contractual software in connected devices has increased significantly.
                    <xref ref-type="bibr" rid="ref25">
                        <sup>25</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref27">
                        <sup>27</sup>
                    </xref>
                </p>
                <p>For example, internet-enabled refrigerators and heating, ventilation and air-conditioning (HVAC) systems may be linked to smart contracts that automatically verify payment of amounts due to suppliers and adjust, suspend or downgrade the services provided in the event of customer default.
                    <xref ref-type="bibr" rid="ref25">
                        <sup>25</sup>
                    </xref>
                </p>
                <p>

                    <italic toggle="yes">&#x201c;Electronic Judge&#x201d; and Automated Enforcement</italic>
                </p>
                <p>The notion of &#x201c;self-enforcement&#x201d; is commonly used to describe the way blockchain-based smart contracts execute contractual obligations through automated processes. Rather than relying on subsequent human intervention, such contracts are programmed to carry out specific actions such as releasing digital assets or denying access to certain goods or services once predefined conditions are satisfied, including instances of default on loan repayments or rental obligations. This approach is premised on the view that human decision-making is susceptible to bias and inconsistency, whereas algorithmic execution is regarded as impartial and predictable, operating without discretion, hesitation, or the capacity to withhold performance.
                    <xref ref-type="bibr" rid="ref22">
                        <sup>22</sup>
                    </xref>
                </p>
                <p>Max Raskin has suggested that a judge can, in functional terms, be understood as a machine that applies a set of rules to a given constellation of facts and then instructs other actors to implement the outcome. On this view, judicial enforcement is not the only conceivable mechanism for giving effect to contractual obligations: instead of a human judge interpreting and applying contractual terms, it is theoretically possible for a computational system to perform that role. For such a system to be viable, it must possess two essential capabilities: first, the ability to generate normatively &#x201c;correct&#x201d; outputs from the factual inputs provided; and second, the ability for those outputs to be translated back into the real world through appropriate enforcement pathways.
                    <xref ref-type="bibr" rid="ref25">
                        <sup>25</sup>
                    </xref>
                </p>
                <p>The vending machine is often cited as the paradigmatic example of a self-executing contract. It is typically defined as &#x201c;a self-contained automatic machine that dispenses goods or provides services upon the insertion of coins.&#x201d; In contractual terms, the machine completes one side of the bargain automatically once acceptance occurs unilaterally through the insertion of the required sum of money. This simple model illustrates how performance may, in part, be detached from ongoing human discretion and delegated to a technical artefact.
                    <xref ref-type="bibr" rid="ref22">
                        <sup>22</sup>
                    </xref>
                </p>
                <p>

                    <italic toggle="yes">Smart Contracts and the Sale of Movables and Immovable.</italic>
                </p>
                <p>It is relatively straightforward to imagine contracts for the sale of movable property being structured as smart contracts and executed electronically. By contrast, it is less intuitive to see how contracts for the sale of immovable property (real estate) could be fully implemented in this way.
                    <xref ref-type="bibr" rid="ref32">
                        <sup>32</sup>
                    </xref>
                </p>
                <p>Nonetheless, a stylized model can be constructed on a blockchain platform. Under such a model, once the buyer and seller have concluded a sale agreement, the buyer transfers the deposit, which is held in a neutral escrow-like account controlled by a smart contract. After the buyer has transferred the full purchase price to that smart-contract escrow, the seller may finalize the transaction by triggering the contract to:
                    <list list-type="roman-lower">
                        <list-item>
                            <label>(i)</label>
                            <p>release the funds to the seller&#x2019;s account and;</p>
                        </list-item>
                        <list-item>
                            <label>(ii)</label>
                            <p>transfer the tokenized title to the property to the buyer. The transfer is then recorded on the blockchain and the ownership status updated accordingly.
                                <xref ref-type="bibr" rid="ref21">
                                    <sup>21</sup>
                                </xref>
                            </p>
                        </list-item>
                    </list>
                </p>
                <p>This scenario rests on several critical assumptions. First, the property must be tokenized, meaning that a specific blockchain token has been legally and technically linked to the underlying real estate. Although there is growing publicity around &#x201c;selling houses on the blockchain&#x201d;, significant legal and technical hurdles still need to be addressed before such models can be widely implemented. Secondly, the transaction is assumed to involve a straightforward transfer of unencumbered title between the parties, which often does not reflect the more complex reality of real-estate practice (e.g. mortgages, easements, co-ownership, registration requirements).
                    <xref ref-type="bibr" rid="ref11">
                        <sup>11</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref4">
                        <sup>4</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref8">
                        <sup>8</sup>
                    </xref>
                </p>
                <p>

                    <italic toggle="yes">Smart Contracts and Loan Agreements</italic>
                </p>
                <p>A similar thought experiment can be applied to loan agreements. A borrower could submit an electronic loan application to a bank, which would, in turn, notify the borrower of the required documentation. Once the documentation has been duly provided and verified, the lender may transfer the loan amount into an escrow account governed by a smart contract (a pre-designated address on the blockchain). The smart contract could then automatically manage disbursement and repayment in accordance with the agreed terms such as releasing funds upon satisfaction of specified conditions, scheduling repayments, and triggering default consequences thereby reducing the scope for ex post opportunism and manual intervention, while still operating within the broader legal framework that recognizes and constrains such automated arrangements.
                    <xref ref-type="bibr" rid="ref32">
                        <sup>32</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref17">
                        <sup>17</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref9">
                        <sup>9</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref33">
                        <sup>33</sup>
                    </xref>
                </p>
            </sec>
            <sec id="sec17">
                <title>The Role of Blockchain in Smart Contracts</title>
                <p>Smart contracts represent an evolutionary development of the blockchain system, which was originally created to enable the operation of digital currencies. In essence, a smart contract is a computer program that runs on a blockchain platform, through which dealings in assets can be conducted in a fully electronic manner. This includes transactions involving sale, purchase, lease, mortgage, construction, development, insurance and other forms of contractual arrangements. In all such cases, contractual relations may be implemented via smart contracts expressed in the form of computer code deployed on the blockchain.
                    <xref ref-type="bibr" rid="ref31">
                        <sup>31</sup>
                    </xref>
                </p>
                <p>

                    <bold>

                        <italic toggle="yes">Definition of Blockchain</italic>
</bold>
                </p>
                <p>Blockchain was initially introduced as the technological backbone of the cryptocurrency Bitcoin, and only later began to acquire independent significance as its various potential uses became better understood. It nevertheless remains closely associated with Bitcoin, forming the core of its technological infrastructure.
                    <xref ref-type="bibr" rid="ref26">
                        <sup>26</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref31">
                        <sup>31</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref22">
                        <sup>22</sup>
                    </xref>
                </p>
                <p>Cryptocurrencies are used primarily for two purposes: as a store of value and as a means of exchange, in other words, they perform a function analogous to money. These characteristics have lent support to the proposition that cryptocurrencies may be treated as a form of property right. Since digital currencies rely on the blockchain system, the latter has been taken as a starting point for structuring transactions involving other types of assets, whether movable or immovable.
                    <xref ref-type="bibr" rid="ref31">
                        <sup>31</sup>
                    </xref>
                </p>
                <p>Governments and corporations around the world remain deeply uncertain as to how best to employ blockchain technologies in different areas of social and economic life, although the Emirate of Dubai, for example, has taken serious steps towards their comprehensive implementation.
                    <xref ref-type="bibr" rid="ref39">
                        <sup>39</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref12">
                        <sup>12</sup>
                    </xref>
                </p>
                <p>Blockchain may be defined as a decentralized database of all verified transactions, shared across peer-to-peer (P2P) networks and operating through cryptographic algorithms. Its importance can be captured by noting that it enables the transfer of digital assets (or the digital representation of offline physical assets) in a manner that reduces or even eliminates intermediaries in economic transactions, by keeping accurate records of asset holders without the involvement of traditional intermediaries such as registries or land registration authorities. Blockchain thus ensures permanent access to reliable information.
                    <xref ref-type="bibr" rid="ref15">
                        <sup>15</sup>
                    </xref>
                </p>
                <p>In more general terms, blockchain denotes a class of digital technologies that combine cryptography, data management, networking and incentive mechanisms to support the verification, execution and recording of transactions between parties.</p>
                <p>

                    <bold>

                        <italic toggle="yes">Operational Logic: Consensus, Cryptography and Nodes</italic>
</bold>
                </p>
                <p>In systems such as Bitcoin, each block contains data representing debit and credit entries on cryptographic addresses. A simple transaction for example, &#x201c;A pays B ten units of cryptocurrency on 2 March at 4 p.m.&#x201d; (Raskin, 2016) is bundled together with other transactions into a block. This block is then proposed to the network and verified by many nodes using a consensus protocol. Once validated, it is cryptographically linked to the preceding blocks, extending the chain and updating the state of the ledger for all participants.
                    <xref ref-type="bibr" rid="ref27">
                        <sup>27</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref28">
                        <sup>28</sup>
                    </xref>
                </p>
                <p>Consensus is achieved without reliance on any central repository of information. Each node maintains a copy of the ledger and participates in validating proposed blocks against the existing history of transactions. Through this distributed verification process, the network converges on a single authoritative version of the ledger, which may record rights, obligations and ownership interests.
                    <xref ref-type="bibr" rid="ref28">
                        <sup>28</sup>
                    </xref>
                </p>
                <p>Cryptography is central to this architecture. Transactions are digitally signed, and each block contains a cryptographic hash of the previous block. When a new block is added and propagated to the network, each node verifies both the signatures and the integrity of the chain. This design makes ex post alteration of recorded data computationally prohibitive: modifying one block would require recalculating the cryptographic links for that block and all subsequent blocks on every node in the network.
                    <xref ref-type="bibr" rid="ref7">
                        <sup>7</sup>
                    </xref>
                </p>
                <p>Different governance models of blockchain can be distinguished. In public blockchains, resilience is generally high owing to the large and open set of validating nodes. In consortium and private blockchains, the number of nodes is smaller; while this may reduce resilience in a purely technical sense, it also limits external exposure and can enhance control, confidentiality and regulatory compliance. In all cases, a node denotes an individual participant in the network that takes part in verifying and propagating data; collectively, these nodes maintain what operates as a logically unified ledger shared across the platform.
                    <xref ref-type="bibr" rid="ref10">
                        <sup>10</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref13">
                        <sup>13</sup>
                    </xref>
                </p>
            </sec>
            <sec id="sec18">
                <title>Comparing the contractual formation of smart contracts and traditional contracts</title>
                <p>Contract law is one of the most dynamically evolving branches of private law, continually adapting to new business models and technologies.
                    <xref ref-type="bibr" rid="ref26">
                        <sup>26</sup>
                    </xref> In this context, the emergence of smart contracts raises the question whether parties who opt into code-based arrangements still intend to create legally binding relations, or merely to operate within an alternative, purely technical regulatory framework. Where smart contracts are used to achieve outcomes that are, in substance, identical to those governed by traditional contracts, such as the transfer of ownership in assets. it is difficult to deny their contractual character.
                    <xref ref-type="bibr" rid="ref26">
                        <sup>26</sup>
                    </xref> Under most common law systems, the classic elements of contract formation offer and acceptance, consideration or subject-matter, intention to create legal relations, and sufficient certainty of essential terms may all be identified in smart contract transactions, even if they are expressed and implemented through code rather than natural language.
                    <xref ref-type="bibr" rid="ref21">
                        <sup>21</sup>
                    </xref>
                </p>
                <p>At the same time, blockchain technology can be viewed, following Savelyev, as a &#x201c;paradigm shift&#x201d; in contracting because it enables the full automation of performance by both parties, in contrast to devices such as vending machines that only automate one side of the exchange. This qualitative transformation, however, does not mean that smart contracts can fully replicate the nuance and flexibility of written agreements drafted in natural language, especially where open-textured legal standards are concerned.
                    <xref ref-type="bibr" rid="ref26">
                        <sup>26</sup>
                    </xref> It therefore becomes essential that programmers and platform designers internalise existing legal requirements when coding smart contracts, as errors or omissions in drafting or updating the code may give rise to liability where they lead to non-compliance with prevailing contractual norms or cause harm to one of the parties.
                    <xref ref-type="bibr" rid="ref25">
                        <sup>25</sup>
                    </xref>
                </p>
                <p>

                    <bold>

                        <italic toggle="yes">Form of the contract</italic>
</bold>
                </p>
                <p>In classical civil-law doctrine, the form of the contract is generally understood to take one of three principal shapes:</p>
                <p>

                    <bold>

                        <italic toggle="yes">Written form</italic>
</bold>
                </p>
                <p>The parties agree on specific contractual terms, reduce them to writing in several paper originals, sign them, and each party retains one or more physical copies in their possession. This form used where the subject-matter of the contract is of significant financial value.</p>
                <p>

                    <bold>

                        <italic toggle="yes">Documentary electronic form</italic>
</bold>
                </p>
                <p>Here, the contract is concluded in &#x201c;screen-based&#x201d; form through a computer program or a website accessed via any electronic device (computer, mobile phone, etc.), and the party merely declares his or her identity through the interface. This form is usually resorted to where the contract does not concern a high-value economic transaction, and the parties are primarily concerned with reducing the costs of travel, legal drafting, official registration, and similar transaction costs.</p>
                <p>Neither of these two forms necessarily requires the involvement of a third party between the contracting parties.</p>
                <p>

                    <bold>

                        <italic toggle="yes">Trusted electronic form</italic>
</bold>
                </p>
                <p>This form combines the advantages of the previous two: the reliability and evidential value of the written form, and the speed, convenience, and cost reduction of electronic contracting. It relies on an electronic signature mechanism whereby the party maintains a private electronic signature key consisting of a string of letters and numbers (such as ysp5965ms7009jnd74ndljd). When the party wishes to enter an electronic contract, the identity of the sender verified by means of the previously communicated public key, and the private key used to complete the transaction. A certification authority supervises this process usually a governmental body or a private entity licensed by the state which generates the public and private keys and thereby ensures a level of reliability comparable to traditional paper-based dealings.</p>
                <p>Although this last method is highly effective in guaranteeing the authenticity and reliability of an electronic contract even in the absence of the parties&#x2019; physical co-presence, since each has transmitted proof of identity and confirmed consent beyond reasonable doubt it ultimately amounts to a formal transposition of the trustworthy written contract into an equally trustworthy electronic format.</p>
                <p>By contrast, smart contracts, while they may rely on this trusted electronic form for concluding the contract, go a significant step further by ensuring that performance is also carried out electronically. Receipt of funds, for example, may be affected automatically between the bank accounts of the parties at a specified time through a dedicated software application. This presupposes linking the electronic bank accounts of both parties to the smart contract, and feeding the program with information on whether each party has performed its obligations for instance, by connecting the software to electronic sensors capable of monitoring construction works and triggering payment instalments accordingly, or to biometric attendance systems that record workers&#x2019; daily presence, and to performance reports prepared by their supervisors, so that the program can automatically release full salaries or impose appropriate deductions based on the data supplied.</p>
                <p>

                    <bold>

                        <italic toggle="yes">Party Autonomy/Consent</italic>
</bold>
                </p>
                <p>Although the terms of a smart contract are executed automatically, the validity of the contract still presupposes the parties&#x2019; will (consent). This will be manifested at the moment an individual decides to enter a transaction based on pre-defined terms or, in the case of electronic agents, when the individual chooses to use such an agent to conclude certain agreements and agrees to be bound by its acts.
                    <xref ref-type="bibr" rid="ref25">
                        <sup>25</sup>
                    </xref>
                </p>
                <p>For a contract to be properly formed, there must be a common intention between the parties to enter legal relations. The test for determining whether this requirement is met is an objective one: whether a reasonable person would regard the agreement as legally binding. In the context of a smart contract, once the offer is accepted, execution typically begins at the same time; it is therefore unlikely that a reasonable person would not regard such an arrangement as a binding contract.</p>
                <p>Comparisons with earlier waves of technological innovation in contracting are instructive. Smart contracts may evolve in a manner analogous to &#x201c;click-wrap&#x201d; agreements, which are formed entirely online. One party posts the contractual terms on its website, thereby offering goods or services; the buyer then indicates consent to be bound by those terms through his or her conduct usually by clicking an &#x201c;I agree&#x201d; button. United States courts have generally held click-wrap agreements to be enforceable, recognising that, in this modern setting, parties are not required to discuss and negotiate every individual clause.
                    <xref ref-type="bibr" rid="ref15">
                        <sup>15</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref32">
                        <sup>32</sup>
                    </xref>
                </p>
                <p>Where part of the contract is drafted in ordinary language and another part is expressed in code, the parties may agree that specific terms be represented in the form of computer code. However, it is important that such coded expression be capable of being received as evidence of the parties&#x2019; agreement in any subsequent judicial or arbitral proceedings. If courts or tribunals were unable to recognise this record as reflecting the parties&#x2019; consent, the legal effectiveness of the arrangement would be seriously undermined although courts may, in practice, rely on expert evidence to interpret the meaning of the code.
                    <xref ref-type="bibr" rid="ref32">
                        <sup>32</sup>
                    </xref>
                </p>
                <p>The declaration of intent itself is traditionally analysed as comprising an objective and a subjective element. The subjective element consists of: (1) the will to perform an act; (2) awareness of making a declaration of intent; and (3) the will to enter a transaction. Some commentators argue that this subjective element presupposes human behaviour and legal capacity, which are not present in the smart contract&#x2019;s automated operations.
                    <xref ref-type="bibr" rid="ref32">
                        <sup>32</sup>
                    </xref>
                </p>
                <p>Under the current legal framework, however, execution software may be understood as a mere conveyor or messenger of the contracting party&#x2019;s declaration of intent transmitting or receiving such declarations on behalf of that party. In German and French law, a messenger does not need to possess legal capacity to contract, which supports the view that software can function as a technical medium for expressing a legally valid will formed by a natural or legal person.
                    <xref ref-type="bibr" rid="ref41">
                        <sup>41</sup>
                    </xref>
                </p>
                <p>To reconcile the demands of technical certainty with the requirements of legal attribution before courts and arbitral tribunals, contemporary scholarship has proposed a hybrid model of so-called Smart Contract Templates, built upon what is known as the Ricardian triple. This model combines:
                    <list list-type="roman-lower">
                        <list-item>
                            <label>(i)</label>
                            <p>a legal text in natural language (legal prose) that judges and lawyers can read and interpret in accordance with the rules of contract law.</p>
                        </list-item>
                        <list-item>
                            <label>(ii)</label>
                            <p>a set of parameters that link the legal terms to digital, machine-processable elements; and</p>
                        </list-item>
                        <list-item>
                            <label>(iii)</label>
                            <p>standardised code that performs the automatic execution of the contractual provisions on a blockchain platform.</p>
                        </list-item>
                    </list>
                </p>
                <p>This approach demonstrates that expressing party intent in the form of code is not meant to replace the contract in its legal sense, but rather to operate as an execution layer functionally tied to a written agreement that remains available as the primary reference point in case of dispute, thereby alleviating concerns about accepting code as evidence of consent and allowing expert technical testimony to assist in its interpretation without detaching it from the traditional contractual framework.
                    <xref ref-type="bibr" rid="ref16">
                        <sup>16</sup>
                    </xref>
                </p>
                <p>

                    <bold>

                        <italic toggle="yes">Certainty of the electronic signature</italic>
</bold>
                </p>
                <p>In the context of smart contracts, what is commonly referred to as the &#x201c;electronic signature&#x201d; has been adopted as a means of verifying the identity of the contracting parties. The question nevertheless remains whether a cryptographic signature by the parties&#x2019; sufficient evidence of their identity is.</p>
                <p>In many jurisdictions, electronic signatures are treated as equivalent to handwritten signatures, and their legal definition is broadly similar across different legal systems. Thus, for example, the United States Uniform Electronic Transactions Act defines an electronic signature as &#x201c;an electronic sound, symbol, or process attached to or logically associated with a record and executed or adopted by a person with the intent to sign the record.&#x201d;
                    <xref ref-type="bibr" rid="ref48">
                        <sup>48</sup>
                    </xref> Likewise, Regulation (EU) No 910/2014 (EIDAS) defines the electronic signature, the advanced electronic signature and the qualified electronic signature as data in electronic form attached to or logically associated with other electronic data and used as a method of signing, and further provides that a qualified electronic signature is to be regarded as legally equivalent to a handwritten signature.
                    <xref ref-type="bibr" rid="ref43">
                        <sup>43</sup>
                    </xref>
                </p>
                <p>

                    <bold>

                        <italic toggle="yes">
Subject-matter of the contract</italic>
</bold>
                </p>
                <p>Just as a valid subject-matter is required in a traditional contract, a smart contract also has a subject-matter, which will typically consist in the transfer of digital assets recorded on a blockchain. This may be characterised, within the framework of contract theory, as the legal effect which constitutes the object of the obligation, thereby preserving the classical distinction between contracts and gratuitous dispositions, in as much as contracts involve an exchange of obligations coupled with the possibility of judicial enforcement.
                    <xref ref-type="bibr" rid="ref6">
                        <sup>6</sup>
                    </xref>
                </p>
                <p>

                    <bold>

                        <italic toggle="yes">The conditional nature of smart contracts</italic>
</bold>
                </p>
                <p>It has already been noted that a smart contract is drafted in a programming language and that conditional statements form the core of its structure. The logic of computer programming operates through formulations such as &#x201c;if condition X is fulfilled, effect Y follows,&#x201d; which is closely aligned with the contractual conception of obligations that are subject to a condition precedent or subsequent. Raskin has argued that, in this context, the performance of the contract is nothing more than the activation of one of these pre-programmed conditional statements.
                    <xref ref-type="bibr" rid="ref25">
                        <sup>25</sup>
                    </xref> From the standpoint of contract doctrine, such arrangements may be construed either as a transaction subject to a condition where the very formation of the contract depends on a given event, or as a conditional obligation within a contract already concluded, where the performance of certain terms is contingent upon subsequent events.</p>
                <p>In this sense, contract law, smart contracts and computer programming all operate within a common conditional framework built on the logic of &#x201c;if &#x2026; then &#x2026;&#x201d;. At the same time, it must be emphasised that smart contracts do not constitute a form of artificial intelligence: they are not capable of machine learning or of autonomously reshaping their own terms but are designed to produce a specific outcome whenever the same set of pre-defined conditions is met.
                    <xref ref-type="bibr" rid="ref25">
                        <sup>25</sup>
                    </xref>
                </p>
                <p>

                    <bold>

                        <italic toggle="yes">Contract interpretation</italic>
</bold>
                </p>
                <p>Given the technical features of smart contracts, the traditional rules on contractual interpretation are not readily applicable most notably the principle of construing the contract according to the parties&#x2019; common intention, even where this diverges from the literal wording, or according to the meaning that a reasonable person would attribute to the terms. Smart contracts are conceived as self-contained arrangements that are not meant to be interpreted ex post by external bodies or jurisdictions; the code itself is intended to operate as the final arbiter of the &#x201c;transaction&#x201d; it represents.
                    <xref ref-type="bibr" rid="ref26">
                        <sup>26</sup>
                    </xref>
                </p>
                <p>However, two important qualifications must be made. First, the technical complexity of smart contracts and the need for advanced programming skills to create such arrangements mean that, in many cases, they are developed by specialized companies at the request of a client. The separation between the programmer who writes the code and the party who intends to use it in their commercial activity creates a risk of misunderstanding regarding the terms of the future agreement. This reflects a divergence between execution and intention, which is aggravated by the significant gap in abstraction between legal language and programming languages. The use of Boolean logic in the code may reduce the scope for interpretation and provide a prominent level of certainty, but it does not eliminate the problem entirely.
                    <xref ref-type="bibr" rid="ref25">
                        <sup>25</sup>
                    </xref>
                </p>
                <p>From a computational perspective, any potential ambiguity must be addressed ex ante through the design of the executable program so that no &#x201c;unknown points&#x201d; remain at the performance stage. The history of computing shows, however, that software does not always operate as its designers expect: once deployed, the code may fail or behave differently from what was intended. Even if the actual outcome of a smart contract diverges from the parties&#x2019; subjective intentions, the system still constitutes the closest mechanical approximation to their will, because the behaviour of computer code is predictable under a given set of rules, whereas ambiguity in human interpretation is not resolved automatically.
                    <xref ref-type="bibr" rid="ref32">
                        <sup>32</sup>
                    </xref>
                    <sup>,</sup>
                    <xref ref-type="bibr" rid="ref25">
                        <sup>25</sup>
                    </xref>
                </p>
                <p>The sphere of discretion exercised by the human mind lies beyond the reach of computer programs, because it involves outcomes and value judgments that were neither fully contemplated nor specified by the parties prior to the conclusion of the contract but arise only after it. Where, for example, performance is made dependent on a party&#x2019;s reasonable personal satisfaction such as the commissioning of a painting this assessment is inherently subjective. One way in which the parties may address this is by reserving, to a certain extent, discretionary power in the contractual terms from the outset, or, alternatively, by refraining from the use of a smart contract in situations where such discretion constitutes an essential element of the agreement.
                    <xref ref-type="bibr" rid="ref25">
                        <sup>25</sup>
                    </xref>
                </p>
            </sec>
            <sec id="sec19" sec-type="conclusions">
                <title>Conclusions</title>
                <p>in conclusion, smart contracts represent an evolutionary development rather than a disruption of traditional contract law. Their significance lies not in replacing legal doctrine, but in reshaping the conditions under which contractual obligations are expressed, executed, and enforced. By translating legal commitments into programmable logic, smart contracts shift a substantial part of contractual governance from ex post adjudication to ex ante design, thereby redefining the balance between legal certainty and equitable flexibility.</p>
                <p>This transformation exposes a structural tension between the rigidity of code and the adaptive nature of legal reasoning. While automated execution enhances efficiency and reduces opportunistic behavior, it simultaneously limits the capacity to accommodate unforeseen circumstances, correct errors, or protect weaker parties. As a result, the effectiveness of smart contracts ultimately depends on the extent to which legal safeguards are embedded at the design stage, rather than relied upon after performance has occurred.</p>
                <p>So, the future of smart contracting does not lie in the dominance of code over law, but in their functional integration. Legal systems are called upon to evolve, not by abandoning established principles, but by reinterpreting them considering technologically mediated transactions. This requires a shift toward hybrid contractual models, where legal text and code operate in tandem, supported by regulatory oversight and interpretative mechanisms capable of bridging the gap between technical execution and legal intent.</p>
                <p>Ultimately, the challenge is not to determine whether law or code should prevail, but to ensure that their interaction produces outcomes that remain consistent with the fundamental objectives of contract law: fairness, predictability, and the protection of legitimate expectations in an increasingly digitalized economy.</p>
            </sec>
            <sec id="sec20">
                <title>Recommendations</title>
                <p>Based on the findings, the study proposes the following more concise recommendations:</p>
                <p>

                    <bold>

                        <italic toggle="yes">For legislators and regulators</italic>
</bold>
                </p>
                <p>

                    <italic toggle="yes">Clarify the legal status of smart contracts.</italic>
                </p>
                <p>Expressly recognize smart contracts as contracts in law whenever the classic elements of offer, acceptance, consideration/cause and intention are present, treating code as a technical vehicle for expression and performance rather than a separate &#x201c;law of the code&#x201d;.</p>
                <p>

                    <italic toggle="yes">Adopt a differentiated approach to &#x201c;strong&#x201d; smart contracts.</italic>
                </p>
                <p>Provide specific rules for highly irrevocable or non-modifiable smart contracts, including minimum &#x201c;exit&#x201d; or emergency-stop mechanisms and clear allocation of risk for bugs and exploited vulnerabilities.</p>
                <p>

                    <italic toggle="yes">Protect weaker parties and consumers.</italic>
                </p>
                <p>Ensure that rules on unfair terms, consumer protection and pre-contractual information apply equally on-chain, with requirements for accessible natural-language documentation mirroring the code and explicit warnings where self-execution makes reversal difficult.</p>
                <p>

                    <italic toggle="yes">Integrate DLT into existing regulatory regimes.</italic>
                </p>
                <p>Continue to adapt frameworks for crypto-assets, VASPs and DLT market infrastructures, with attention to supervisory access to data, AML/CFT obligations and reconciling immutability with data-protection rights.</p>
                <p>

                    <bold>

                        <italic toggle="yes">For courts and arbitral tribunals</italic>
</bold>
                </p>
                <p>

                    <italic toggle="yes">Develop methods for interpreting code.</italic>
                </p>
                <p>Articulate principles for reading and construing smart contracts, including structured use of expert evidence to translate code into legal categories and rules for resolving conflicts between code behavior and proven common intention.</p>
                <p>

                    <italic toggle="yes">Refine liability rules for code defects.</italic>
                </p>
                <p>Clarify when programmers, platform operators or parties bear responsibility for losses arising from bugs, design flaws or foreseeable security weaknesses.</p>
                <p>

                    <italic toggle="yes">Recognize hybrid instruments.</italic>
                </p>
                <p>Treat legal prose plus parametrized code as one integrated contract, with the written text retaining primacy for resolving disputes while giving strong evidential weight to on-chain records.</p>
                <p>

                    <bold>

                        <italic toggle="yes">For contracting parties, lawyers and technical designers</italic>
</bold>
                </p>
                <p>

                    <italic toggle="yes">Use dual-layer documentation.</italic>
                </p>
                <p>Accompany smart contracts with a clear natural-language agreement identifying the parties, subject-matter, risk allocation and dispute-resolution mechanism, and explicitly mapping key clauses to code.</p>
                <p>

                    <italic toggle="yes">Embed dispute-resolution and safety mechanisms ex ante.</italic>
                </p>
                <p>Incorporate arbitration or other ADR clauses, together with technical tools (multi-sig, escrow, supervised oracles, pause functions) that allow suspension, correction or rollback in cases of serious defects, hacks or unforeseen events.</p>
                <p>

                    <italic toggle="yes">Conduct legal&#x2013;technical audits.</italic>
                </p>
                <p>Subject material smart-contract deployments, especially those involving pooled funds, retail users or systemic functions to join legal and security review to verify compliance, robustness and alignment between business intent and coded logic.</p>
                <p>

                    <bold>

                        <italic toggle="yes">For future research and policy debate</italic>
</bold>
                </p>
                <p>

                    <italic toggle="yes">Deepen the conceptual and systemic analysis.</italic>
                </p>
                <p>Further work should address conflict-of-laws issues in cross-border smart contracts, the legal status of DAOs, interactions with insolvency and restructuring proceedings, and the possible role of automated enforcement agents or &#x201c;electronic judges&#x201d; alongside state courts and arbitral mechanisms.</p>
                <p>Ethical considerations.</p>
                <p>This study does not involve human participants or animals. Therefore, no ethical approval or consent was required.</p>
            </sec>
        </sec>
    </body>
    <back>
        <sec id="sec23" sec-type="data-availability">
            <title>Data availability</title>
            <sec id="sec24">
                <title>Underlying data</title>
                <p>Repository name: Smart Contracts and Blockchain Technology: Legal Sources Used in the Study. 
                    <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.5281/zenodo.20489840">https://doi.org/10.5281/zenodo.20489840</ext-link>.
                    <xref ref-type="bibr" rid="ref49">
                        <sup>49</sup>
                    </xref>
                </p>
                <p>The project contains the following underlying data:
                    <list list-type="bullet">
                        <list-item>
                            <label>&#x2022;</label>
                            <p>
F1000_data_availability_reply_and_source_list.docx (a source-list file containing the publicly available legal and academic sources used in the doctrinal and comparative legal analysis, including legislation, regulations, international instruments, books, reports, journal articles, working papers, and online legal materials).</p>
                        </list-item>
                    </list>
                </p>
            </sec>
            <sec id="sec25">
                <title>Extended data</title>
                <p>No extended data is associated with this article.</p>
                <p>Data are available under the terms of the 
                    <ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/publicdomain/zero/1.0/legalcode">Creative Commons Zero &#x201c;No rights reserved&#x201d; data waiver (CC0 1.0 Public domain dedication)</ext-link>.</p>
            </sec>
            <sec id="sec26">
                <title>Reporting guidelines</title>
                <p>Not applicable. This is a doctrinal legal study and does not require reporting guidelines.</p>
            </sec>
        </sec>
        <ref-list>
            <title>References
                <break/>Books and Reports</title>
            <ref id="ref1">
                <label>1</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Arru&#x00f1;ada</surname>
                            <given-names>B</given-names>
                        </name>
</person-group>:
                    <article-title>Blockchain&#x2019;s Struggle to Deliver Impersonal Exchange.</article-title>
                    <source>

                        <italic toggle="yes">Minnesota Journal of Law, Science &amp; Technology.</italic>
</source>
                    <year>2018</year>;<volume>19</volume>:<fpage>55</fpage>.
                    <pub-id pub-id-type="doi">10.24926/15529541.3794</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref2">
                <label>2</label>
                <mixed-citation publication-type="other">
                    <collab>Bank for International Settlements</collab>:
                    <article-title>Embedded Supervision: How to Regulate Crypto Markets Using Distributed Ledger Technology.</article-title>
                    <source>

                        <italic toggle="yes">BIS Working Paper No. 811.</italic>
</source>
                    <year>2019</year>.</mixed-citation>
            </ref>
            <ref id="ref3">
                <label>3</label>
                <mixed-citation publication-type="book">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>De Filippi</surname>
                            <given-names>P</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Wright</surname>
                            <given-names>A</given-names>
                        </name>
</person-group>:
                    <source>

                        <italic toggle="yes">Blockchain and the Law: The Rule of Code.</italic>
</source>
                    <publisher-name>Harvard University Press</publisher-name>;<year>2018</year>.
                    <pub-id pub-id-type="doi">10.4159/9780674985933</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref4">
                <label>4</label>
                <mixed-citation publication-type="book">
                    <collab>European Law Institute</collab>:
                    <source>

                        <italic toggle="yes">Blockchain Technology and Smart Contracts.</italic>
</source>
                    <publisher-name>ELI</publisher-name>;<year>2022</year>.</mixed-citation>
            </ref>
            <ref id="ref5">
                <label>5</label>
                <mixed-citation publication-type="book">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Lu</surname>
                            <given-names>S</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <source>

                        <italic toggle="yes">AI Applications in Web3 Sup Tech and Reg Tech: A Regulatory Perspective.</italic>
</source>
                    <publisher-name>ADGM Academy Research Centre and Asian Institute of Digital Finance</publisher-name>;<year>2025</year>.</mixed-citation>
            </ref>
            <ref id="ref6">
                <label>6</label>
                <mixed-citation publication-type="book">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>McKendrick</surname>
                            <given-names>E</given-names>
                        </name>
</person-group>:
                    <source>

                        <italic toggle="yes">Contract Law.</italic>
</source>
                    <publisher-name>Oxford University Press</publisher-name>;
                    <edition>15th ed</edition>
                    <year>2020</year>.
                    <pub-id pub-id-type="doi">10.1093/he/9780198855293.001.0001</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref7">
                <label>7</label>
                <mixed-citation publication-type="book">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Narayanan</surname>
                            <given-names>A</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <source>

                        <italic toggle="yes">Bitcoin and Cryptocurrency Technologies.</italic>
</source>
                    <publisher-name>Princeton University Press</publisher-name>;<year>2016</year>.</mixed-citation>
            </ref>
            <ref id="ref8">
                <label>8</label>
                <mixed-citation publication-type="book">
                    <collab>OECD</collab>:
                    <source>

                        <italic toggle="yes">The Tokenization of Assets and Potential Implications for Financial Markets.</italic>
</source>
                    <publisher-name>OECD Publishing</publisher-name>;<year>2020</year>.
                    <pub-id pub-id-type="doi">10.1787/83493d34-en</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref9">
                <label>9</label>
                <mixed-citation publication-type="book">
                    <collab>OECD</collab>:
                    <source>

                        <italic toggle="yes">Blockchain Technologies as a Digital Enabler.</italic>
</source>
                    <publisher-name>OECD Publishing</publisher-name>;<year>2021</year>.</mixed-citation>
            </ref>
            <ref id="ref10">
                <label>10</label>
                <mixed-citation publication-type="book">
                    <collab>UK Government Chief Scientific Adviser</collab>:
                    <source>

                        <italic toggle="yes">Distributed Ledger Technology: Beyond Blockchain.</italic>
</source>
                    <publisher-name>Government Office for Science</publisher-name>;<year>2016</year>.</mixed-citation>
            </ref>
            <ref id="ref11">
                <label>11</label>
                <mixed-citation publication-type="book">
                    <collab>UNIDROIT</collab>:
                    <source>

                        <italic toggle="yes">Digital Assets and Private Law.</italic>
</source>
                    <publisher-name>UNIDROIT</publisher-name>;<year>2023</year>.</mixed-citation>
            </ref>
            <ref id="ref12">
                <label>12</label>
                <mixed-citation publication-type="other">
                    <collab>World Economic Forum</collab>:
                    <article-title>Blockchain Beyond the Hype: A Practical Framework for Business Leaders.</article-title>
                    <year>2018</year>. (accessed 22 December 2025).
                    <ext-link ext-link-type="uri" xlink:href="https://www.weforum.org/reports/blockchain-beyond-the-hype">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref13">
                <label>13</label>
                <mixed-citation publication-type="other">
                    <collab>World Economic Forum</collab>:
                    <article-title>The Future of Financial Infrastructure: An Ambitious Look at How Blockchain Can Reshape Financial Services.</article-title>
                    <year>2016</year>.</mixed-citation>
            </ref>
        </ref-list>
        <ref-list>
            <title>Journal Articles and Working Papers</title>
            <ref id="ref14">
                <label>14</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Buterin</surname>
                            <given-names>V</given-names>
                        </name>
</person-group>:
                    <article-title>Hard Forks, Soft Forks, and the Future of Ethereum.</article-title>
                    <year>2016</year>. (accessed 10 December 2025).
                    <ext-link ext-link-type="uri" xlink:href="https://blog.ethereum.org/2016/07/20/hard-fork-completed/">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref15">
                <label>15</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Catchlove</surname>
                            <given-names>P</given-names>
                        </name>
</person-group>:
                    <article-title>Smart Contracts: A New Era of Contract Use.</article-title>
                    <year>2017</year>. (accessed 10 December 2025).
                    <ext-link ext-link-type="uri" xlink:href="https://ssrn.com/abstract=3090226">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref16">
                <label>16</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Clack</surname>
                            <given-names>CD</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Bakshi</surname>
                            <given-names>VA</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Braine</surname>
                            <given-names>L</given-names>
                        </name>
</person-group>:
                    <article-title>Smart Contract Templates: Foundations, Design Landscape and Research Directions.</article-title>
                    <source>

                        <italic toggle="yes">arXiv 1608.00771.</italic>
</source>
                    <year>2016</year>.</mixed-citation>
            </ref>
            <ref id="ref17">
                <label>17</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Cole</surname>
                            <given-names>GM</given-names>
                        </name>
</person-group>:
                    <article-title>The Long Convergence: &#x201c;Smart Contracts&#x201d; and the &#x201c;Customization&#x201d; of Commercial Law.</article-title>
                    <source>

                        <italic toggle="yes">South. Calif. Law Rev.</italic>
</source>
                    <year>2019</year>.</mixed-citation>
            </ref>
            <ref id="ref18">
                <label>18</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Castillo</surname>
                            <given-names>M</given-names>
                            <prefix>del</prefix>
                        </name>
</person-group>:
                    <article-title>Ethereum Executes Blockchain Hard Fork to Return DAO Funds.</article-title>
                    <source>

                        <italic toggle="yes">CoinDesk.</italic>
</source>
                    <year>2016</year>.</mixed-citation>
            </ref>
            <ref id="ref19">
                <label>19</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Heidari</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Hashemi</surname>
                            <given-names>S</given-names>
                        </name>
</person-group>:
                    <article-title>&#x2018;Towards Standardized Regulations for Blockchain Smart Contracts: Insights from Delphi and SWARA Analysis&#x2019;, Amity.</article-title>
                    <source>

                        <italic toggle="yes">J. Manag.</italic>
</source>
                    <year>2023</year>;<volume>XI</volume>(<issue>II</issue>).</mixed-citation>
            </ref>
            <ref id="ref20">
                <label>20</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Kolber</surname>
                            <given-names>AJ</given-names>
                        </name>
</person-group>:
                    <article-title>Not-So-Smart Blockchain Contracts and Artificial Responsibility.</article-title>
                    <source>

                        <italic toggle="yes">Stanford Technology Law Review.</italic>
</source>
                    <year>2018</year>;<volume>21</volume>(<issue>2</issue>).</mixed-citation>
            </ref>
            <ref id="ref21">
                <label>21</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Madir</surname>
                            <given-names>J</given-names>
                        </name>
</person-group>:
                    <article-title>Smart Contracts: (How) Do They Fit under Existing Legal Frameworks?.</article-title>
                    <source>

                        <italic toggle="yes">SSRN.</italic>
</source>
                    <year>2018</year>;<volume>3301463</volume>.
                    <pub-id pub-id-type="doi">10.2139/ssrn.3301463</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref22">
                <label>22</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Mik</surname>
                            <given-names>E</given-names>
                        </name>
</person-group>:
                    <article-title>Smart Contracts: Terminology, Technical Limitations and Real-World Complexity.</article-title>
                    <source>

                        <italic toggle="yes">Law Innov. Technol.</italic>
</source>
                    <year>2019</year>;<volume>9</volume>:<fpage>269</fpage>.</mixed-citation>
            </ref>
            <ref id="ref23">
                <label>23</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Miller</surname>
                            <given-names>S</given-names>
                        </name>
</person-group>:
                    <article-title>Computer Security as the Future of Law&#x2019;.</article-title>
                    <source>

                        <italic toggle="yes">Presentation.</italic>
</source>
                    <year>1997</year>.
                    <ext-link ext-link-type="uri" xlink:href="http://www.caplet.com/security/futurelaw/">Reference Source</ext-link>
                    <ext-link ext-link-type="uri" xlink:href="http://www.lexology.com/library/detail.aspx?g=8128f5c4-5923-4981-9129-f0fe84ec57af">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref24">
                <label>24</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Nakamoto</surname>
                            <given-names>S</given-names>
                        </name>
</person-group>:
                    <article-title>Bitcoin: A Peer-to-Peer Electronic Cash System.</article-title>
                    <year>2008</year>. (accessed 25 December 2025).
                    <ext-link ext-link-type="uri" xlink:href="https://bitcoin.org/bitcoin.pdf">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref25">
                <label>25</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Raskin</surname>
                            <given-names>M</given-names>
                        </name>
</person-group>:
                    <article-title>The Law of Smart Contracts.</article-title>
                    <source>

                        <italic toggle="yes">Georgetown Law Technology Review.</italic>
</source>
                    <year>2016</year>. (accessed 26 December 2025).
                    <ext-link ext-link-type="uri" xlink:href="https://ssrn.com/abstract=2842258">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref26">
                <label>26</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Savelyev</surname>
                            <given-names>I</given-names>
                        </name>
</person-group>:
                    <article-title>Contract Law 2.0: &#x201c;Smart&#x201d; Contracts as the Beginning of the End of Classic Contract Law.</article-title>
                    <year>2017</year>. (accessed 28 December 2025).
                    <ext-link ext-link-type="uri" xlink:href="https://www.lexology.com/library/detail.aspx?g=8128f5c4-5923-4981-9129-f0fe84ec57af">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref27">
                <label>27</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Sklaroff</surname>
                            <given-names>JM</given-names>
                        </name>
</person-group>:
                    <article-title>Smart Contracts and the Cost of Inflexibility.</article-title>
                    <source>

                        <italic toggle="yes">Univ. Pa. Law Rev.</italic>
</source>
                    <year>2017</year>;<volume>166</volume>:<fpage>263</fpage>.</mixed-citation>
            </ref>
            <ref id="ref28">
                <label>28</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Staples</surname>
                            <given-names>M</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Risks and Opportunities for Systems Using Blockchain and Smart Contracts.</article-title>
                    <year>2017</year>. (accessed 22 December 2025).
                    <ext-link ext-link-type="uri" xlink:href="https://d1wqtxts1xzle7.cloudfront.net/102517822/Blockchains_20and_20Smart_20Contracts-libre.pdf">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref29">
                <label>29</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Szabo</surname>
                            <given-names>N</given-names>
                        </name>
</person-group>:
                    <article-title>Smart Contracts.</article-title>
                    <year>1994</year>. (accessed 12 December 2025).
                    <ext-link ext-link-type="uri" xlink:href="http://szabo.best.vwh.net/smart.contracts.html">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref30">
                <label>30</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Szabo</surname>
                            <given-names>N</given-names>
                        </name>
</person-group>:
                    <article-title>Formalizing and Securing Relationships on Public Networks.</article-title>
                    <source>

                        <italic toggle="yes">First Monday.</italic>
</source>
                    <year>1997</year>;<volume>2</volume>(<issue>9</issue>). (accessed 26 December 2025).
                    <ext-link ext-link-type="uri" xlink:href="http://ojphi.org/ojs/index.php/fm/article/view/548/469">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref31">
                <label>31</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Szczerbowski</surname>
                            <given-names>JJ</given-names>
                        </name>
</person-group>:
                    <chapter-title>Place of Smart Contracts in Civil Law: A Few Comments on Form and Interpretation.</chapter-title>
                    <source>

                        <italic toggle="yes">Proceedings of the 12th Annual International Scientific Conference.</italic>
</source>
                    <year>2017</year>.</mixed-citation>
            </ref>
            <ref id="ref32">
                <label>32</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Werbach</surname>
                            <given-names>K</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Cornell</surname>
                            <given-names>N</given-names>
                        </name>
</person-group>:
                    <article-title>Contracts Ex Machina.</article-title>
                    <source>

                        <italic toggle="yes">Duke Law J.</italic>
</source>
                    <year>2017</year>;<volume>67</volume>:<fpage>313</fpage>.</mixed-citation>
            </ref>
            <ref id="ref33">
                <label>33</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Zetzsche</surname>
                            <given-names>DA</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Arner</surname>
                            <given-names>DW</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Buckley</surname>
                            <given-names>RP</given-names>
                        </name>
</person-group>:
                    <article-title>Decentralized Finance.</article-title>
                    <source>

                        <italic toggle="yes">Journal of Financial Regulation.</italic>
</source>
                    <year>2020</year>;<volume>6</volume>:<fpage>172</fpage>.</mixed-citation>
            </ref>
        </ref-list>
        <ref-list>
            <title>Legislation and Regulatory Instruments</title>
            <ref id="ref34">
                <label>34</label>
                <mixed-citation publication-type="other">
                    <article-title>Abu Dhabi Global Market, Financial Services and Markets Regulations 2015 (FSMR).</article-title>
                </mixed-citation>
            </ref>
            <ref id="ref35">
                <label>35</label>
                <mixed-citation publication-type="other">
                    <article-title>Arizona Revised Statutes Annotated &#x00a7; 44&#x2013;7061(E)(2).</article-title>
                    <year>2017</year>.</mixed-citation>
            </ref>
            <ref id="ref36">
                <label>36</label>
                <mixed-citation publication-type="other">
                    <article-title>Decree of the President of the Republic of Belarus No. 8 (21 December 2017).</article-title>
                </mixed-citation>
            </ref>
            <ref id="ref37">
                <label>37</label>
                <mixed-citation publication-type="other">
                    <article-title>Dubai Law No. 4 of 2022 Regulating Virtual Assets in the Emirate of Dubai.</article-title>
                </mixed-citation>
            </ref>
            <ref id="ref38">
                <label>38</label>
                <mixed-citation publication-type="other">
                    <article-title>Dubai Virtual Assets Regulatory Authority (2023), Virtual Assets and Related Activities Regulations (7 February 2023).</article-title>
                </mixed-citation>
            </ref>
            <ref id="ref39">
                <label>39</label>
                <mixed-citation publication-type="other">
                    <article-title>Government of Dubai, Dubai Blockchain Policy (United Arab Emirates).</article-title>
                </mixed-citation>
            </ref>
            <ref id="ref40">
                <label>40</label>
                <mixed-citation publication-type="other">
                    <article-title>Directive (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons regarding the processing of personal data and on the free movement of such data (General Data Protection Regulation), OJ L 119, 4 May 2016.</article-title>
                </mixed-citation>
            </ref>
            <ref id="ref41">
                <label>41</label>
                <mixed-citation publication-type="other">
                    <article-title>European Parliament (2017), Resolution of 16 February 2017 on Civil Law Rules on Robotics (2015/2103(INL)).</article-title>
                </mixed-citation>
            </ref>
            <ref id="ref42">
                <label>42</label>
                <mixed-citation publication-type="other">
                    <article-title>Financial Services Regulatory Authority (FSRA), Guidance &#x2013; Regulation of Virtual Asset Activities in ADGM (most recent version).</article-title>
                </mixed-citation>
            </ref>
            <ref id="ref43">
                <label>43</label>
                <mixed-citation publication-type="other">
                    <article-title>Regulation (EU) No. 910/2014 of the European Parliament and of the Council (23 July 2014).</article-title>
                </mixed-citation>
            </ref>
            <ref id="ref44">
                <label>44</label>
                <mixed-citation publication-type="other">
                    <article-title>Regulation (EU) 2022/858 of the European Parliament and of the Council (30 May 2022).</article-title>
                </mixed-citation>
            </ref>
            <ref id="ref45">
                <label>45</label>
                <mixed-citation publication-type="other">
                    <article-title>Regulation (EU) 2023/1114 of the European Parliament and of the Council (31 May 2023).</article-title>
                </mixed-citation>
            </ref>
            <ref id="ref46">
                <label>46</label>
                <mixed-citation publication-type="book">
                    <collab>UNCITRAL</collab>:
                    <source>

                        <italic toggle="yes">Model Law on Electronic Commerce with Guide to Enactment.</italic>
</source>
                    <publisher-name>United Nations</publisher-name>;<year>1996</year>.</mixed-citation>
            </ref>
            <ref id="ref47">
                <label>47</label>
                <mixed-citation publication-type="book">
                    <collab>UNCITRAL</collab>:
                    <source>

                        <italic toggle="yes">Model Law on Automated Contracting (MLAC) with Guide to Enactment.</italic>
</source>
                    <publisher-name>United Nations</publisher-name>;<year>2024</year>.</mixed-citation>
            </ref>
            <ref id="ref48">
                <label>48</label>
                <mixed-citation publication-type="other">
                    <article-title>Uniform Electronic Transactions Act 1999 s 2(8).</article-title>
                </mixed-citation>
            </ref>
        </ref-list>
        <ref-list>
            <title>Data repository</title>
            <ref id="ref49">
                <label>49</label>
                <mixed-citation publication-type="other">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Mahmoud</surname>
                            <given-names>D</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Hammad</surname>
                            <given-names>H</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Sulaiman</surname>
                            <given-names>SA</given-names>
                        </name>
</person-group>:
                    <article-title>Smart Contracts and Blockchain Technology: Legal Sources Used in the Study.</article-title>
                    <source>

                        <italic toggle="yes">Zenodo.</italic>
</source>
                    <year>2026</year>.
                    <pub-id pub-id-type="doi">10.5281/zenodo.20489840</pub-id>
                </mixed-citation>
            </ref>
        </ref-list>
    </back>
</article>
