Code as Law or Law as Code? Smart Contracts and Enforceability in Indian Courts
The digital asset revolution has transitioned from a niche subculture to a major commercial reality. At the heart of this disruption sits the “smart contract”—a piece of self-executing code deployed on decentralised, immutable ledgers that automatically triggers obligations when pre-defined parameters are met. Proponents of Web3 often rely on the maxim “code is law,” suggesting that these cryptographic systems bypass the friction, delays, and bias of traditional legal machinery.
However, when a multi-million-rupee protocol fails, a coding glitch triggers an unintended liquidation, or a party alleges fraud, the romanticism of algorithmic autonomy collides with institutional reality. The question then shifts from the digital realm to the marble corridors of justice: Are smart contracts legally enforceable in Indian courts? Navigating the intersection of the Indian Contract Act 1872, the Information Technology Act 2000, and the modern digital landscape reveals a complex reality where code must ultimately bow to codification.
The Anatomy of a Smart Contract: A Legal Translation
To evaluate enforceability, we must first demystify the technology. A smart contract is not an explicit “agreement” in the traditional semantic sense; rather, it is an automated instruction set architecture written in languages like Solidity or Rust.
[Traditional Contract] ──> Natural Language, Ambiguity, Human Discretion
│
▼ Translated into
│
[Smart Contract] ──> Cryptographic Code, Deterministic “If-Then” Logic, On-Chain Execution
In commercial practice, smart contracts generally fall into two categories:
-
The Ancillary Code Model (Hybrid Contracts): A traditional natural-language contract exists off-chain, and specific operational performance parameters (such as escrow release or cross-border payment processing) are outsourced to an on-chain automated script.
-
The Pure Code Model: The entire interaction, agreement, and performance reside solely within the code, completely detached from natural language or external paper trails.
For Indian courts to recognise either model, the digital arrangement must map cleanly onto statutory pillars established in the nineteenth century.
Fitting the Square Cryptographic Peg into the Round Statutory Hole
The foundational regime for checking contract validity in India is the Indian Contract Act 1872 (ICA). Section 10 of the ICA mandates that all agreements are contracts if they are made by the free consent of parties competent to contract, for a lawful consideration, and with a lawful object, and are not expressly declared to be void.[1]
1. Offer and Acceptance in Deterministic Logic
Under Section 2 of the ICA, an agreement is born when a proposal is accepted.[2] In a pure code smart contract, the deployment of code onto a public blockchain (like Ethereum) can be construed as an “invitation to treat” or a standing offer.
When a user interacts with the smart contract address by signing a transaction with their private key, they formally communicate their acceptance. The Supreme Court of India implicitly validated automated electronic interactions in Trimex International FZE v Vedanta Aluminium Ltd, ruling that contracts concluded via electronic communications carry the same legal weight as traditional written agreements.[3]
2. The Cryptographic Dilemma of “Free Consent”
Consent requires consensus ad idem—parties must agree on the same thing in the same sense.[4] This creates an evidentiary hurdle for smart contracts. If a non-technical business owner interacts with a smart contract, can it be argued they consented to thousands of lines of complex programming code they could not read?
If a compiler error or an unforeseen logic exploit results in an unintended transfer of assets, a court may find that true consent was vitiated by a mutual mistake of fact under Section 20 of the ICA, rendering the agreement void.[5]
3. Lawful Consideration and Virtual Digital Assets (VDAs)
Contracts require a reciprocal exchange of value (consideration).[6] In the decentralised ecosystem, this consideration is almost exclusively paid in native cryptocurrencies or tokens.
While the Reserve Bank of India has frequently expressed structural concerns regarding digital currencies, the Supreme Court’s landmark ruling in Internet and Mobile Association of India v Reserve Bank of India set aside the central bank’s sweeping banking ban on crypto assets.[7] Furthermore, the structural taxation framework introduced via Finance Acts confirms that while tokens are heavily regulated and taxed, they are not illegal. Therefore, the exchange of digital tokens constitutes valid consideration under Section 25 of the ICA.
The E-Contract Shield: The Information Technology Act 2000
While the ICA provides the theoretical skeleton, the Information Technology Act 2000 (IT Act) provides the legislative muscle that allows digital agreements to hold up in court.
Section 10A of the IT Act explicitly states that where contract formation, proposals, and acceptances are expressed in electronic form, such a contract shall not be deemed unenforceable solely on the ground that electronic means were used.[8] This provides a strong statutory shield for the ancillary code model.
However, a critical compliance issue emerges when validating autonomous blockchain actions against the statutory requirements for electronic signatures:
Because asymmetric cryptographic keys used in decentralised networks bypass centralized Certifying Authorities, a pure smart contract lacks a statutorily recognized digital signature. Consequently, a litigant cannot automatically rely on the mandatory legal presumptions of authenticity provided under Section 85B of the Indian Evidence Act 1872 (now read alongside the Bharatiya Sakshya Adhiniyam 2023).[10]
Procedural Hurdles and Evidentiary Pitfalls in Indian Litigation
Proving a smart contract breach in an Indian courtroom involves navigating significant procedural hurdles. Under Section 63 of the Bharatiya Sakshya Adhiniyam 2023 (BSA)—which recently replaced Section 65B of the legacy Indian Evidence Act—any electronic record produced in court must be accompanied by a specific certificate confirming the integrity and proper operation of the device that produced it.[11]
The Decentralisation Paradox: How does a litigant provide a compliance certificate for an electronic record generated by a globally distributed, decentralised network of validator nodes?
No single entity owns or maintains a public blockchain network. Without specialized expert testimonies under Section 45 of the Indian Evidence Act/BSA, a court may struggle to admit raw block-explorer data as reliable evidence.[12]
Furthermore, the core philosophy of smart contracts is immutability. Traditional contract law balances strict enforcement with equitable doctrines like force majeure, frustration (Section 56 of the ICA), and the judicial power to rectify or rescind unfair agreements.[13] If a smart contract continues to execute mechanically during a disruptive global event, its rigid architecture runs counter to the flexible principles of equity deeply embedded in Indian jurisprudence.
Jurisdiction and the Ghost of Anonymity
The internet has no borders, and public blockchains are inherently international. In Modi Entertainment Network v W.S.G. Cricket Pte Ltd, the Supreme Court established clear rules for contractual jurisdiction and the validity of choice-of-law clauses.[14] However, applying these rules requires identifying the parties involved.
Because public ledger transactions rely on pseudonymous hexadecimal wallet addresses, identifying the true counterparty is incredibly difficult. If an anonymous entity drains an liquidity pool through a flash loan transaction, the aggrieved Indian party face an uphill battle. They must establish:
-
Territorial jurisdiction under Section 20 of the Code of Civil Procedure 1908.[15]
-
The physical location of the defendant or where the cause of action arose.
-
A clear strategy for enforcing a court decree against an anonymous cryptographic wallet.
The Path Forward: Hybrid Legal Frameworks
Smart contracts will not replace traditional Indian contract law anytime soon. Instead, corporate and legal strategies are shifting toward Hybrid Smart Legal Contracts.
┌────────────────────────────────────────────────────────┐
│ Traditional Legal Agreement │
│ – Formulated in natural, clear language │
│ – Defines jurisdiction, force majeure, and intent │
└───────────────────────────┬────────────────────────────┘
│
▼ Incorporates by Reference
│
┌────────────────────────────────────────────────────────┐
│ On-Chain Smart Contract │
│ – Executes deterministic actions (e.g., payments) │
│ – Acts as a programmatic tool of the master contract │
└────────────────────────────────────────────────────────┘
By ensuring that an overarching natural-language agreement references the deployed smart contract address, businesses can leverage programmatic execution without discarding their constitutional and statutory protections.
Conclusion
Smart contracts offer unprecedented operational efficiency, but they do not operate in a legal vacuum. Indian courts possess a remarkably resilient statutory framework in the Indian Contract Act 1872, capable of expanding to absorb modern technical innovations. However, until specific amendments explicitly reconcile decentralized cryptographic signatures with the IT Act, the legal enforceability of pure, code-only smart contracts remains an uncertain frontier.
For innovators, legal advisors, and enterprise creators, the message is clear: Code cannot safely be treated as law unless it is carefully structured to comply with the law.
Table of Authorities
Statutory Legisations
-
Bharatiya Sakshya Adhiniyam 2023.
-
Code of Civil Procedure 1908.
-
Indian Contract Act 1872.
-
Information Technology Act 2000.
Judicial Decisions
-
Internet and Mobile Association of India v Reserve Bank of India (2020) 10 SCC 1.
-
Modi Entertainment Network v W.S.G. Cricket Pte Ltd (2003) 4 SCC 341.
-
Trimex International FZE v Vedanta Aluminium Ltd (2010) 3 SCC 1.
Footnotes
[1] Indian Contract Act 1872, s 10.
[2] ibid, s 2(h).
[3] Trimex International FZE v Vedanta Aluminium Ltd (2010) 3 SCC 1.
[4] Indian Contract Act 1872, s 13.
[5] ibid, s 20.
[6] ibid, s 2(d).
[7] Internet and Mobile Association of India v Reserve Bank of India (2020) 10 SCC 1.
[8] Information Technology Act 2000, s 10A.
[9] ibid, s 3.
[10] Indian Evidence Act 1872, s 85B.
[11] Bharatiya Sakshya Adhiniyam 2023, s 63.
[12] Indian Evidence Act 1872, s 45.
[13] Indian Contract Act 1872, s 56.
[14] Modi Entertainment Network v W.S.G. Cricket Pte Ltd (2003) 4 SCC 341.
[15] Code of Civil Procedure 1908, s 20.
