Ethereum and Indian institutional finance
India has already decided to tokenise. What will it run on?
The answer decides who can build here.
SEBI has required a distributed ledger inside corporate-bond infrastructure since 2022. In September 2026 the RBI and SEBI put the first tokenised corporate bonds on a live rail. The direction is not in question.
The rail underneath is still open. The options are a public chain like Ethereum, a closed ledger shared between institutions, or a closed ledger run by one of them. On a public chain, confidentiality has to be added in a layer above. India's first tokenised bonds went on a closed ledger owned by its stock depositories, with the cash settled in central-bank money.
What follows is what is live, what Indian law permits, and where public Ethereum actually fits.
Why "whether" is already settled
It arrived by regulation, not adoption.
SEBI's Security and Covenant Monitoring System (tracks corporate bonds and non-convertible securities) has recorded charges and covenants for corporate bonds on a distributed ledger since 1 April 2022. It is operated by the two depositories, NSDL and CDSL. No corporate bond ISIN activates without it.
The most durable piece of blockchain infrastructure in Indian finance did not come from a startup and does not involve a token. A regulator required it, and the depositories run it.
4,291 issuersT4 have been onboarded as a result of the mandate.
The line India actually draws
The ledger is mandated. The asset is taxed at 30%.
On 10 September 2026 the RBI Governor and the SEBI Chairman launched a tokenised corporate-bond rail together: ₹1,025 croreT1 raised across three issuers, settled atomically in wholesale CBDC. At the same event, crypto and stablecoins were kept off the programme entirely.
Gains on crypto are taxed at 30% plus a 4% cessT1, losses cannot be offset against gains or carried forward, and 1%T1 is withheld at source on every transfer. A trader who ends the year down still owes tax on the trades that went up. Holding crypto is legal; running a book in it is not really viable.
What is actually at stake
The biggest prizes sit where the law is silent.
The largest opportunities in India are inside the domestic perimeter where the law is silent, while the permitted pilots are offshore, small, or aimed at the leg that was never slow.
India's corporate bond market has ₹53.6 lakh croreT1 outstanding and trades about ₹7,645 croreT1 on an average day. Less than four percent of it changes hands in a month. On an exchange a trade settles the next day. Away from the exchange it can take three to seven, most of that spent on paperwork.
The pattern repeats across the economy. India receives $135 billionT1 a year in remittances, more than any other country. Small businesses face a ₹25 lakh croreT3 credit gap, and only 14%T3 of them hold formal credit at all.
Set that against what has actually been built. The September pilot tokenised the primary issuance of a bond, the part that already completed in a day. The illiquid secondary market, where the friction actually sits, was left alone.
Module C — the full sizing of where the value is, segment by segment
What the case has to survive
Confidentiality ruled out every public chain.
On a public chain, positions and transfers are visible to anyone who looks; a whitelist controls who can enter, not who can see. That is the stated reason JPMorgan, Goldman Sachs, DTCC and HSBC built on permissioned Canton, and the reason India's own tokenised bonds settled on a ledger owned by the depositories. The requirement disqualifies any ledger whose contents are public by default, Ethereum included, so a proposal that puts confidential bank activity on one is answering a question nobody asked.
Privacy is the fastest-moving part of the Ethereum stack, and none of it has yet reached the layer where the rejection happened. The Ethereum Foundation's roadmap leaves the base layer alone: L1 stays a public ledger by design, and confidentiality is built above it at the wallet, application and layer-2 layers. So the overlay is what an institution actually has to judge. The Enterprise Ethereum Alliance's own April 2026 survey rates one of sevenT1 enterprise privacy stacks generally available, with fiveT1 still at pilot.
The one regulated production deployment sits in fund distribution rather than bank settlement. Since February 2026, tokenised money-market funds from four managersT4/T3 — Aberdeen, BlackRock, Fidelity International and State Street — have been available through Archax with a privacy wrapper on a TEE-based Ethereum layer-2. That is a layer which had already chosen public chains. No bank-run core-settlement venue has moved. SWIFT built its shared ledger on Linea, Ethereum layer-2 technology, put 17 banksT1 on it, and kept it permissioned.
The remaining objections concede better than they argue. Every consortium blockchain of the last decade failed, which is true, and the failures were governance failures rather than technical ones. And India already has UPI, an account aggregator and a working depository, which is largely correct for the retail and data layers. What survives both concessions is narrow and specific: bond secondary settlement, cross-border, and deep-tier MSME receivables, none of which those rails were built to solve.
Module E — what is actually moving on privacy, and what is notModule F — every objection in its strongest form, with its residual weakness
The full briefing
Seven modules, each with its sources.
What this is: A seven-module briefing, drawn from published sources, on where distributed-ledger settlement and tokenisation stand for Indian institutional finance, built for readers who have seen several blockchain pitches this year and were unconvinced by all of them.
-
What shipped
- Production tokenisation is confined to cash and short-term money: deposit tokens, money-market and Treasury funds, repo, stablecoins.
- Bonds, equities and trade finance are pilots or failures.
- The world's highest-volume system, Broadridge's repo platform at roughly $8tn in a single month, is permissioned rather than public.
- TradeLens, we.trade, Marco Polo, Contour and the ASX CHESS replacement all failed, almost none of them for cryptographic reasons. They failed on consortium governance and competitor distrust, and the same failure modes are latent in India's IBBIC/IBDIC.
-
What's legal in India
- No ban, and no law either, which for the institutional case are very different things.
- The binding constraint is unaddressed legal ground rather than prohibition: on-chain settlement finality and ledger-as-legal-register are not contemplated by Indian statute, and supervisory caution does the rest.
- Only the private-crypto route is genuinely restrictive, via a punitive tax, and that is not this case.
- The widest permitted perimeter is GIFT City rather than the domestic market, though the domestic sandbox moved first in September 2026 and now carries a live tokenised-bond issuance.
-
Where the value is
- The largest rupee prizes and the nearest permitted pilots do not overlap, and that gap is the whole strategic problem.
- The big opportunities sit in the domestic RBI/SEBI perimeter where the law is silent, while the permitted pilots are offshore, tiny, or aimed at the wrong leg.
- SEBI's September 2026 bond pilot tokenised primary issuance, which was never slow, and left the illiquid secondary market untouched.
- For most of these processes the incumbent rail already clears the trade, which leaves fraud or capital mobility as the only honest marginal case.
-
Ethereum vs alternatives
- The choice is three-way: public chains, multi-party permissioned (Canton), and single-operator permissioned EVM. The middle option is usually left out of the argument.
- Ethereum wins on uptime, counterparty reachability and India-available talent.
- It loses on confidentiality, cost predictability, permissioning granularity and legally recognised finality, which are precisely the criteria that decide bank settlement.
-
The privacy question
- The forward-looking answer to the confidentiality finding that runs through A, D and F.
- Ethereum's base layer is not becoming confidential and was never proposed to be; the work sits in overlays.
- One regulated deployment exists: tokenised money-market funds from four large managers, distributed through the FCA-regulated Archax with a privacy wrapper since February 2026. It is at the fund layer rather than the bank-settlement layer.
- SWIFT built its shared ledger on Ethereum layer-2 technology and kept it permissioned.
-
The objections
- Each objection is stated in its strongest form, with the honest response and the residual weakness that survives it.
- The regulatory objections are the strongest and mostly correct as stated, so conceding them is more persuasive than defending against them.
- The two an opponent is most likely to win are "every consortium blockchain failed" and "we already have UPI". The second weakened in September 2026, when the RBI and SEBI built atomic securities settlement on a new ledger rather than extending UPI.
- Lead with the specific rupee problem and the named owner, never with the technology.
-
How adoption happens
- Indian financial infrastructure adopts in a repeatable order: statute first, a regulator-owned utility second, a mandate or subsidy third, phased compulsion fourth, network effects last.
- A tokenised settlement layer moved to stage one-to-two in September 2026: a regulator-blessed utility now exists, but it is still pre-statute, running on a sandbox relaxation with neither a mandate nor a subsidy.
- Demat scaled only under compulsion. Account Aggregator, built without a mandate, is under 10% conversion after five years.
- A conference convenes and aligns; the sandbox procures, which is what Global Fintech Fest 2026 demonstrated.
- Figure Ledger Every quantitative claim in the briefing with its figure, unit, as-of date, source and tier (T1 to T5). Rows are deep-linkable; the full set is JSON.
- Reconciliation A cross-module audit of the briefing: where the modules contradict each other, which figures rest on weak sources, and which claims were retired.