Module G — Adoption Precedent and the Devcon Question

The 30-second answer

New financial infrastructure in India crosses into adoption through a repeatable sequence: statute first, a regulator-owned utility second, a mandate or subsidy third, phased compulsion fourth, network effects last. A tokenised settlement layer moved up that ladder in September 2026 and is now at stage one to two: SEBI's Demat 2.0 pilot, launched 10 September 2026, put a regulator-blessed utility in the field, built by the depositories and settled in wholesale CBDC, but scoped by a sandbox rather than a statute and carrying neither a mandate nor a subsidy. The sequence held exactly as this module describes: the utility arrived from the regulator, not from market pull. The closest analogue, demat, scaled only under compulsion, not market pull; the cautionary analogue, the Account Aggregator, shows a consent network without a mandate produces enablement without usage (under 10% conversion after five years). For the conference question: institutional finance people attend when a named regulator is on the programme, the format is a closed roundtable not a public stage, and it is framed as policy or standards work, and even then a conference convenes and aligns; it does not produce a pilot. The pilot pathway is the sandbox.

The 5-minute summary

The adoption model. Every successful Indian financial-infrastructure transition of the last three decades was preceded by, or accompanied by, a statute or a regulator-owned utility, never by market pull alone. Dematerialisation had the Depositories Act 1996 and NSDL; UPI had NPCI and RBI oversight; RTGS/NEFT were built and run by the RBI itself. Then adoption was forced or paid for: demat by phased compulsion, UPI by a funded zero-MDR subsidy. Network effects came last, not first.

Where tokenised settlement sits, specifically. Stage one to two, as of September 2026. The RBI's tokenised-CD pilot on UMI and SEBI's Demat 2.0 bond pilot are live, and Demat 2.0 is a regulator-blessed utility in the stage-two sense: built by NSDL and CDSL, settled in central-bank money, with the depository record still authoritative. What it does not have is the stage-one statute. It runs on a sandbox relaxation bounded to its own scope and period, not on a recognition of on-chain finality or ledger-as-register, and it carries neither a mandate nor a subsidy. The next stage still requires an RBI designation under the Payment and Settlement Systems Act for any settlement rail, the one lever the RBI can pull administratively, and a decision on whether adoption will be mandated or subsidised. Absent that decision, the Account Aggregator outcome (enablement without usage) remains the base case for stages three to five, and the untraded secondary leg of the bond pilot is the first place to watch for it.

The two most instructive cases. Dematerialisation is the closest structural analogue: it replaced a physical register with an electronic one against active broker and investor resistance, and it worked only because a statute, a regulator-owned utility, and phased compulsion arrived together, since none alone sufficed, and mass adoption still took roughly a decade. The Account Aggregator is the cautionary tale: a Master Direction, a coordinating body, and regulatory push produced 326 million linked accounts but under 10% conversion from enabled to actually-linked, because the data-holding incumbent had weak incentive to participate. A tokenised layer faces the identical incumbent-incentive problem.

The conference question, answered honestly. What draws senior Indian financial-institution people is a policy or standards framing with a named regulator present (the Global Fintech Fest model, or the Point Zero Forum's regulator-inclusive closed format), rather than a vendor showcase or a "Web3 summit" whose optics carry compliance risk. A developer conference can create senior introductions, align on standards, and let regulators observe in a low-commitment setting. It cannot produce a pilot or a procurement: in India that mechanism is the regulatory sandbox. No sourced outcome links any Ethereum developer-conference institutional track to an institutional pilot. So the honest posture is to convene, align, and feed a pre-arranged sandbox destination, since enablement without a mechanism produces no usage, the Account Aggregator lesson applied to events.

The full report

This is the module as originally researched. UPI, Account Aggregator, ONDC and conference figures move monthly and should be re-checked before use after roughly Q4 2026; historical cases (demat, Aadhaar, RTGS) are stable. The summary tiers reflect the reconciliation pass. See the Reconciliation tab and Figure Ledger.

Part one: how financial infrastructure crosses into adoption in India

Case 1: Dematerialisation of securities (1996–2002), the closest structural analogue. The Depositories Act 1996 created the legal basis; NSDL (promoted by IDBI, UTI, NSE) commenced operations 20 November 1996; CDSL followed in 1999. The trigger was the 1992 Harshad Mehta scam and the problems of physical certificates (bad delivery, forgery, 14-day settlement). Adoption was driven by phased compulsion, not choice: SEBI required institutional investors to settle in demat form in 8 scrips from January 1998, and all investors from 4 January 1999, expanding in phases to shares accounting for >90% of trading volume. It met documented resistance: Parliament kept the electronic system as a parallel "substitute" rather than overwriting the paper regime, and older investors and brokers were apprehensive; even two decades later SEBI was still forcing the last physical holdings into demat. Scale was still modest six years in: NSDL reported ~5 million investor accounts and ₹9,53,914 crore (~$108bn) custody value by February 2004. Lesson: demat succeeded because a statute, a regulator-owned utility, and phased compulsion arrived together; tokenisation today has a pilot but none of the three at scale. India translation: a tokenised securities register (SEBI's Demat 2.0 pilot) is the direct descendant; owned by SEBI plus NSDL/CDSL. The Depositories Act still contemplates a depository rather than a ledger, and SEBI took the second of the two routes this case identified: a token-as-representation model with the depository record remaining authoritative, delivered through the regulatory sandbox rather than through an amendment. The prediction held; the amendment is still outstanding.

Case 2: UPI (2016–2026), the mandate-plus-subsidy model. Launched by NPCI under RBI oversight, April 2016, 21 banks; bank participation rose to 741 by July 2026, volume from 1.78 crore transactions (FY17) to 24,162 crore (FY26). The demand accelerant was demonetisation (Nov 2016); the supply accelerant was price, with zero-MDR since January 2020 and a direct subsidy substituting for the removed revenue. But the model is not self-financing: the Parliamentary Standing Committee's 32nd Report (12 March 2026) called zero MDR "financially unsustainable," with incentive support covering only ~11% of industry cost; the 2021–25 incentive totalled ₹8,730 crore (~$986m). Lesson: India will subsidise adoption of infrastructure it deems a public good, but the subsidy is large, contested, and forces the pricing question. India translation: a tokenised wholesale/institutional rail (the RBI's e₹-W-settled pilot); blocked by the absence of a revenue model and the unresolved VDA tax question; would need RBI designation for finality, a CBDT clarification, and a fee-or-subsidy decision.

Case 3: Aadhaar and eKYC (2016–2019), the litigation-and-reversal case. Aadhaar-based eKYC became embedded in banking after 2016, then was curtailed when the Supreme Court (26 September 2018) struck down Section 57 of the Aadhaar Act, halting private eKYC overnight, before a 2019 amendment permitted voluntary opt-in. Lesson: a private-sector data/identity primitive can be built and adopted, then reversed by the courts if the legal basis is contractual rather than statutory, so sequencing must put the statute first.

Case 4: Account Aggregator (2021–2026), the "slower than expected" case. A Master Direction basis (2016), launched September 2021, with Sahamati recognised as the ecosystem's SRO (5 June 2026); 326.30 million cumulative linked accounts and 538.32 million fulfilled consents by July 2026. But the enabled-to-linked conversion remained under 10% (284.6 million linked against 2.88 billion enabled, March 2026), the central weakness, caused by weak data-holder reliability, uneven onboarding, low awareness, and the absence of a commercial incentive for the incumbent to make sharing reliable. Lesson: this is the strongest counter-example to "build the rails and adoption follows," and the outcome a tokenised layer should expect absent compulsion or subsidy.

Case 5: ONDC (2021–2025), the interoperable-network case. Government-backed, reached 1,200+ cities and 7 lakh+ sellers by early 2025, but retail orders peaked at 6.5 million (October 2024) and fell to 4.6 million (February 2025) tracking incentive withdrawal, with a ₹1.5/transaction fee introduced April 2025 and mobility/logistics dominating volume. Lesson: interoperability alone does not overcome incumbent network effects, and early growth was subsidy-driven, which corroborates the governance/network-effect failure thesis.

Case 6: NEFT, RTGS, NACH, the earlier settlement generation. The RBI built and operated the wholesale rails directly: RTGS live 26 March 2004, NEFT November 2005, both on SFMS/INFINET, under the PSS Act 2007; NACH (NPCI) replaced the RBI's regional ECS from 1 May 2016. Lesson: for wholesale settlement the RBI does not wait for the market; it builds and designates, which is why the near-term Indian tokenisation architecture is CBDC-settled and RBI-run, not public-chain. Settlement finality for a tokenised system is not covered by the PSS Act until the RBI designates it, an administrative act the RBI already controls.

The derived model. The stages run: (1) trigger/statute; (2) regulator-owned or regulator-blessed utility; (3) mandate or subsidy; (4) phased compulsion/expansion; (5) network effects/organic use. A tokenised settlement layer sat between stage 0 and stage 1 when this module was researched and moved to stage 1–2 in September 2026: pilots are live and Demat 2.0 is a regulator-blessed utility, but there is still no enabling statute, no mandate and no subsidy, and the utility runs on a sandbox relaxation rather than a designation. The next stage requires an RBI PSS-Act designation for any settlement rail and a mandate-or-subsidy decision; absent the latter, enablement-without-usage is the base case. Revised September 2026.

Part two: what brings institutions to developer-adjacent conferences

Sibos (SWIFT): the reference case. Sibos 2025 (Frankfurt) drew >12,500 with 168 countries, senior executives from 200+ banks, on operations and standards (T+1, ISO 20022, digital-asset interoperability). Institutions attend because it is owned by their own cooperative and framed around standards; annual since 1978, the strongest repeat signal.

Point Zero Forum (GFTN / Swiss SIF): a curated policy-technology dialogue (Zurich, annual since 2022) co-convened with the Swiss finance ministry, the BIS Innovation Hub, MAS, FINMA and the SNB; >2,000 participants, ~one-third public sector, the RBI a listed 2025 attendee, with free "Policy passes" for regulators. Institutions and regulators attend for the explicit public-private policy framing and Chatham-House candour.

Token2049: ~25,000 attendees (Singapore 2025), foregrounding institutional participation, but its own composition is ~15–20% institutions, mostly founders/BD/developers, and much of the programme conflates the infrastructure question with the token-asset question. A lead-generation venue, not a policy venue.

Consensus (disconfirming): at Consensus Hong Kong 2026 the mood was "somber," institutional trading teams "significantly down," with a read that crypto is becoming "a license-driven business where compliance matters more than crypto-native experience." Institutional attendance at a crypto-media conference does not equal institutional commitment.

Devcon / Devconnect institutional programming (the core question): Devconnect Argentina 2025 drew 14,000+ from 130+ countries, 53% first-time Ethereum Foundation attendees. Institutional programming ran as adjacent events, namely "Casa ZK: Institutional Day" (19 Nov 2025, closed-door, ZKsync/Ethereum Foundation) and "The Capital Layer" (18 Nov 2025). The precedent extends to the EEA Industry Day at Devcon 7 Bangkok (11 Nov 2024, sponsored by Circle, EF, Microsoft, EY). The repetition signal is honest but qualified: the theme of an institutional/RWA day recurred across 2024 and 2025, but under different organisers each year, and there is no single continuously branded, proven institution-facing product. And no primary or tier-1 source attributes any specific institutional pilot to attendance at any of these tracks. They convene and align; they are not documented to procure.

The Indian context. The format that reliably draws the most senior Indian FI and regulator participation is the Global Fintech Fest in Mumbai (organised by the Payments Council of India, NPCI and the Fintech Convergence Council with RBI/IFSCA support). GFF 2024 drew >80,000 including 120 central bankers, with PM, RBI Governor and SEBI Chair keynotes. GFF 2026 (8–11 September) is the sharpest available illustration of the line Module B draws: the RBI Governor and SEBI Chairman launched Demat 2.0 from the main stage, tokenisation was one of the fest's three named pillars, and crypto and stablecoins were kept off the programme, with speaker guidance instructing participants to avoid crypto remarks on stage. The infrastructure/asset distinction is now legible in the agenda itself, which is a more useful brief for anyone planning an Indian convening than any amount of argument about it. Practical constraints (analytical synthesis, not sourced): being listed at a "crypto" event carries reputational risk given the RBI's stated stance, which a policy/standards framing removes; senior leaders participate on closed roundtables and regulator panels, not open developer stages; and regulator presence decides attendance, since a developer conference without a regulator on the programme will not draw senior institutional participation.

Format recommendations. (1) A closed-door, Chatham-House institutional roundtable co-badged with a policy convener, held adjacent to the developer programme, on the Point Zero Forum and Casa ZK precedent; it removes the crypto-optics problem and matches the seniority expectation. (2) A standards-and-interoperability working session modelled on Sibos's ISO 20022/T+1 programming rather than a product showcase, because Indian institutions engage with infrastructure as a standards question. (3) A regulator-anchored policy panel co-hosted with an existing Indian convener (within or alongside GFF), with a named regulator confirmed before the event is announced, since regulator presence decides attendance.

Honest assessment. A developer conference can create senior introductions, align on standards, let regulators observe at low commitment, and surface which institutions have live interest. It cannot produce a pilot or a procurement: in India that mechanism is the sandbox. September 2026 demonstrated both halves in one week. Demat 2.0 was launched at GFF and produced by SEBI's Regulatory Sandbox, where REC's issuance had already executed three days before the announcement. A conference is where a regulator chooses to be seen doing the thing; the sandbox is where the thing is done. Plan for the venue accordingly, and do not mistake stage time for a pathway. For it to matter: before, a named regulator confirmed, a closed policy-framed format, a specific infrastructure question, and a defined sandbox destination; after, a written follow-through into a sandbox application or standards working group within weeks. Without a pre-arranged destination the convening dissipates, the Account Aggregator lesson applied to events.

Module close

1. Findings hardest to dismiss. Demat scaled only under compulsion (SEBI AR 1998-99); the Account Aggregator's enabled-to-linked conversion is under 10% after five years (Sahamati); UPI's subsidy covers only ~11% of industry cost (Standing Committee 32nd Report); RTGS/NEFT were RBI-built and derive finality from PSS Act designation (a route unavailable to on-chain settlement until the RBI designates it); no sourced outcome links any Ethereum developer-conference track to an institutional pilot.
2. Strongest chart. UPI monthly volume (FY17–Jul 2026) with markers at demonetisation (Nov 2016) and zero-MDR (Jan 2020), against the bank-count rise (21 to 741), from the PIB "UPI completes 10 years" release and NPCI statistics; it visualises the mandate/shock/subsidy inflection model.
3. Claims most likely to be challenged. "Tokenised settlement is at stage 1–2" (Demat 2.0 is a regulator-blessed utility, but on a sandbox relaxation with no statute, mandate or subsidy; concede that a live ₹1,025 crore issuance reads as further along than the stage label suggests); "adoption needs a mandate or subsidy" (demat compulsion, UPI incentive, AA's sub-10% conversion; if challenged with organic UPI growth, note it required a shock plus a funded zero-MDR regime); "a developer conference can't produce a pilot" (the absence of attributable outcomes; the sandbox is the Indian pilot pathway).
4. One-sentence summary. In India, new financial plumbing becomes real only when a law, a regulator-run utility, and either a mandate or a subsidy arrive together, and tokenised settlement today has pilots but none of those three, so a conference in Mumbai can convene and align the right people but cannot substitute for the statute and the regulator's decision that every prior success required.
5. What this module could not establish. Money20/20 Asia specific attendance/composition; any causal outcome from a developer-conference institutional track; whether SEBI will mandate or subsidise tokenised settlement once Demat 2.0 leaves the sandbox, which on this module's own model decides whether it reaches stage three or stalls where the Account Aggregator did; and whether any Indian bank's compliance function has formally cleared senior participation in an Ethereum-branded event.