Who Holds the Keys to a SEBI Demat 2.0 Tokenised Bond?
In SEBI's Demat 2.0 pilot for tokenised corporate bonds, the depositories hold and manage investors' private keys, and the depository remains the authoritative record of beneficial ownership under the Depositories Act, 1996. The bond is a native token on a private, permissioned ledger, but freezes, attachments and early exits run through the investor's existing demat account, not through a wallet the investor controls.
TL;DR — Key Takeaways
- ✓Keys: Under Question 7 of SEBI's Demat 2.0 FAQ, the depositories hold and manage investors' private keys. Investors never handle keys and have no self-custody option.
- ✓Record: The depository remains the authoritative record of beneficial ownership under the Depositories Act, 1996. The DLT ledger is the form of that record, not a second register.
- ✓Freezes: A freeze, attachment or direction on the demat account or the ISIN applies to the tokenised holding. Existing legal controls reach the token through the account.
- ✓Exit: Before secondary trading opens, investors can request a demat-to-demat transfer through the depositories, but the payment may settle outside the atomic DvP architecture.
- ✓Scope: Three issuers raised Rs 1,025 crore in September 2026 under SEBI's regulatory sandbox. Stage I is institutional; secondary trading and retail access are Stage II.

Who holds the private keys in Demat 2.0?
The depositories do. Question 7 of SEBI's 24-question Demat 2.0 FAQ says they “will hold and manage the private keys on behalf of investors”, so an investor in a tokenised corporate bond never controls a key.
The bond is a native token. Question 1 says the token “is the corporate bond”, issued on a private, permissioned DLT network owned by the depositories. Yet the investor does not hold that token in a wallet of their own. The Demat 2.0 account sits inside the existing demat account, the depository runs it, and the holding shows up in the same depository interface and holding statement the investor already uses. Registration is a consent step: the investor links an eligible demat account to a CBDC wallet through the depository interface (Question 6).
“The depositories will hold and manage the private keys on behalf of investors. Therefore, investors do not need to independently manage cryptographic keys or acquire specialised DLT infrastructure.”
SEBI, FAQs on Demat 2.0: Pilot for Tokenised Corporate Bonds, Question 7
Three consequences follow, by our reading of the FAQ. First, key loss and key compromise become depository operational risks, so the investor needs no seed phrase, no wallet recovery function and no hardware. Second, there is no path for an investor to move the token to a wallet outside the depository system, because the investor never holds a key that could sign such a transfer. Third, the security of every holding depends on how the depositories store and use keys. The FAQ does not say whether they use hardware security modules, multi-party computation or another scheme, and it does not say whether there is one key per investor or a pooled arrangement.
How does Demat 2.0 compare with a public-chain RWA token?
Demat 2.0 makes the opposite trade-off from most public-chain RWA tokens: a native token with depository-held keys and one statutory record, instead of investor or custodian wallets with a separate legal register. The table compares the two on the five questions custodians ask first.
| Question | SEBI Demat 2.0 pilot | Typical permissioned public-chain RWA token (for example ERC-3643) |
|---|---|---|
| Who holds the private key | The depository, on behalf of the investor (FAQ Q7) | The investor, a qualified custodian or a wallet provider; the issuer side holds separate agent keys |
| Which record is authoritative | The depository, under the Depositories Act, 1996; the DLT ledger is the form of the record (Q16) | Depends on jurisdiction and structure; often an off-chain register kept by a transfer agent or registrar, with the chain as a mirror or as the register itself |
| How a freeze is applied | A freeze or attachment on the demat account or ISIN applies to the token (Q17) | An agent key calls an on-chain freeze function on a wallet address or a token amount |
| Where KYC comes from | The investor's existing demat KYC; no fresh KYC (Q6) | Identity claims from trusted issuers, checked by the token on each transfer |
| How an investor exits before a market exists | Demat-to-demat transfer on request through the depositories; cash may settle outside the atomic architecture (Q19) | On-chain transfer to any eligible wallet, subject to the compliance rules; cash settles separately unless a DvP contract is used |
The right-hand column is our general description of public-chain designs, not a single product. Its weak point is the gap between a wallet balance and the legal record, and the concentration of power in issuer-side agent keys. Our analysis of who controls ERC-3643 agent keys covers the seven privileged functions those keys can call. Demat 2.0 closes both gaps by putting keys, ledger and legal record with the same statutory institutions. The cost is that the investor gives up direct control of the asset, and the depositories become a single point of operational failure.
Which record is legally authoritative: the depository or the DLT ledger?
The depository. Question 16 says the depository “remains the authoritative record of beneficial ownership” and that the DLT ledger is only the form in which the record is kept for the pilot. The Depositories Act, 1996 role is unchanged.
“The DLT ledger is the form in which the record is maintained for purposes of the pilot; it does not displace the depository's statutory role under the Depositories Act, 1996.”
SEBI, FAQs on Demat 2.0, Question 16
This is the answer that many tokenisation models leave open. In a typical structure, a token on a public chain and a register kept by a transfer agent can disagree, and someone must decide which one wins. Demat 2.0 avoids that question by design. The ledger is the depository's own record in a new technical form, so there is one record with one legal owner. SEBI's press release frames this as the pilot's distinguishing point: India is, in SEBI's words, the first country where corporate bonds were issued natively on a ledger “with the record of ownership held by a country’s statutory depositories”.
The bond's legal character does not move either. Question 2 says a tokenised bond remains a security under the Securities Contracts (Regulation) Act, 1956, with the same ISIN, coupon, maturity, covenants, rating and investor rights. Question 3 adds that the token bears the same ISIN as the bond issue, and Question 4 says the ISIN is flagged as a pilot or tokenised ISIN. Coupons and redemptions are paid from the holdings recorded on the ledger on the record date (Question 12), which works because the ledger and the authoritative record are the same thing. How custodians build this kind of record-keeping into a compliance model is the subject of our guide to institutional RWA custody and compliance requirements.
How do freezes and attachments reach a tokenised bond?
Through the demat account. Question 17 says a freeze, attachment or direction on the demat account or on the relevant ISIN or token holding applies to the linked tokenised holding, because existing regulatory and legal controls continue to apply.
“A freeze, attachment or direction applicable to the demat account or the relevant ISIN/token holding will apply to the linked tokenised holding as well.”
SEBI, FAQs on Demat 2.0, Question 17
For a court, a tax authority or SEBI, nothing changes in the workflow: the order still names a demat account or an ISIN, and the depository carries it out. No one has to identify a wallet address or ask an issuer to call a freeze function. That is a direct result of depository key custody. Because the depository holds the key, the depository can execute the restriction on the ledger without the investor's cooperation.
Two limits apply. The FAQ states the legal outcome, not the mechanics: it does not say whether a freeze is enforced in the token's smart contract, at the node level or only in the depository's own systems. And Question 21 lists “regulatory controls and restrictions” and “smart-contract-based servicing and exception handling” among the things the pilot is meant to test, so the mechanics may still change. For any design, the compliance evidence that matters is the same: each freeze or attachment should be traceable from the legal order to the entry in the authoritative register and to the ledger state that enforces it.
How can an investor exit before secondary trading opens?
By an interim transfer. Question 19 says a peer-to-peer or demat-to-demat transfer may be enabled on request through the depositories before secondary-market trading is live, with payment possibly completed outside the atomic settlement architecture.
“The payment leg may be completed outside the atomic settlement architecture through CBDC or banking channels. Thus, the investor is not intended to be locked into the investment during the interim period.”
SEBI, FAQs on Demat 2.0, Question 19
The detail that matters for risk teams is the payment leg. At issuance, the bond and the CBDC payment settle as one linked transaction, so either both legs settle or neither does. In an interim exit, the bond moves through the depository while the cash may move separately, through CBDC or a bank transfer. That puts some settlement risk back between buyer and seller for these trades, by our reading. The exit is also on request, so it depends on the depositories enabling it; it is not an open order book.
The longer-term route is Stage II, which enables secondary-market trading and extends access to retail participants (Question 22). Question 11 says there will be no new tokenised exchange: existing RFQ platforms and OTC reporting platforms of the stock exchanges will be linked to the DLT, and only the settlement legs move onto the tokenised infrastructure.
Which issuers have used Demat 2.0 so far?
Three issuers raised Rs 1,025 crore in tokenised bonds by 10 September 2026, according to SEBI press release PR No. 56/2026. The FAQ was issued with that press release.
| Issuer | Issue date | Amount raised | Investors |
|---|---|---|---|
| REC Limited (public sector NBFC) | September 7, 2026 | Rs 500 crore | 18 |
| L&T Limited | September 9, 2026 | Rs 500 crore | 4 |
| IIFL (private NBFC) | September 9, 2026 | Rs 25 crore | 1 |
| Total | Rs 1,025 crore | 23 |
Issuance runs through the stock exchanges' existing Electronic Bidding Platform, and issue proceeds land in the issuer's CBDC wallet (Question 4). The cash leg uses RBI's wholesale e-rupee through the Unified Market Interface, settled as atomic delivery-versus-payment; we covered that cash leg in our page on the first REC issue and wholesale CBDC settlement, and the trade-offs of the model in our analysis of what atomic settlement changes for liquidity.
“Three companies have issued tokenised bonds so far, aggregating ₹1,025 crore.”
SEBI, PR No. 56/2026, Successful launch of Demat 2.0, Mumbai, September 10, 2026
Who runs the ledger, and on what legal basis?
The Market Infrastructure Institutions run it with technology support from NPCI, on a private, permissioned ledger whose nodes are initially operated by the depositories and stock exchanges (Question 20). The pilot runs under SEBI's Regulatory Sandbox (Question 23).
Node access is planned to widen in steps. Stage I covers issuance through the Electronic Bidding Platform with asset servicing on the ledger, with institutional participants. Stage II adds secondary trading and retail access. Stage III may extend nodes to credit rating agencies, depository participants and other regulated entities, and consider other instruments (Question 22). Any relaxation needed for the pilot is granted inside the sandbox for a defined scope and period, and SEBI says the pilot is meant to test the architecture before a broader framework is considered. Rules that apply to the bond itself, such as credit rating, debenture trustees, listing and disclosure, continue to apply (Question 13).
What should custodians and compliance teams take from Demat 2.0?
Demat 2.0 shows a regulator choosing depository key custody and a single statutory record over self-custody. It is a reference design for what a native token can mean when the investor never holds a key.
- Who it fits: institutional bond investors who want atomic settlement and automated coupons without running wallets, and regulators who want freezes and attachments to work through existing account-level orders.
- Who it does not fit: investors who want to hold a security in their own wallet, move it across platforms or use it as on-chain collateral outside the depository system. The FAQ offers no such path.
- Where it can break: the depositories hold every key, so their key management and ledger operations become a concentrated operational risk; interim exits settle cash outside the atomic model; and the freeze mechanics on the ledger are not yet public.
For issuers outside India, the useful lesson is the order of questions. Decide first who holds the keys and which record is authoritative, then design freezes, attachments and exits around that record. A token design that answers issuance but not these questions leaves the hard part for later.
Frequently Asked Questions
Who holds the private keys for a Demat 2.0 tokenised bond?
The depositories. Question 7 of SEBI's Demat 2.0 FAQ says the depositories "will hold and manage the private keys on behalf of investors", so investors never manage cryptographic keys or run DLT infrastructure. The investor sees the holding through the existing depository interface and holding statement. In practice this means a lost or compromised key is a depository operational problem, not an investor recovery problem, and there is no self-custody option in the pilot.
Is the DLT ledger or the depository the legal record of ownership?
The depository. Question 16 of the FAQ says the depository remains the authoritative record of beneficial ownership, and that the DLT ledger is only the form in which that record is kept for the pilot. The ledger does not displace the depository's statutory role under the Depositories Act, 1996. Because SEBI's press release says the ledger is owned by the depositories, the token record and the legal record sit with the same institutions, so there is no second register to reconcile.
Can a regulator or court freeze a Demat 2.0 tokenised bond?
Yes. Question 17 of the FAQ says existing regulatory and legal controls continue to apply, and a freeze, attachment or direction on the demat account or the relevant ISIN or token holding applies to the linked tokenised holding as well. The order targets the demat account or the ISIN, as it does today. The FAQ does not describe the smart-contract mechanics, and it lists regulatory controls and restrictions among the things the pilot is meant to test.
How can an investor sell a Demat 2.0 bond before secondary trading starts?
Through an interim transfer. Question 19 says a peer-to-peer or demat-to-demat transfer may be enabled on request through the depositories before secondary-market trading is live. The payment leg may then settle outside the atomic architecture, through CBDC or ordinary banking channels. So an early exit is possible, but it does not carry the same both-legs-or-neither guarantee as a pilot issuance. Secondary trading through existing RFQ platforms is planned for Stage II.
Does an investor need a new demat account or fresh KYC for Demat 2.0?
No. Question 6 says the Demat 2.0 account is an extension of the investor's existing demat account, not a separate account, and the existing KYC is used. The investor registers through the depository interface by linking the eligible demat account to a CBDC wallet and giving consent. The issuer needs no Demat 2.0 account, but it needs a CBDC wallet linked to its bank account to receive proceeds and pay coupons and redemptions.
Related Articles
Who Is the Transfer Agent for a Tokenized Security?
Legal ownership lives in the master securityholder file, not in a wallet balance, even when a registered transfer agent keeps that file on a blockchain.
Who Keeps the Register for a Tokenised Luxembourg Fund?
Under the CSSF tokenisation FAQ, a control agent does not replace the UCI administrator that keeps the register.
Why Can't a Dutch Security Be Issued Only as a Token?
The AFM and DNB found Dutch law blocks direct tokenisation, so Dutch issuers run hybrid structures with two records.
What Must an Issuer Report After Freezing Sanctioned Tokens?
An on-chain freeze of sanctioned holdings starts the OFAC reporting clock; it does not finish the compliance work.