Civil Law And Smart Contracts And Blockchain Based Agreements In Uae .
1. Introduction
Smart Contract Hybrid Legal Code Interaction is an emerging area of UAE civil law dealing with the relationship between computer-executable contractual code and conventional legal agreements.
A hybrid smart contract combines two different forms of contractual expression:
Traditional legal code: Written contractual provisions expressed in natural language, such as English or Arabic.
Digital executable code: Computer instructions, blockchain protocols or automated software that execute contractual obligations when specified conditions are satisfied.
The two forms operate together to create, administer and perform contractual relationships.
For example, a UAE construction company may enter into a traditional construction agreement containing payment, delivery, quality and dispute-resolution clauses. The parties may also use a blockchain-based smart contract to release payments automatically when an authorised project engineer confirms completion of specified milestones.
The conventional agreement establishes the legal obligations, while the smart contract automates their performance.
This creates important civil-law questions:
Is executable code legally binding?
What happens when computer code contradicts the written agreement?
Can an automatically executed transaction be reversed?
Who bears responsibility for programming errors?
Can courts recognise blockchain records as evidence?
Can parties obtain compensation for automated contractual failures?
How should contractual interpretation operate when human language and machine code produce different results?
The UAE is particularly relevant to this subject because it has developed legislation concerning electronic transactions, digital signatures, data protection, blockchain applications and smart-government systems.
Central principle: A smart contract is not outside civil law merely because its obligations are performed through computer code. Its legal effect depends on the applicable legislation, the parties' intention, contractual validity and the circumstances of execution.
2. Legal framework governing smart contract hybrid arrangements in the UAE
The principal legal framework consists of the following legislation.
A. Federal Decree-Law No. 25 of 2025 – New Civil Transactions Law
The new Civil Transactions Law came into force on 1 June 2026, replacing Federal Law No. 5 of 1985.
It provides the general civil-law framework for:
Formation of contracts.
Contractual consent.
Interpretation of contractual provisions.
Performance of obligations.
Good faith.
Breach of contract.
Compensation.
Invalidity and rescission.
Restitution.
Liability arising from unlawful conduct.
These principles apply to smart-contract arrangements where the relevant legal relationship falls within the scope of the Law.
A computer program does not independently establish that all legal requirements for a valid contract have been satisfied.
For instance, an automated payment instruction may execute successfully even though the underlying agreement was entered into through fraud or without valid authority.
In that situation, the parties may still have civil remedies.
B. Federal Decree-Law No. 46 of 2021 on Electronic Transactions and Trust Services
This legislation provides the principal statutory foundation for electronic transactions and electronic signatures.
Its importance includes:
Recognition of electronic documents.
Recognition of electronic signatures.
Rules concerning electronic records.
Legal recognition of electronic communications.
Requirements relating to electronic authentication.
Evidentiary treatment of electronic records.
Rules concerning electronic contracting.
A contract does not become legally ineffective merely because it is concluded electronically rather than on paper.
This is particularly important for blockchain-based agreements and digitally executed contractual arrangements.
C. Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data
Smart contracts may process personal information relating to customers, suppliers, employees and financial counterparties.
Relevant issues include:
Lawful processing.
Transparency.
Data security.
Data-subject rights.
Cross-border transfers.
Responsibility of controllers and processors.
A smart contract that permanently records personal information on an immutable blockchain may create difficulties when personal-data correction, deletion or restriction rights become applicable.
D. Federal Decree-Law No. 32 of 2021 on Commercial Companies
This legislation becomes relevant when smart contracts are used for:
Shareholder agreements.
Corporate voting.
Automated dividend distribution.
Capital contributions.
Corporate governance.
Digital management of company obligations.
The legal validity of automated corporate operations must be considered alongside mandatory company-law requirements.
E. Federal Decree-Law No. 6 of 2018 on Arbitration, as amended
Smart-contract arrangements frequently include arbitration clauses.
However, the arbitration clause must satisfy the applicable legal requirements, including requirements relating to written form, authority and consent.
Automated execution does not automatically make a dispute-resolution clause valid or binding.
3. Legal recognition of smart contracts and automated transactions
A. Article 10 – Electronic contracting
Article 10 of Federal Decree-Law No. 46 of 2021 establishes that:
Offer and acceptance may be expressed electronically.
A contract cannot be denied validity merely because it is contained in electronic documents.
Electronic form does not, by itself, deprive a contract of evidential value or enforceability.
This means that parties can potentially conclude binding contracts through digital interfaces and computer systems.
B. Article 11 – Automated electronic transactions
Particularly important provision
Article 11 expressly recognises contracts formed between automated electronic systems programmed in advance for that purpose.
Its importance for smart contracts is considerable.
For example:
A UAE online trading platform may automatically accept an order when a customer satisfies predetermined conditions.
The system may:
Identify the customer.
Verify the order.
Calculate the price.
Confirm acceptance.
Generate a transaction record.
Initiate payment.
The fact that no human personally performs every step does not automatically invalidate the contract.
Article 11 also addresses the legal consequences of errors in automated electronic transactions and the conditions under which a natural person may be able to withdraw an erroneous electronic transaction.
Legal interpretation: Article 11 provides a strong foundation for automated contracting, although it does not automatically validate every blockchain-based smart contract or every programmed contractual term.
u.ae+1
4. Structure of a hybrid smart contract
A hybrid smart contract consists of several interconnected elements.
1. Traditional legal agreement
Rights, duties, payment terms, warranties, governing law and dispute resolution
2. Executable smart-contract code
Programmed conditions, automated payment and performance instructions
3. Oracle and external data
Delivery confirmation, exchange rates, project milestones and other external information
4. Blockchain or execution platform
Transaction recording, execution and verification
5. Judicial and legal enforcement
Interpretation, remedies, restitution, damages and dispute resolution
The hybrid arrangement is not simply a combination of two documents. It is an interaction between legal rules and technological instructions.
The legal agreement determines the rights and obligations, while the executable code carries out particular operational tasks.
5. Different models of hybrid legal-code interaction
A. Natural-language agreement with executable code
The parties sign a conventional agreement and incorporate computer code to automate certain obligations.
Example: A supplier agrees to deliver goods to a UAE retailer. The smart contract releases payment after an authorised delivery confirmation.
B. Code incorporated by reference
The written agreement expressly incorporates a specified version of the smart-contract code.
The parties agree that the code will perform certain contractual operations.
The agreement should identify:
The relevant code version.
The blockchain network.
The execution conditions.
The identity of authorised users.
The treatment of programming errors.
The legal consequences of failed execution.
C. Code-only agreements
The parties interact with an executable program without a separate natural-language agreement.
Such arrangements raise more difficult questions about consent, accessibility, understanding, authority and contractual certainty.
The Electronic Transactions Law supports electronic contracting, but the parties must still satisfy the applicable rules of contract formation.
D. Hybrid agreements with human intervention
Some smart contracts require human approval before execution.
For example, a construction payment system may require an engineer's confirmation before automatically releasing payment to a contractor.
This model reduces the risk of automatic execution based on inaccurate external data.
6. Interaction between written contractual terms and executable code
One of the most significant legal problems arises when the written agreement and the computer program produce different results.
Consider the following hypothetical situation.
A UAE company enters into a written supply agreement providing that payment must be made within 30 days of delivery.
However, the smart contract is programmed to release payment immediately after the delivery data is received.
A technical error causes the system to release payment before the agreed contractual deadline.
The following questions arise:
Was the automated payment authorised?
Did the code accurately implement the written agreement?
Does the payment constitute valid contractual performance?
Can the payer seek restitution?
Is the software developer responsible?
Does the supplier have a legitimate right to retain the payment?
Which document prevails?
There is no universal UAE statutory rule that every written contract automatically overrides every smart contract.
The answer depends on the parties' agreement, incorporation of the code, interpretation rules, applicable mandatory legislation and evidence of consent.
A carefully drafted hybrid agreement should contain an express precedence clause.
For example:
Illustrative contractual precedence clause
"In the event of any inconsistency between this written agreement and the executable smart-contract code, the provisions of this written agreement shall prevail, except to the extent that the parties expressly agree otherwise in a separately authenticated written amendment."
Copy clause
This is a drafting recommendation, not a mandatory statutory clause.
7. Six important case-law authorities and their relevance
Important case-law qualification
There is an important limitation in this subject: as of November 2026, the available legal research does not establish six reported UAE judgments directly deciding the enforceability of smart contracts themselves.
The following authorities therefore distinguish direct digital-transaction decisions from analogous electronic-contract, authentication and digital-asset decisions. They should not be misrepresented as six judgments on blockchain smart contracts.
Case 1. Gate Mena DMCC v Tabarak Investment Capital Ltd
[2023] DIFC CA 002 – Judgment dated 13 June 2024
Subject: Cryptocurrency transactions and contractual obligations.
Facts:
The dispute arose from a proposed Bitcoin transaction involving approximately 300 BTC.
The parties disagreed about the contractual arrangements governing the custody and transfer of the cryptocurrency, including the conditions for releasing the Bitcoin and receiving the purchase money.
Decision:
The DIFC Court of Appeal allowed the appeal in part and ordered a retrial on a particular issue.
The Court considered:
Contract formation.
Authority of representatives.
Conditions precedent.
Custody of digital assets.
Contractual duties.
The relationship between digital transactions and conventional contractual obligations.
Principle: A cryptocurrency transaction remains subject to ordinary legal analysis of agreement, authority, obligations and breach.
Relevance: A smart contract may execute a Bitcoin transfer, but the underlying legal agreement determines whether the transfer was contractually authorised.
DIFC Courts
Case 2. Gate Mena DMCC v Tabarak Investment Capital Ltd
[2024] DIFC DEC 002 – Judgment dated 17 June 2026
Subject: Digital-asset transactions and automated contractual performance.
Facts:
This was the retrial following the Court of Appeal's decision in the earlier Gate Mena litigation.
The dispute concerned the proposed transfer and custody of Bitcoin and the conditions under which digital assets were to be released.
Decision:
The Digital Economy Court dismissed the claim after considering whether a binding agreement had been formed and what obligations the parties had undertaken.
The Court applied ordinary principles of offer, acceptance, intention to create legal relations and contractual performance.
Principle: Digital execution does not eliminate the need to prove the formation and terms of a binding contract.
Relevance: A smart contract's successful execution is not conclusive proof that all the legal conditions for an authorised contractual transfer were satisfied.
DIFC Courts
Note: These first two decisions concern different stages of the same litigation, not two unrelated disputes.
Case 3. Dubai Court of Cassation – Real Estate Appeal No. 40 of 2025
Judgment dated 24 March 2025
Subject: Electronic signatures and electronic property transactions.
Facts:
The dispute involved a property sale agreement electronically signed through the Dubai Land Department's system.
A party challenged the electronic agreement.
Decision and principle:
The Court applied Articles 54–58 of Federal Decree-Law No. 35 of 2022 on Evidence.
It recognised the evidentiary force of electronic records and signatures, including qualifying electronic documents generated through official systems.
A bare allegation of forgery was insufficient to displace properly authenticated electronic evidence.
Relevance: This authority is important for smart-contract property transactions because blockchain records, electronic signatures and transaction histories may be relied upon to establish contractual activity and authentication.
However, electronic evidentiary recognition does not automatically establish the validity of every underlying property transfer.
Polaris Legal Library+1
Case 4. ICICI Bank Ltd v Bavaguthu Raghuram Shetty
[2022] DIFC CFI 034 – Judgment dated 17 February 2025
Subject: Electronic signatures, authority and enforceability of guarantees.
Facts:
ICICI Bank sought enforcement of personal guarantees associated with financing arrangements.
The dispute involved electronic or copied signatures and whether the defendant had signed or authorised their use.
Decision:
The DIFC Court examined the authenticity of the signatures and the surrounding documentary evidence.
It distinguished between:
A genuine signature.
An electronic or copied signature authorised by the person.
A signature that had not been authorised.
The Court upheld the bank's claims under three guarantees while dismissing its claim under the Modular Personal Guarantee.
Principle: Electronic execution does not remove the need to establish genuine consent and authority.
Relevance: A smart contract may identify a wallet or execute an instruction, but this does not necessarily establish that the legally relevant person authorised the transaction.
DIFC Courts+1
Case 5. Naho v Neukirchi
[2024] DIFC SCT 415 – Proceedings decided in 2025
Subject: Electronic communications and judicial review.
This case involved proceedings before the DIFC Small Claims Tribunal and a subsequent application for permission to appeal.
It illustrates the importance of the procedural and evidentiary treatment of electronic contractual communications.
Principle and relevance: Electronic communications and records may be important in establishing what the parties agreed and how their legal relationship developed.
For smart contracts, this is relevant where a party claims that a digital instruction represented an agreed contractual variation or that a transaction was authorised.
It is an electronic-contracting analogy, not a direct ruling on blockchain code.
DIFC Courts
Case 6. Ras Al Khaimah Court of Cassation – Commercial Appeal No. 46/15 JY
Judgment dated 24 January 2021
Subject: Computer-generated commercial records and electronic invoices.
Facts and issue:
The case concerned the evidentiary use of computer-generated commercial statements and invoices in a dispute between traders.
Decision and principle:
The Court considered the admissibility and evidentiary significance of commercial records maintained through modern technological systems.
The judgment is relevant to the recognition of electronically maintained business records in commercial relationships.
Relevance: Smart-contract litigation frequently requires evidence of transaction histories, payment records, automated invoices and performance events.
Electronic records can be significant evidence, although their weight depends on the applicable evidentiary requirements and reliability of the system.
Case 7. Ras Al Khaimah Court of Cassation – Commercial Appeal No. 65/14 JY
Judgment dated 9 February 2020
Subject: Service through modern technological means.
The Court considered the validity of service through modern communication technology.
The relevant principles included verification of:
The recipient's identity.
Ownership or control of the communication channel.
The reliability of the communication method.
Proper documentation of the service.
Relevance: Smart-contract systems also depend on the authentication of participants and the reliability of digital communication channels.
A digital message or system instruction should not automatically be treated as proof of legally authorised consent without examining its authenticity and attribution.
This is a procedural technology analogy rather than a direct smart-contract ruling.
Polaris Legal Library
8. DIFC and ADGM approaches to coded contracts
The UAE has different legal frameworks for mainland courts and financial free zones.
A. DIFC approach: Coded Contracts
The Dubai International Financial Centre has introduced the concept of a Coded Contract under its Contract Law.
A coded contract is an agreement consisting entirely of coded terms and executed by a computer program, without a natural-language version.
This is a significant development because it expressly addresses the possibility of contractual arrangements existing entirely in executable code.
However, recognition as a coded contract does not remove the need to establish:
Mutual consent.
Contractual capacity.
Sufficiently certain terms.
Intention to create legal relations.
Compliance with applicable mandatory law.
B. ADGM approach
The Abu Dhabi Global Market has its own Electronic Transactions Regulations 2021.
These regulations recognise electronic records and electronic contracts.
Although the ADGM framework supports electronically concluded arrangements, it does not provide the same express coded-contract concept identified in the DIFC framework.
C. Mainland UAE approach
Mainland UAE law relies principally on:
Federal Decree-Law No. 25 of 2025.
Federal Decree-Law No. 46 of 2021.
Federal Decree-Law No. 35 of 2022 on Evidence.
Relevant commercial, consumer and sector-specific legislation.
The mainland framework recognises electronic and automated contracting, but there is no specific comprehensive federal smart-contract code that determines every issue of blockchain-based contractual enforceability.
Chambers and Partners+2
9. Liability arising from smart-contract programming errors
Programming errors are a major source of civil disputes.
Consider a situation in which a smart contract automatically transfers AED 500,000 instead of AED 50,000 because of a coding error.
Potentially responsible parties may include:
A. Software developer
A developer may face contractual or civil liability where the developer has breached an applicable duty, failed to meet agreed specifications or acted negligently.
Relevant questions include:
Was the code developed according to contractual specifications?
Was appropriate testing performed?
Was the error reasonably foreseeable?
Was the developer responsible for maintaining the system?
Did the error cause the loss?
B. Contracting parties
The parties themselves may bear responsibility where they approved incorrect code, supplied inaccurate instructions or failed to comply with their contractual responsibilities.
C. Oracle service provider
An oracle supplies external information to a blockchain.
For example, a smart contract may depend on:
Foreign exchange rates.
Weather information.
Delivery confirmations.
Insurance data.
Commodity prices.
If an oracle supplies inaccurate information and causes an incorrect payment, liability depends on the oracle provider's contractual obligations, representations and applicable civil-liability rules.
D. Platform operator
A platform operator may be responsible where its contractual or regulatory obligations have been breached.
However, operating the blockchain does not automatically make the platform operator liable for every transaction executed on it.
10. Invalidation and reversal of smart-contract transactions
A particularly difficult issue concerns transactions that have already been executed.
Blockchain technology may make a transaction technically irreversible. Nevertheless, technical irreversibility does not necessarily mean legal irreversibility.
A court may examine whether the transaction resulted from:
Fraud.
Mistake.
Lack of legal capacity.
Lack of authority.
Invalid contractual consent.
Breach of mandatory law.
Unauthorised execution.
Unjustified retention of transferred property or funds.
Available legal remedies
| Remedy | Purpose |
|---|---|
| Declaration of invalidity | Establish that the transaction lacks legal validity |
| Rescission | Set aside a transaction where statutory requirements are met |
| Restitution | Restore property or money transferred |
| Compensation | Recover proven financial loss |
| Injunction | Prevent threatened or continuing unlawful conduct |
| Specific performance | Require performance of a legally binding obligation |
| Non-enforceability | Prevent reliance on a transaction against a protected claimant |
A court may order the parties to restore assets or compensate the injured party even if the original blockchain transaction cannot technically be deleted.
11. Civil liability in automated performance systems
Smart contracts can create new forms of contractual disputes.
A. Automatic payment without delivery
A smart contract releases payment despite the supplier not delivering goods.
The buyer may claim contractual remedies, depending on the agreement and applicable law.
B. Incorrect execution of insurance claims
A smart contract automatically rejects an insurance claim because its data conditions are incorrectly programmed.
The insurer cannot necessarily avoid its contractual obligations merely by relying on the automated rejection.
C. Incorrect construction milestone certification
A smart contract releases payment following incorrect project data.
The dispute may involve the contractor, engineer, employer and technology provider.
D. Automated termination
A smart contract automatically terminates a service agreement because a payment was recorded as late, even though payment was made within the agreed period.
The parties may dispute whether termination was contractually justified.
E. Digital asset transfer
A smart contract transfers a token or cryptocurrency to the wrong wallet.
The legal analysis may involve authorisation, ownership, custody, mistake and restitution.
12. Consumer protection and smart contracts
Smart contracts are increasingly relevant to online retail, financial services and digital marketplaces.
A consumer may accept an online agreement without understanding that certain contractual provisions are executed automatically.
UAE consumer-protection principles remain relevant.
Businesses should ensure:
Clear disclosure of contractual terms.
Transparency about automatic deductions.
Proper consent mechanisms.
Accessible cancellation procedures where legally required.
Protection against misleading contractual representations.
Appropriate handling of erroneous payments.
Compliance with mandatory consumer rights.
A business cannot automatically avoid consumer-protection obligations by arguing that its computer program executed the disputed transaction.
13. Data protection and blockchain-based contracts
Hybrid smart contracts often require personal information to identify participants and execute transactions.
This creates a potential conflict between blockchain immutability and data-protection obligations.
For example, an employment smart contract may permanently record:
Employee identification information.
Salary details.
Attendance records.
Performance information.
Payment histories.
However, personal-data protection legislation may require correction, deletion or restriction of personal information in appropriate circumstances.
Possible technical solutions include:
Keeping personal information off-chain.
Storing only cryptographic references on-chain.
Using permissioned blockchain systems.
Limiting access to authorised participants.
Establishing procedures for correcting inaccurate data.
Designing privacy controls into the system.
The legal framework must be assessed separately for mainland UAE, DIFC and ADGM data-protection regimes.
14. Jurisdiction and dispute resolution
Hybrid smart-contract disputes can involve parties located in different countries and computer systems distributed across multiple jurisdictions.
Questions may arise concerning:
The governing law.
The place of contractual performance.
The court having jurisdiction.
The location of digital assets.
Arbitration agreements.
Enforcement of judgments.
Recognition of foreign awards.
A smart contract should ideally contain a conventional governing-law clause and dispute-resolution clause.
For example:
A UAE company and a Singapore supplier may use a blockchain-based payment system. If the code executes incorrectly, the parties should not have to rely on uncertain assumptions about the location of the blockchain network to determine the governing law.
The legal agreement should clearly identify the applicable law and dispute-resolution forum, subject to mandatory jurisdictional rules.
15. Practical example: Hybrid smart contract in a UAE construction project
Consider a construction project in Dubai involving an employer, contractor, engineer and blockchain service provider.
The parties execute a conventional construction agreement and incorporate an automated payment system.
Illustrative transaction
Contract value
AED 10M
AUTOMATED MILESTONE PAYMENT STRUCTURE
Foundation completion
AED 2M
Structural completion
AED 3M
Mechanical installation
AED 2M
Final completion
AED 3M
How execution works
Engineer certifies completion of a milestone.
Authorised data enters the smart-contract system.
The program verifies the payment conditions.
The payment is automatically released.
The blockchain records the transaction.
Legal dispute scenario
Suppose the engineer mistakenly certifies structural completion.
The system releases AED 3 million even though the structural work is incomplete.
The employer may pursue:
A contractual claim against the contractor.
A claim concerning negligent certification, where the relevant duty exists.
A contractual claim against the software provider, if the system failed to meet its agreed specifications.
Restitution or damages, depending on the legal basis and circumstances.
The blockchain record establishes what happened technically. It does not independently establish that the contractor was legally entitled to receive the payment.
16. Major legal challenges and reforms required in the UAE
| Legal challenge | Potential reform |
|---|---|
| Conflict between code and written agreements | Standardised precedence clauses |
| Programming errors | Mandatory testing and audit requirements for critical applications |
| Oracle inaccuracies | Clear allocation of oracle responsibility |
| Unauthorised execution | Strong authentication and authority verification |
| Irreversible transactions | Emergency suspension and legally compliant recovery mechanisms |
| Cross-border disputes | Clear governing-law and jurisdiction clauses |
| Privacy conflicts | Privacy-preserving blockchain architecture |
| Consumer vulnerability | Accessible disclosure and dispute procedures |
| Unclear developer liability | Contractual allocation of technical responsibilities |
| Evidence disputes | Reliable audit trails and electronic-record preservation |
17. Critical legal analysis
The interaction between smart contracts and conventional legal agreements represents an important development in UAE civil law.
The central challenge is that computer code operates through predetermined instructions, whereas civil law evaluates intention, consent, fairness, good faith, responsibility and legally recognised rights.
These systems are not always perfectly aligned.
For example, a smart contract may automatically execute a payment because a predetermined data condition has been satisfied. However, the law may require consideration of whether the condition was genuinely fulfilled, whether the person supplying the data had authority and whether the payment was legally due.
Three principles should guide judicial interpretation.
First: Technological execution is not equivalent to legal validity.
A transaction can be technically successful but legally defective.
Second: Digital evidence must be distinguished from contractual consent.
A blockchain record may demonstrate that a wallet executed a transaction, but additional evidence may be needed to establish who authorised it and why.
Third: Civil liability must remain technologically neutral.
A party should not escape its legal obligations merely because it performs them through automated software.
The UAE's recognition of automated electronic transactions under Article 11 of the Electronic Transactions Law, combined with the DIFC's coded-contract framework, provides a foundation for the continued development of hybrid contractual systems.
18. Conclusion
Smart Contract Hybrid Legal Code Interaction is an emerging area of UAE civil law in which conventional contractual principles interact with executable digital instructions.
The legal framework is based on the Civil Transactions Law, the Electronic Transactions and Trust Services Law, the Evidence Law and applicable special legislation.
The case-law authorities discussed above demonstrate that UAE courts and the DIFC judiciary recognise the importance of digital transactions, electronic signatures, authentication, contractual intention and digital-asset obligations.
The most important conclusions are:
Automated electronic contracts can have legal validity under Article 11 of Federal Decree-Law No. 46 of 2021.
Electronic contracting is not invalid merely because it occurs digitally.
Smart-contract execution does not automatically prove valid contractual consent.
Written contractual provisions and executable code must be interpreted together.
Programming errors may create contractual or civil liability.
Technically irreversible transactions may still generate legal remedies.
Electronic and blockchain records can play an important evidentiary role.
DIFC coded-contract recognition must be distinguished from the mainland UAE framework.
Data protection and consumer rights continue to apply.
Human judicial authority remains important for determining legal rights and remedies.
Ultimately, UAE civil law does not require a choice between conventional contracts and smart contracts. Its developing framework permits technological execution while retaining the legal principles necessary to protect consent, contractual certainty, fairness and civil responsibility.
Research qualification: The seven authorities above include one set of two decisions from the same Gate Mena litigation and several electronic-transaction analogies. They should be used as supporting judicial authorities, not cited as seven direct precedents establishing smart-contract enforceability. The distinction is especially important in academic legal writing.

comments