Who Must Find a Lost Holder of a Tokenized Security?
SEC Rule 17Ad-17 requires recordkeeping transfer agents and broker-dealers to run two database searches for a lost securityholder, and requires paying agents to notify an unresponsive payee. Both triggers assume paper: returned mail and uncashed checks. A tokenized register that emails notices and pays to wallets can lose a holder without tripping either one.
TL;DR — Key Takeaways
- ✓Current rule: A holder is lost when mail sent to the address on file comes back undeliverable and no new address arrives. The transfer agent or broker-dealer must then run two free database searches, the first within 3 to 12 months.
- ✓Paying agents: An unresponsive payee has not negotiated a check within 6 months (180 days) or before the next check. At least one written notice is due within 7 months (210 days). Amounts under $25 are exempt.
- ✓Tokenized gap: Email notices rarely come back as returned mail, and wallet distributions are never negotiated. A tokenized register can hold an unreachable holder for years without the rule ever starting a search. This is our analysis, not an SEC statement.
- ✓Proposal: Release 34-106246 (September 1, 2026) would add an inactive securityholder after 18 months without account activity, require two notices, and cover rejected electronic payments. Comments close November 3, 2026.

What does Rule 17Ad-17 require when a holder is lost?
It requires two database searches for the holder's correct address, at no charge to the holder: the first between 3 and 12 months after the holder becomes lost, the second between 6 and 12 months after the first search.
The duty falls on every recordkeeping transfer agent whose master securityholder file includes lost securityholders, and on every broker-dealer with customer security accounts that include them. The rule, 17 CFR 240.17Ad-17, dates from 1997. The SEC's 2026 releases write it as Rule 17ad-17; the eCFR still uses the older capitalisation. The obligation is one of “reasonable care to ascertain the correct addresses” of lost holders, and the two searches are the minimum the rule specifies.
A holder becomes lost when two things are true. First, an item of correspondence sent to the address in the master securityholder file came back as undeliverable. Second, the firm has received no information about a new address. If the firm re-sends the item within one month, it may date the holder's lost status from the day the re-sent item comes back.
The searches must use at least one information database service. The rule defines that as an automated service with addresses for the entire United States, names for at least 50% of the US adult population, an index by taxpayer identification number (TIN) or name, and updates at least four times a year, or any service that produces comparable results. The firm searches by TIN, or by name if a TIN search is not reasonably likely to work. It may not use a search method that charges the holder before both required searches are done.
Three cases are exempt: the firm has documentation that the holder has died; the account is worth less than $25, counting dividends, interest, other payments due and securities owned; or the holder is not a natural person. The last exemption matters for tokenized products. Many of them are sold to funds, companies and trusts, and those holders fall outside the search duty.
“Such database searches must be conducted without charge to a lost securityholder and with the following frequency: (i) Between three and twelve months of such securityholder becoming a lost securityholder; and (ii) Between six and twelve months after the first search for such lost securityholder by the transfer agent, broker, or dealer.”
17 CFR 240.17Ad-17(a)(1), eCFR
Who else carries a duty under the rule?
Paying agents do. Any issuer, transfer agent, broker-dealer, investment adviser, indenture trustee or custodian that distributes issuer payments to holders must send at least one written notice to an unresponsive payee within 7 months (210 days).
A holder becomes an unresponsive payee when a check is not negotiated before the earlier of two dates: the next regularly scheduled check, or 6 months (180 days) after the check was sent. The holder stops being an unresponsive payee once the check is negotiated. Checks under $25 are excluded. A paying agent need not send the notice if the holder already counts as a lost securityholder. The definition of paying agent is broad. In a tokenized fund, the issuer, the administrator distributing yield and the transfer agent could each fall within it, depending on who receives the issuer's payments and passes them on.
| Element | Lost securityholder | Unresponsive payee |
|---|---|---|
| Who is obliged | Recordkeeping transfer agents; broker-dealers with customer security accounts | Any paying agent, including issuers, advisers, trustees and custodians |
| Trigger | Correspondence returned undeliverable, no new address received | Check not negotiated by the next check or 180 days |
| Required action | Two database searches, free to the holder | At least one written notice |
| Deadline | 3 to 12 months after lost; second search 6 to 12 months later | 210 days after the check was sent |
| Exemptions | Documented death; account under $25; not a natural person | Check under $25; holder already a lost securityholder |
| Records | Written procedures describing the methodology, kept under Rule 17Ad-7(i) | |
Paragraph (d) is where most examination findings would start. Every obliged firm must keep records that demonstrate compliance, including written procedures that describe its methodology. A firm that cannot show when each holder became lost, and when each search ran, cannot show compliance with the timing windows. Lost holder procedures sit alongside the other custody-side duties covered in the institutional RWA custody compliance guide, and they belong in the same operating manual.
Why can a tokenized register miss both triggers?
Both triggers are paper events. A bounced email is not clearly an item “returned as undeliverable” to the address on file, and a stablecoin distribution credited to a wallet is never “negotiated” like a check. This section is our analysis.
Start with what the issuer knows. A lost securityholder is not someone who lost a private key. A key-loss case is the reverse: the issuer knows who the holder is, and the holder cannot reach the position. Rule 17Ad-17 covers a holder the issuer cannot reach, while the register still shows the position.
Now take an illustrative tokenized note, not a real product. Investors onboard with a name, a TIN, an email address and a whitelisted wallet. Statements go by email. Monthly coupons are paid in a stablecoin to each wallet. One investor changes jobs, the work email is closed, and the investor stops checking the wallet. Here is what happens to each trigger:
- Lost securityholder: the email server may return a bounce, or may accept and discard the message. The current definition refers to correspondence sent to the address in the master securityholder file. If the file holds only a postal address that nobody writes to, no item ever comes back.
- Unresponsive payee: each coupon lands in the wallet. There is no check, so there is nothing to negotiate, and the 180-day clock never starts.
- Result: the register shows a live holder receiving payments, while nobody has heard from that person in years. When a state dormancy period runs, the position may be reported as unclaimed without a single search having run.
The SEC has noticed the same pattern from the other side. Its 2026 proposal says the current rule requires a search for the correct physical mailing address. It also asks, in comment request 120, how firms comply when they hold no physical mailing address for a holder at all.
What would the September 2026 proposal change?
Release 34-106246 would add an “inactive securityholder”, defined as no observed account activity for 18 months, and require at least two written notices. It would also cover electronic payments that are rejected and returned as undeliverable.
The SEC proposed the change on September 1, 2026 as part of a wider rewrite of the transfer agent rules, covered in our review of the SEC transfer agent rule proposal. It was published in the Federal Register on September 4, 2026, File No. S7-2026-30, and comments close November 3, 2026. Nothing below is in force.
The proposal makes four changes to the rule:
- Inactive securityholders: recordkeeping transfer agents and broker-dealers would send at least two written notices. The first is due within 6 months of the holder becoming inactive, the second within 6 months of the first. Each must say that the account has been inactive, that some jurisdictions may treat inactive accounts as unclaimed property, and how the holder can show activity. Notices may go by any method reasonably expected to reach the holder.
- Lost securityholder definition: the phrase tying returned correspondence to the address in the master securityholder file would be deleted. Any undeliverable item would count, including one sent to an email address held elsewhere.
- Unresponsive payees: an electronic payment rejected and returned as undeliverable would trigger the notice, alongside an uncashed check. Status would end once the holder gives new payment instructions that result in a successful transfer.
- Record retention: the records cross-reference would move from Rule 17ad-7(i) to Rule 17ad-7(a), part of a single retention period the proposal sets for most transfer agent records.
“Is the Commission's proposed description of account activity appropriate? What types of account activity should be sufficient to prevent a securityholder from being deemed inactive? Does the description adequately capture activity in tokenized securities?”
SEC Release 34-106246, section III.K.4, comment request 116
The proposed list of account activity includes logging in, email access, electronic communication about the account, a transaction in the account where the assets are held, read receipts, and any other action showing the holder is reachable and engaged. Whether a transfer from a whitelisted wallet, or a signed message from it, counts as a transaction “in the account” is not stated. Request 116 shows the SEC has not settled it either. A coupon arriving in the wallet is activity by the paying agent, not by the holder, so on our reading it would not reset the 18-month clock.
How does the rule interact with state escheatment?
It does not override it. Rule 17Ad-17(c)(5) states that the paying agent notice duty has no effect on state escheatment laws, and the 2026 release says some states are cutting dormancy periods for securities from five years to three.
The release describes two dormancy triggers used by most states. One is the “Returned Post Office” standard: US mail returned as undeliverable. The other runs from the last contact or activity by the owner, whether or not mail is delivered. The SEC names New York, Arizona, South Dakota, Maryland and New Hampshire as states with three-year dormancy periods for securities. It also warns that states using an inactivity standard could require a firm to escheat assets “even though there is no lost securityholder as defined by the rule.”
“Although securityholders who have had their securities escheated may be able to petition the state to reclaim their property, states generally indemnify holders only for the value of the securities at the time of escheatment, not for subsequent market appreciation, dividend streams, or tax consequences.”
SEC Release 34-106246, section III.K.1, Background
For a tokenized security this creates a timing risk that the federal rule does not cover. A state inactivity clock can run on a holder who never became lost under the federal definition. The state rules themselves differ by jurisdiction and change often, so the dormancy period that applies to a given holder is a question for counsel, not something to hard-code from a summary.
What should a tokenized issuer set up now?
Keep each holder's TIN, legal name and postal address linked to every wallet, and add an internal inactivity trigger that does not depend on returned mail. These are our recommendations, not rule requirements.
A database search runs on a TIN or a name. A wallet address finds nobody in a commercial address database. If the identity record and the wallet record drift apart, the transfer agent can run the search but has nothing to search with. The practical controls follow from that:
- Identity link: one record per holder that ties the TIN, name, postal address, email and every whitelisted wallet together, kept by the party that keeps the master securityholder file.
- Returned-item log: treat bounced email and failed postal mail as dated events in the holder record. That date starts the 3-to-12-month window under the current rule.
- Internal inactivity trigger (editorial suggestion): flag a holder after a set period with no holder-initiated wallet transaction, no login and no reply to email. The 18-month figure in the proposal is a reasonable reference point, but it is not law yet.
- Payment exceptions: record any distribution that fails, is returned or cannot be sent because a wallet is frozen. Under the proposal, these would count as rejected electronic payments.
- Written procedures: paragraph (d) already requires them. They should say which events start each clock for a tokenized holder, since the rule text does not.
A protocol-level compliance layer can keep the on-chain side of this record, such as which identity a wallet maps to and when it last initiated a transfer. The search, the notices and the escheatment decision remain the transfer agent's and issuer's obligations. Firms with a view on how wallet activity should count have until November 3, 2026 to file comments on File No. S7-2026-30.
Sources: 17 CFR 240.17Ad-17, Lost securityholders and unresponsive payees (eCFR); SEC Release 34-106246, Transfer Agent Rules (proposed); SEC fact sheet on Release 34-106246; Federal Register, Transfer Agent Rules, document 2026-18190. Sources checked October 30, 2026. The tokenized note example, the analysis of how the triggers apply to wallets, and the recommended controls are editorial analysis, not SEC statements.
Frequently Asked Questions
Is a holder who lost their private key a lost securityholder under Rule 17Ad-17?
No. The rule defines a lost securityholder by correspondence returned as undeliverable with no new address received. A holder who lost a key is usually still reachable: the transfer agent knows who they are and can contact them. That is a wallet recovery problem. Rule 17Ad-17 covers the opposite case, where the record shows a position but the holder cannot be reached.
When must the two lost securityholder searches happen?
The first search must run between three and twelve months after the holder becomes lost. The second must run between six and twelve months after the first search. Both must use at least one information database service, search by taxpayer identification number where that is likely to work, and cost the holder nothing. Deceased holders, accounts under $25 and holders that are not natural people are exempt.
Does a stablecoin distribution sent to a wallet count as a negotiated check?
The current rule does not say. Its unresponsive payee test turns on a check not being negotiated within 6 months or before the next scheduled check. An on-chain transfer has no negotiation step. The September 2026 proposal would add a second test for an electronic payment rejected and returned as undeliverable. Whether a credited wallet transfer is ever rejected is a question the text leaves open.
Does Rule 17Ad-17 stop a state from escheating tokenized securities?
No. Paragraph (c)(5) states that the paying agent notice requirement has no effect on state escheatment laws, and the rule creates no exemption from them. In the 2026 proposal the SEC says state laws are moving toward inactivity standards and shorter dormancy periods, and that some states use three years for securities. State law, not the SEC rule, decides when property escheats.
Related Articles
How Should an RWA Issuer Recover a Lost Wallet?
ERC-3643 wallet recovery is a privileged process for restoring a holding when an investor loses access to a private key. Its operational purpose is continuity of the investor position, not creation of a second entitlement. Issuers need to reconcile the identity record, the token balance and any services that still refer to the old address.
Who Is the Transfer Agent for a Tokenized Security?
Legal ownership of a security lives in the master securityholder file, not in a wallet balance. SEC staff has confirmed a registered transfer agent may keep that file on a blockchain — but Section 17A registration, three-business-day turnaround under Rule 17Ad-2, and five-business-day posting under Rule 17Ad-10 still apply.