CRI explained: this guide covers what it means, who it applies to, the step-by-step process, documents required, fees, due dates and penalties in India — so you can stay compliant with confidence and avoid costly mistakes.
Quantum computing and blockchain are the last two technologies dealt with in paragraph 5 of the CRI Guidelines 2025. Each gets a short statement of how the Office sees the technology, the rule that an abstract idea is not patentable but a real-world application may be, and illustrative examples with the disclosure the specification must contain.
A theoretical concept such as quantum mechanics principles or the idea of a blockchain is not patentable as an abstract idea; a real-world, tangible application with a concrete technical effect or improvement in a technological process may be (paras 5.3 and 5.4). Quantum applications need hardware-level disclosure (Examples 17 and 18). Blockchain applications need cryptographic techniques, data structures, consensus mechanisms and hardware or network interactions described (para 5.4.1; Examples 19 and 20). The Guidelines are the Patent Office's guidance and do not have the force of law; the Patents Act, 1970 and the Patents Rules, 2003 as now in force prevail.
The Office revises its guidelines, so check the current version on ipindia.gov.in. For the general sufficiency rules see paragraph 4.4. A blockchain or quantum applicant who needs the specification checked can use our objection reply service or have the draft reviewed before filing.
Quantum computing (paragraph 5.3)
The Guidelines describe quantum computing as using superposition, entanglement and quantum tunnelling to process information, with fields of application including quantum sensing, quantum key distribution, quantum simulation and the quantum internet. They list the layers and components that a quantum computer may include: qubit technologies, quantum gates, chips and processors, cooling and shielding equipment, signal amplifiers, compiler engines, decoders, simulators and error-correcting codes. They also note that the main challenge is the physical hardware, which is often highly specialised or experimental.
The legal statement follows. An abstract idea, such as a formula or a theoretical concept like a quantum mechanics principle, is not patentable because it lacks practical application. When a quantum innovation turns the principle into a real-world application, such as a method for optimising logistics using quantum algorithms or a specific hardware configuration for qubit control, it may become patentable. The key, the Guidelines say, is to show a concrete technical effect or improvement in a technological process.
Quantum examples (paragraph 5.3.1)
| Example | The Guidelines' invention | Disclosure the Office lists | Aspect that may take it outside section 3(k) |
|---|---|---|---|
| 17 | A hybrid quantum-classical system with a superconducting qubit processor, a classical control unit using machine learning for feedback and error mitigation, a compiler to pulse sequences, cooling and shielding and a synchronisation module | Qubit materials, dimensions and design; the architecture of the machine learning control unit with parameters, data types and feedback protocols; a flow diagram of compiler-to-pulse translation with timing and error margins; the cryogenic and shielding specifications; block diagrams of the integration | Adaptive gate-level adjustment during execution that improves fidelity and performance |
| 18 | A chip-based photonic quantum device with reconfigurable optical circuits, single-photon sources, tuning elements and detectors | Chip layout with waveguide geometry, materials and fabrication; control logic for single- and two-qubit gates; test data on loss, extinction ratios and phase tuning; a sample protocol execution with timing diagrams and expected output distributions | A reconfigurable platform giving high-speed, low-noise operation with better gate fidelity and scalability |
The pattern is that a quantum claim is disclosed at the level of the physical device: materials, geometry, environment, control logic and measured data.
Blockchain (paragraph 5.4)
The Guidelines describe blockchain as a peer-to-peer, distributed, append-only ledger updated by consensus among nodes. They mention non-repudiation, digital signatures, encryption, smart contracts and distributed ledger technology as components, and name banking, cyber security, supply chain management, healthcare and governance as fields of application.
The same legal statement follows: a theoretical concept such as blockchain is not patentable as an abstract idea, but a real-world application with a concrete technical effect or improvement in a technological process may be.
What a blockchain specification must contain (paragraph 5.4.1)
The Guidelines require comprehensive descriptions of:
- the cryptographic techniques used;
- the specific data structures;
- the consensus mechanisms employed;
- any interactions with hardware or network systems.
They add that elements such as the distributed ledger, smart contracts, consensus mechanisms, cryptographic processes and network configurations must be clearly defined, and that clear descriptions of consensus mechanisms and data layouts such as block structures and linkages are crucial for enablement. They name proof of work, proof of stake and practical Byzantine fault tolerance among the mechanisms that may be involved.
One point favours applicants. For smart contracts, the Guidelines say only high-level functionality need be disclosed, with sensitive implementation details kept back, if the technical effect does not lie in the smart contract.
Blockchain examples (paragraph 5.4.2)
| Example | The Guidelines' invention | Disclosure the Office lists | Aspect that may take it outside section 3(k) |
|---|---|---|---|
| 19 | A method of running a rental agreement over a blockchain, where a smart contract verifies a cryptocurrency payment, issues an access token and an access control module activates a physical or virtual asset | Smart contract logic and its triggering parameters; the protocol stack linking contracts to IoT hardware; the events recorded immutably; fallback mechanisms for failures, expired contracts or disputes | Automated enforcement of access and payment rights without a central server, with reduced fraud and latency and integration of physical devices |
| 20 | A supply chain provenance system on a private blockchain with a hybrid consensus mechanism, several smart contracts, oracle inputs and off-chain storage anchored on chain by hash trees | Node configuration, network permissions and consensus parameters; the function of each smart contract; the off-chain storage and on-chain anchoring; the hybrid consensus including validator selection and fault tolerance; oracle integration and sensor protocols | Low-latency finality and real-time tracking, with reduced on-chain storage demand and secure real-time environmental monitoring |
Both blockchain examples involve a physical interface, either an access control module or sensors, which is part of the technical effect the Guidelines identify.
What the examiner checks
| Question | What the applicant should show |
|---|---|
| Is this an abstract concept? | A defined application with a technical effect, not just the principle |
| Is the hardware or network structure disclosed? | Components, configuration and measured behaviour |
| Are the cryptographic and consensus elements specified? | Named techniques, parameters and data layout |
| Is the technical effect stated? | Latency, fidelity, storage, security or similar, tied to claim features |
| Does the claim match the disclosure? | Each claimed element supported in the description |
How an objection is usually framed, and how to answer it
| Objection | Answer |
|---|---|
| "Insufficient disclosure of consensus mechanism or data structure" | Point to the description of validators, block layout and parameters; add nothing that is not in the original specification |
| "The invention is an abstract business use of blockchain" | Show the technical effect on the network or hardware and apply the substance tests in paragraph 4.5.2 |
| "Quantum claim lacks hardware detail" | Cite the device description, materials and test data |
A worked example (invented)
Pragati Ledger claims a method for recording crop procurement on a blockchain. The examiner objects that the claim is an abstract recording scheme. Pragati's specification describes a permissioned network with a named consensus procedure, a block structure with a batch hash, and weighbridge sensors that submit readings through a stated protocol, which reduces manual reconciliation delay. Pragati amends the claim to include the consensus step and the sensor interface and answers by tying the delay reduction to those features. Following Example 20, the answer rests on the structure and the physical interface, not on the commercial purpose.
Common lapses
- Describing a blockchain as "a secure ledger" without the consensus or data layout.
- Putting the technical effect in the description only.
- Over-disclosing smart contract code when the effect lies elsewhere; the Guidelines allow high-level disclosure in that case.
- Describing quantum hardware by function only, with no materials or measured data.
Need help with a blockchain or quantum filing?
These specifications are heavy on technical detail and the disclosure has to match the claims. Our team can review a draft for the points listed in paragraphs 5.3 and 5.4 and help with replies to objections. See patent objection reply, and read next on how the Office handles AI and machine learning scenarios.
Key takeaways
- Abstract quantum or blockchain concepts are not patentable; tangible applications with a technical effect may be.
- Quantum claims need device-level disclosure.
- Blockchain claims need cryptography, data structures, consensus mechanisms and hardware or network interaction.
- Smart contract code may be disclosed at high level if the effect lies elsewhere.
- The four examples all end in a technical effect.
Read next
- CRI Guidelines 2025, paragraph 4.4: sufficiency of disclosure
- CRI Guidelines 2025, paragraphs 5.1 to 5.2.2: AI, ML and DL inventions
- CRI Guidelines 2025, paragraph 5.2.3: illustrative scenarios
- Software Patents in India: Can Software Be Patented
Disclaimer: Based on the manuals and guidelines published by the Office of the Controller General of Patents, Designs and Trade Marks that are named in the article, as consulted on 4 October 2026. They are guidance and do not have the force of law; the Patents Act, 1970 and the Patents Rules, 2003 as amended (including the 2024 amendment rules) prevail, and the current versions on ipindia.gov.in should be checked. This article is general information, not legal advice; check the official text before acting.