Custody & Infrastructure10 min read
MB
Editorial Team
·November 14, 2026

Can a Tokenized Private Fund Interest Skip a Custodian?

The privately offered securities exception lets a registered adviser hold certain private securities without a qualified custodian. The SEC's October 2026 custody proposal treats tokenized securities as crypto assets and says one fails the exception if its ownership record is not only on the issuer's books or it can move without the issuer's prior consent.

TL;DR — Key Takeaways

  • ✓The proposal: SEC Release IA-7023 / IC-36353 (File No. S7-2026-35, dated 1 October 2026) would redesignate rule 206(4)-2 as rule 223-1 and treat tokenized securities as crypto assets. Comments are due 7 December 2026. It is not a final rule.
  • ✓The exception: The privately offered securities exception moves to 223-1(b)(2) with its three prongs unchanged: non-public offering, uncertificated with ownership recorded only on the issuer or transfer agent books, and transferable only with prior consent.
  • ✓The SEC position: Request for comment 3 says a crypto asset fails the exception if its ownership is not recorded only on the issuer or transfer agent books, or if it can move without the issuer's prior consent. It asks whether any crypto asset could qualify.
  • ✓The fallback: An adviser holding any part of the private keys is in self-custody under proposed 223-1(b)(7): a written, quarterly finding that no qualified custodian will hold the asset, joint authorization, one address per client and an annual internal control report.
  • ✓The design question: Whether an issuer-maintained on-chain register is the issuer's books, and whether an identity allowlist is prior consent, is unanswered. A comment letter is the place to argue it.

Ready to get started?

Join others who are already using our platform.

Can a Tokenized Private Fund Interest Skip a Custodian?

What does the SEC custody proposal say about privately offered securities?

It keeps the exception word for word at a new address, proposed rule 223-1(b)(2), and then says in request for comment 3 that crypto assets would not meet it if ownership is not recorded only on the issuer or transfer agent books, or if they can move without the issuer's prior consent.

The release is titled “Adviser and Regulated Fund Custody Rules; Crypto Custody Rules” and carries Release Nos. IA-7023 and IC-36353. It was dated 1 October 2026, published in the Federal Register on 6 October 2026, and asks for comments by 7 December 2026. It proposes to redesignate the Advisers Act custody rule, rule 206(4)-2, as rule 223-1 (footnote 124). Under the current rule, the exception lets an adviser hold a client's privately offered securities without a qualified custodian. The Commission adopted it in 2003 because, as the release puts it on page 258, the need for issuer or holder consent before a transfer makes these assets “less likely to be stolen by a third party or simply lost.”

The earlier Blockmaze reading of this question, in the analysis of whether crypto custody relief covers tokenized fund shares, called the exception's availability for tokens contested. The proposal does not settle it, but it now states the Commission's starting position and the two facts it will test.

“Crypto assets would not be able to meet this exception if, for example, records of their ownership are not recorded only on the books of the issuer or its transfer agent in the name of the client, or if they can be transferred without the prior consent of the issuer.”

SEC Release IA-7023, request for comment 3, pp. 49-50

Is a tokenized private fund interest a crypto asset under the proposal?

Yes, if any part of its ownership record is kept on a blockchain. The release says crypto assets include tokenized securities “where the record of ownership is maintained in whole or in part on or through one or more crypto networks.”

Proposed rule 223-1(d)(3) defines a crypto asset as “any digital representation of value that is recorded on a cryptographically secured distributed ledger.” For an adviser, the rule covers only crypto assets that represent funds or securities. A limited partnership interest issued as a token is a security, so it is in scope. The words “in whole or in part” matter: a fund that keeps its legal register off-chain but mirrors holdings to tokens still has a record of ownership maintained partly through a crypto network, on a plain reading of the text.

Four other proposed definitions decide how the rule applies. “Crypto network” is a blockchain or similar distributed ledger network. “Key materials” are the private keys, “or any part thereof”, needed to move the asset. “Self-custody” is “possession of any portion of a client crypto asset's key materials.” “Crypto asset address” is the on-chain identifier that receives and stores the asset. The release adds on page 59 that self-custody turns on actual possession of key materials, not on the authority to obtain them, although custody can still be imputed in the second case.

“Crypto assets would also include digital securities (commonly known as ‘tokenized’ securities), which are financial instruments enumerated in the definition of ‘security’ under the Federal securities laws that are formatted as or represented by a crypto asset, where the record of ownership is maintained in whole or in part on or through one or more crypto networks.”

SEC Release IA-7023, section II.A.1(b), p. 54

What are the three prongs of the exception, and where can a token fail?

The prongs are a non-public offering, an uncertificated security recorded only on the issuer or transfer agent books in the client's name, and transfer only with prior consent. A token can fail the second and third; the first is about the offering, not the technology.

Proposed rule 223-1(b)(2)(ii) keeps a fourth condition for pooled vehicles: a fund client can use the exception only if the fund is audited and the audited financial statements are distributed under paragraph (b)(4). A tokenized interest held for a fund-of-funds therefore needs the audit as well as a token that passes the prongs.

Prong in 223-1(b)(2)(i)What the SEC says about crypto assetsToken design fact that decides it
(A) Acquired from the issuer in a transaction not involving any public offeringNothing specific in request 3Offering exemption used (for example Regulation D); unchanged by tokenization
(B) Uncertificated, ownership recorded only on the books of the issuer or its transfer agent in the client's nameFails if records are not only on issuer or transfer agent books in the client's nameWho maintains the register; whether the chain is the register or a copy; whether the wallet maps to the client by name
(C) Transferable only with prior consent of the issuer or holdersFails if the asset can be transferred without the issuer's prior consentWhether every transfer is blocked unless the issuer or its agent has approved the receiver, and who can change that approval
(ii) Pooled vehicle audited, statements distributedUnchanged from current 206(4)-2(b)(2)(ii)Not a token question

Does an on-chain register count as the issuer's books?

The SEC has not said. If the issuer or its registered transfer agent keeps the master securityholder file and the chain is that file, there is an argument it is their book; a public ledger anyone can write to is harder to describe that way.

The release gives two signals. In the recordkeeping section (p. 349) it would let advisers keep required ledger records on a crypto network if the on-chain record is “true, accurate, and current”, and it expects off-chain records to fill gaps, for example to tie a public address to a named client. It cites the January 2026 staff Tokenization Statement, which observed that an issuer or its agent “uses onchain database records alongside offchain database records and associates the onchain information.” That is the integration model described in the guide to who acts as transfer agent for a tokenized security, where the legal record is the master securityholder file and the token balance is how it is expressed.

Two readings follow. Reading one: where the issuer or its transfer agent alone can register holders, update the register and reverse entries, the chain plus the linked off-chain file is the issuer's book, and the word “only” is met. Reading two: a balance recorded on a shared network that the holder's key can change is not recorded “only” on the issuer's books, because the network and the wallet are a second place where ownership lives. Request 3 uses the second framing as its example of failure. Neither reading is settled law; they are the two positions a comment letter would choose between.

Is an identity allowlist the issuer's prior consent?

Possibly, but the proposal does not answer it. An ERC-3643 token rejects any transfer to a wallet the issuer's agents have not registered, which is consent before the transfer; it is not consent to each specific transfer.

In the T-REX reference code, a transfer succeeds only if the receiver passes isVerified in the identity registry and every compliance module allows it. Only an agent can add a wallet to the registry. A holder can still move tokens between two already-registered wallets without the issuer doing anything at the time. Agents can also call forcedTransfer and wallet recovery to move tokens back, which is a remedy after theft rather than consent before it. These are agent-key powers, so who holds the agent keys matters as much as the code; the description here is from reading the code, not from running it.

The test the SEC set is functional. Request 3 asks what conditions would keep the exception limited to crypto assets “that provide external safeguards against the kinds of abuse the custody rule seeks to prevent.” The 2003 rationale was theft and loss by an outsider. A stolen key on an allowlisted token can send tokens only to registered wallets, and an agent can reverse the move. A stolen key on an open ERC-20 can send them anywhere, irreversibly. That difference is the argument for treating a registry gate as prior consent. The counter-argument is that a compromised agent key, or a registered wallet controlled by the thief, defeats it.

“Are there crypto assets that could qualify as privately offered securities? If so, what characteristics of such crypto assets and/or their crypto networks satisfy the conditions of the privately offered securities exception?”

SEC Release IA-7023, request for comment 3, p. 50

What applies if the exception is not available?

Either a qualified custodian holds the token, or the adviser self-custodies under proposed rule 223-1(b)(7). Self-custody requires a written finding, before custody and at least quarterly, that no qualified custodian will hold the asset.

The conditions below are taken from the proposed rule text in the release (pp. 729-733). Request 3 also asks whether a crypto asset that does qualify should be excepted from these conditions. On our reading of the proposed text, that means an adviser holding the keys to a qualifying token would still face paragraph (b)(7) unless the final rule says otherwise, because (b)(2) relieves only paragraph (a)(1).

Proposed 223-1(b)(7) conditionWhat it requires
(i) Qualified custodian determinationWritten finding, after due inquiry, that no qualified custodian will maintain the asset; before taking custody and at least quarterly; move to a qualified custodian as soon as reasonably practicable once one is available
(ii) Expertise and systemsDocumented safeguarding expertise; key management limited to designated supervised persons; joint authorization of transfers by two or more designated persons, at least one a management person; one or more addresses holding only that client's assets
(iii) CybersecurityAt least annual written risk assessment; measures to detect and remediate threats; incident response and recovery
(iv) Internal control reportFrom an independent public accountant within six months and then each calendar year, including verification that assets reconcile to the crypto network
(v) Annual reviewWritten review of the safeguarding systems and cybersecurity controls
(vi)-(vii) Account statementsQuarterly statements with address, network, balances and transactions; not required for an audited pooled vehicle
(viii) Financial asset electionWritten agreement to treat each asset as a financial asset and the adviser as a securities intermediary under applicable State law

For a tokenized private fund interest the first condition is the gate. If any qualified custodian will hold the token, the adviser cannot self-custody it. The broader custodian landscape, including bank and trust options, is mapped in the guide to institutional RWA custody requirements, and the history of the rule before this proposal is in the earlier piece on who can custody a tokenized security for an adviser.

What else in the release touches tokenized private interests?

Three items: request 12 on how custody of a tokenized security should work, request 215 on amending the exception for private fund interests, and the statement that registered funds have no such exception at all (p. 257).

  • Request 12 (p. 58). Asks what guidance the custody rules need for tokenized securities, and whether holding the associated crypto asset at a custodian or in self-custody would ever “not be sufficient to effectively hold the tokenized security in custody.” This is the case where the token and the legal interest can separate.
  • Request 215 (pp. 280-281). In the discretionary trading section, asks whether more specific text is needed for asset types including “private fund interests”, and whether the privately offered securities exception should be amended to accommodate them.
  • Registered funds (p. 257). “No similar provision exists under the Investment Company Act”. Requests 206 and 207 ask whether one should.

The same release also adds Form ADV questions on tokenized private funds; those reporting items are covered separately and are not repeated here.

“Are there any circumstances in which maintaining the associated crypto asset at a permitted custodian, or in self-custody by an adviser pursuant to the proposed adviser self-custody rule, would not be sufficient to effectively hold the tokenized security in custody under the Commission's custody rules?”

SEC Release IA-7023, request for comment 12, p. 58

What evidence would support the exception in a comment letter?

Evidence that the issuer or its transfer agent alone controls the register and every eligible receiver, and that a lost or stolen holder key cannot move the interest outside that control. The deadline is 7 December 2026.

Question the SEC askedEvidence an issuer or adviser could show
Recorded only on issuer or transfer agent books?Transfer agent agreement naming the chain as the master securityholder file; linkage from each wallet to a named holder off-chain; reconciliation procedure
Prior consent of the issuer?Contract code showing transfers revert unless the receiver is registered; list of keys that can register wallets; whether holder-to-holder moves between registered wallets need fresh approval
External safeguards against theft and loss?Recovery and forced-transfer procedure; multisig or approval policy on agent keys; record of how a lost-key case was handled
Features similar to privately offered securities?Offering exemption, subscription documents and the fund agreement consent clause that the token mirrors

Comments go through the SEC's comment form for File No. S7-2026-35. We have not reviewed the comment letters filed so far, and we do not know of any adviser that relies on the current exception for a permissioned token today.

Who does this apply to, and what was not checked?

It applies to SEC-registered advisers whose clients hold tokenized private fund interests or other tokenized private securities, and to issuers designing those tokens. It does not apply to registered funds, which have no such exception.

It matters most where the adviser holds keys to the wallet that holds the interest. If a qualified custodian holds the token and the adviser has no key materials, the exception question does not arise. Everything above is read from the proposing release as published on sec.gov. It is a proposal, not an adopted rule, and this is analysis, not legal advice. The Commission may answer request 3 either way, or not at all, in a final rule.

Frequently Asked Questions

Is the SEC custody proposal for crypto and tokenized securities already in force?

No. Release IA-7023 / IC-36353 (File No. S7-2026-35) is a proposed rule dated 1 October 2026 and published in the Federal Register on 6 October 2026. Comments are due by 7 December 2026. Until the Commission adopts a final rule, advisers remain under current rule 206(4)-2, and the final text may differ from the proposal on every point discussed here.

Does the SEC proposal count a tokenized private fund interest as a crypto asset?

If its ownership record sits on a blockchain, yes. Proposed rule 223-1(d)(3) defines a crypto asset as any digital representation of value recorded on a cryptographically secured distributed ledger. The release says this includes tokenized securities where the record of ownership is maintained in whole or in part on or through one or more crypto networks. A fund interest with a purely off-chain register and no token is outside that definition.

Can a tokenized security qualify for the privately offered securities exception?

The SEC has not decided. Request for comment 3 says a crypto asset would not meet the exception if, for example, its ownership is not recorded only on the books of the issuer or its transfer agent in the client's name, or if it can be transferred without the issuer's prior consent. It then asks commenters whether any crypto asset could qualify and what features would make it qualify.

What does an adviser have to do if it holds the keys to a tokenized fund interest?

Under proposed rule 223-1(b)(7), holding any portion of a client crypto asset's private keys is self-custody. The adviser must determine in writing, before taking custody and at least quarterly, that no qualified custodian will hold the asset. It also needs joint authorization of transfers by two or more designated persons including a management person, one address per client, cybersecurity assessments and an annual internal control report.

Do registered funds get a privately offered securities exception?

No. The release states that no similar provision exists under the Investment Company Act or its rules, so a registered fund must keep privately offered securities with a permitted custodian. Requests for comment 206 and 207 ask whether an approach like the Advisers Act exception should be made available to regulated funds and what extra safeguards it would need.

Ready to get started?

Join others who are already using our platform.