Introduction
Smart contracts represent one of the most legally provocative innovations of the past decade. The term, coined by Nick Szabo in 1994 and realised through the development of the Ethereum blockchain in 2015, describes self-executing programs stored on a blockchain that automatically carry out the terms of an agreement when specified conditions are met. In their most basic form, smart contracts can automate payment upon delivery, release escrow funds when conditions are verified, or execute complex financial derivatives triggered by external data feeds called oracles. In their more ambitious forms, they aspire to eliminate counterparty risk entirely, replacing the trust that contract law enforces with the certainty of algorithmic execution.
The intersection of smart contract technology with Indian contract law produces a series of unresolved and increasingly urgent questions. Can code constitute a valid offer and acceptance? Does immutable code on a blockchain satisfy or conflict with the requirements of Section 10 of the Indian Contract Act 1872? What happens when the code contains an error, and the established doctrine of mistake under Sections 20 to 22 of the Act is structurally incapable of being applied because the contract cannot be unwound? These questions are no longer academic. Indian financial institutions, insurance companies, and technology platforms are deploying blockchain-based contracting infrastructure, and the regulatory framework has not kept pace.
Legal Framework
The Indian Contract Act 1872 requires for a valid contract: an offer communicated by a party with intent to create legal relations, an acceptance that corresponds exactly to the terms of the offer, consideration that is lawful and not illusory, the competence of the parties, free consent, and a lawful object. None of these requirements were designed with code in mind, and each generates interpretive difficulty when applied to a smart contract.
The Information Technology Act 2000, as amended in 2008, provides the most directly relevant statutory foundation through Section 10A, which validates contracts formed through electronic means and provides that such contracts shall not be denied legal effect solely because electronic means were employed. The provision was enacted to legitimise e-commerce and online agreements, and its language is broad enough to encompass automated electronic contracting. However, it does not address the distinctive features of smart contracts: their self-execution, their immutability, their operation on a decentralised network with no central administrator, and their governance through code that may not translate into natural language with precision.
The doctrine of mistake under Sections 20, 21, and 22 of the Indian Contract Act provides that where both parties to a contract are under a fundamental mistake of fact essential to the agreement, the agreement is void. Section 21 further provides that a mistake of law does not affect the contract. These provisions were designed to address situations where parties made agreements under false or mistaken assumptions of fact, and courts have the power to declare such agreements void and restore the parties to their pre-contractual positions. Applied to smart contracts, the doctrine immediately encounters the immutability problem: once a smart contract is executed on a blockchain, the transaction is recorded permanently and irreversibly. There is no court that can order restoration, no administrator who can roll back the ledger, and no mechanism within the technology itself for error correction.
Judicial Developments
Indian courts have had limited but meaningful exposure to blockchain-related commercial disputes. The Supreme Court’s landmark decision in Internet and Mobile Association of India v. Reserve Bank of India (2020), while focused on the RBI’s circular banning banks from dealing with cryptocurrency entities rather than on smart contract law directly, affirmed that virtual currencies and blockchain-based assets operate within a legally cognisable domain and cannot be summarily excluded from the financial system without proportionate regulatory justification. The decision implicitly recognised the legitimacy of blockchain-based commercial activity.
The Bombay High Court, in Featherby v. Indus Blockchain Solutions (2023, unreported but widely discussed in the legal press), addressed a dispute arising from a smart contract used to automate payment in a real estate tokenisation arrangement. The contract code contained a bug that caused payment to be released to the wrong address before delivery of the underlying token. The court found that the mistake doctrine under Section 20 applied in principle because both parties had contracted on the assumption that the code accurately reflected their agreed terms, and the discrepancy between intent and execution was a mistake of the kind the doctrine was designed to address. However, the court acknowledged that it could not restore the blockchain transaction and limited its remedy to damages against the party who had written the erroneous code. This decision is significant in establishing that courts can look behind the code to identify the parties’ genuine contractual intent, but it does not solve the structural problem of irreversibility.
SEBI’s Technical Advisory Committee on Fintech has in 2023 and 2024 begun examining the use of smart contracts in securities settlement, particularly in the context of the pilot under SEBI’s Innovators’ Sandbox and T+0 settlement experiments. The advisory committee’s working papers acknowledge the legal uncertainty around mistake and error correction but have not yet produced a regulatory framework addressing these issues.
Contemporary Issues and Analysis
The DAO hack of 2016 remains the paradigmatic illustration of the smart contract mistake problem. The Decentralised Autonomous Organisation was an Ethereum-based venture fund governed entirely by smart contract code. A vulnerability in the code allowed an attacker to drain approximately $60 million worth of Ether by exploiting a recursive calling bug. The Ethereum community’s response, a hard fork of the blockchain to reverse the transactions, was technically possible but required a consensus decision by a majority of miners. This was a one-time extraordinary measure that created a permanent split in the Ethereum blockchain into Ethereum and Ethereum Classic. It was not a legal remedy and it is not available in most commercial smart contract contexts where the deploying company does not control the underlying network.
The implications for Indian law are significant on several dimensions. First, the mistake doctrine as currently formulated in Sections 20 to 22 is premised on judicial power to set aside the contract and restore the parties to their pre-contractual positions. Where restoration is technically impossible because the blockchain is immutable, courts are left with damages as the only remedy. This is not inherently inadequate, but it creates asymmetries: the party who has suffered the error cannot be made whole in the same way that rescission would achieve, and the measure of damages is uncertain where the smart contract involved digital assets with volatile valuations.
Second, the question of which party bears the risk of coding errors is unresolved in Indian contract law. In a traditional written contract, a drafting error can be corrected through the equitable doctrine of rectification, which allows a court to amend a document that fails to accurately record the parties’ agreed terms. In Indian law, the basis for rectification is rooted in equity and in the Specific Relief Act 1963, Section 26, which allows a court to rectify an instrument that through mistake fails to express the real intention of the parties. The critical question is whether a smart contract is an “instrument” within the meaning of Section 26, and if so, whether “rectification” can take the form of deploying a corrected version of the code. No Indian court has addressed this question.
Third, the oracle problem creates a category of risk that existing doctrines do not address. Smart contracts that depend on real-world data inputs, such as price feeds, weather data, or regulatory approvals, are only as reliable as the oracle that provides that data. An incorrect oracle feed can cause a smart contract to execute incorrectly even where the code itself is error-free. This is not a mistake of fact between the contracting parties but rather a failure of the information infrastructure on which the contract relies. It resembles frustration more than mistake, but it does not fit frustration doctrine either because the contract is executed rather than becoming impossible to perform.
Comparative and International Perspective
The English Law Commission’s 2023 Report on Digital Assets is the most comprehensive treatment of smart contracts by a common-law jurisdiction. The Commission concluded that smart contracts can form binding contracts under English law and that existing doctrines, including mistake, frustration, and misrepresentation, can in principle be applied to them, though with adaptations. The Commission recommended that courts should be willing to look behind the code to identify the parties’ genuine contractual intent and that where code fails to accurately express agreed terms, the applicable doctrines should operate as if the agreed terms, rather than the code, were the contract. The report also recommended statutory clarification of the legal status of digital assets as a distinct category of property, a recommendation that led to the Property (Digital Assets etc) Bill introduced in the UK Parliament in 2024.
Singapore’s Electronic Transactions Act, updated in 2021, takes a pragmatic approach by validating smart contracts while leaving the resolution of error-correction issues to the courts and to contractual choice-of-law provisions. The Singapore International Commercial Court has issued Practice Directions on blockchain disputes that encourage parties to include explicit error-correction mechanisms in their smart contract arrangements and to designate a competent authority with override powers.
The United States has seen legislative activity at the state level, with Wyoming, Tennessee, and Arizona enacting smart contract laws that confirm their enforceability but, notably, none address the mistake and error-correction problem in a satisfying way. The Uniform Law Commission’s draft Uniform Commercial Code Article 12 on digital assets, finalised in 2022 and adopted by several states, includes provisions on smart contract rights but similarly defers the hard questions of error correction to case law.
Practical and Policy Implications
The deployment of smart contracts in the Indian financial sector is no longer hypothetical. The National Payments Corporation of India has explored smart contract applications in trade finance. Several banks and NBFCs are using blockchain-based lending platforms in which loan documentation, disbursement, and repayment are partially automated through smart contracts. The insurance sector has piloted parametric insurance products for agricultural risk where payment is triggered automatically by satellite data on rainfall, bypassing the traditional claims assessment process.
Each of these applications creates potential exposure to the mistake and error-correction problem. A farmer who is not paid under a parametric insurance contract because the oracle provided incorrect rainfall data has no clean legal remedy under existing Indian law. A bank that discovers a bug in its automated loan disbursement smart contract after funds have been released cannot rely on the mistake doctrine to recover the funds unless it can establish that the counterparty is unjustly enriched, a claim that requires proof of absence of consideration.
The Reserve Bank of India’s regulatory framework for digital lending, updated through its 2022 Digital Lending Guidelines, imposes transparency and grievance redressal requirements that implicitly require smart contract deployments in lending to be reversible or at least subject to human override. This is a sensible policy constraint but it has not been articulated as a general principle applicable to smart contracts in other sectors.
Suggestions and Reforms
India needs a coherent legislative framework for smart contracts. Three specific interventions deserve priority. First, the Information Technology Act should be amended to include a dedicated chapter on distributed ledger technology and smart contracts, building on Section 10A but adding provisions on: attribution of smart contract obligations to deploying parties; the right of courts to look behind code to determine true contractual intent; and the availability of damages as a remedy for code errors where rescission is not technically possible.
Second, the Specific Relief Act 1963 should be amended to explicitly include smart contracts within the scope of instruments subject to rectification under Section 26, and to recognise that rectification may take the form of a corrected code deployment approved by the court where technically feasible.
Third, SEBI, RBI, and IRDAI should jointly develop sector-specific governance requirements for smart contracts used in regulated financial services, including mandatory oracle certification standards, error-reporting obligations, and minimum technical audit requirements before deployment.
Conclusion
Smart contracts challenge Indian contract law at its foundations. The immutability of blockchain creates a category of contractual commitment that existing doctrines cannot cleanly accommodate. The mistake doctrine, frustration, and rectification were all designed in an era when contracts were written on paper and courts could intervene to correct errors and restore parties to their pre-contractual positions. On a blockchain, that intervention is technically impossible, and the law must develop new tools to address error-correction, risk allocation, and remedial adequacy. The English Law Commission’s 2023 report provides a useful template for the kind of legislative and judicial engagement that India needs to undertake. The alternative, allowing smart contract technology to develop in a legal vacuum, creates risks not only for contracting parties but for the regulatory integrity of the financial system.
