On-Chain Transfer Agents: How Tokenized Share Registries Work

Quick answer: An on-chain transfer agent performs the same legal function as a traditional stock transfer agent — maintaining the official record of who owns what — except the record of ownership lives on a blockchain instead of (or alongside) a private database. In the United States, this is only lawful because a handful of states amended their corporate codes to recognize distributed ledgers as valid stock ledgers, and because the entity doing the recording still has to register with the SEC under Section 17A and follow Rule 17Ad’s turnaround-time and recordkeeping standards. Most live programs today — including BlackRock’s BUIDL fund and Franklin Templeton’s OnChain fund — use a “hybrid” structure where a registered transfer agent keeps the legally authoritative books off-chain and mirrors ownership onto a permissioned token that can move between wallets in seconds instead of days.

Why On-Chain Transfer Agents Are Having a Moment

For most of the last century, proving you owned a share of stock meant trusting a paper trail: a certificate, then a broker’s internal ledger, then a central depository’s book-entry record, then a transfer agent reconciling all of it in the background. That chain of custody works, but it is slow by design. Ownership changes typically move through several intermediaries before anyone’s balance actually updates, and each hop adds a day or two of settlement risk and a fee.

Two things changed that calculus. First, several states rewrote their corporate statutes to say, in plain terms, that a company’s official stock ledger can be a blockchain. Delaware did this in 2017 by amending Section 224 of its General Corporation Law to permit “one or more distributed electronic networks or databases” as an acceptable form of stock ledger, provided the system can produce an accurate list of holders on demand. Nevada and Wyoming followed with similar language. Second, large regulated asset managers started actually using that permission at scale rather than treating it as a legal curiosity.

Franklin Templeton was first to market in a meaningful way, launching its OnChain U.S. Government Money Fund in 2021 with share ownership recorded on the Stellar network (and later mirrored to Polygon), administered through its own registered transfer agent affiliate. BlackRock followed in March 2024 with the USD Institutional Digital Liquidity Fund — known by its ticker, BUIDL — using Securitize Markets LLC as the fund’s registered transfer agent and Ethereum as the primary settlement rail. BUIDL crossed roughly half a billion dollars in assets within two months of launch and had grown past several billion by 2025, expanding across additional chains including Solana, Avalanche, Aptos, Polygon, Arbitrum, and OP Mainnet through bridge-based mirroring. Those two funds turned “on-chain transfer agent” from a legal thought experiment into an operating business line that dozens of issuers, custodians, and fintech platforms are now trying to replicate.

None of this replaced the underlying regulatory framework. It sits on top of it. A transfer agent handling tokenized shares still has to file Form TA-1, still answers to the SEC’s Division of Trading and Markets, and still has to hit the same turnaround clocks that have governed paper transfers since the 1970s. What changed is the plumbing underneath the compliance obligations, not the obligations themselves.

What a Transfer Agent Actually Does — and Where Blockchain Fits In

Under Section 17A of the Securities Exchange Act, a transfer agent performs any of four core functions on behalf of an issuer: countersigning and monitoring the issuance of securities, registering transfers of ownership, exchanging or converting securities, and — often the most operationally heavy job — maintaining the master record of who holds what and paying dividends or distributions against that record. Anyone performing these functions for a security registered under the Exchange Act generally has to register with the SEC as a transfer agent, regardless of whether the ledger they keep is a SQL database, a spreadsheet, or a smart contract.

That last clause is the whole story of on-chain transfer agency. A blockchain is, mechanically, just another way to store a ledger of balances and an append-only history of changes to those balances. What makes it interesting for this specific job is that the ledger is shared, cryptographically tamper-evident, and — if the token is built correctly — able to enforce transfer rules automatically rather than relying entirely on a back-office team to catch violations after the fact.

In practice, an on-chain transfer agent still runs a conventional back office. It answers shareholder calls, processes dividend elections, handles escheatment for abandoned property, and files the same annual reports as a paper-based transfer agent. The difference shows up in three places: how the golden record is defined, how transfer restrictions are enforced, and how fast a change in ownership actually settles.

Two Competing Models: Mirrored Ledger vs. Native On-Chain Register

Almost every program running today falls into one of two architectures, and the distinction matters far more than most marketing material lets on.

The mirrored (hybrid) model

In the mirrored model, the transfer agent’s traditional internal database remains the legally authoritative record — the one that would win in a courtroom dispute over who owns what. The blockchain token is a synchronized copy that the transfer agent updates every time its internal ledger changes, and that it also monitors for on-chain transfers so it can update the internal ledger to match. This is how Franklin Templeton’s fund and, largely, how BlackRock’s BUIDL fund are structured: Securitize’s transfer agent entity keeps books of record, and the Ethereum-based token is the operational interface investors and custodians actually interact with day to day. If the chain and the internal database ever disagree, the transfer agent’s books control, and a reconciliation process corrects the token supply or balances.

The native on-chain register model

In the native model, there is no separate “real” ledger sitting behind the token — the distributed ledger itself is the official stock ledger, as contemplated by Delaware’s Section 224 amendment. A handful of smaller issuers and a few crypto-native cap-table platforms have gone this route for private company equity, since it avoids the reconciliation overhead of running two ledgers in parallel. It is a harder model to run for a large, actively traded fund, because it requires the transfer agent’s entire compliance, audit, and disaster-recovery apparatus to be built around blockchain data from day one rather than bolted onto an existing system.

Most large, regulated issuers choose the mirrored model precisely because it lets them keep the compliance infrastructure they already have and layer a faster settlement rail on top, accepting the operational cost of running two synchronized ledgers as the price of not having to re-architect everything else.

Permissioned Tokens and the Whitelist Problem

A freely transferable token is a liability for a transfer agent handling registered securities, because federal securities law does not let just anyone buy or hold certain instruments — accredited-investor limits, Regulation D holding periods, OFAC sanctions screening, and fund-specific eligibility rules (minimum investment size, jurisdiction restrictions) all have to be enforced somewhere. If the token can move to any wallet with no checks, the transfer agent has effectively lost control of its own register.

The fix is a permissioned token standard rather than a plain transferable one. Two standards dominate this space in practice: ERC-1400, an early security-token framework built around “partitions” that can carry different transfer restrictions, and ERC-3643 (also called the T-REX protocol), which pairs each token with an on-chain identity registry so a transfer only succeeds if both the sending and receiving wallet have already passed a compliance check baked into the smart contract itself. Under either standard, a transfer that would otherwise violate a rule simply reverts — it does not get flagged after settlement for someone to unwind later, it never settles at all.

This is the single biggest practical difference between an on-chain transfer agent and a traditional one. A paper-based transfer agent typically catches an ineligible transfer during a post-trade review, sometimes days after the fact, and then has to reverse it. A well-built permissioned token catches it at the moment of the attempted transaction and blocks it before it ever touches the ledger. That said, this only works if the whitelist itself is kept current — a wallet that passed KYC eighteen months ago but whose owner has since been added to a sanctions list is still, mechanically, a “whitelisted” wallet until someone updates the registry.

Regulatory Scaffolding: Rule 17Ad, Form TA-1, and State Corporate Law

Registering as a transfer agent starts with Form TA-1, filed with the SEC (or, for bank-affiliated transfer agents, an appropriate banking regulator), which discloses the applicant’s ownership, financial condition, and the securities it intends to service. Registration alone does not relax any of the operating rules that follow.

Rule 17Ad-2 sets turnaround-time standards for routine items — historically requiring that 95% of routine transfers, and comparable percentages of dividend or distribution items, be processed within three business days of receipt, with items processed outside that window classified and reported as aged. A blockchain settling a transfer in twelve seconds obviously clears that bar with room to spare, but it does not eliminate the reporting obligation; the transfer agent still has to be able to demonstrate its turnaround statistics to examiners on request.

Rule 17Ad-7 governs recordkeeping — how long records must be kept and in what format — and here the blockchain’s immutability is genuinely useful, since an on-chain history of transfers is, by construction, a tamper-evident audit trail that satisfies the spirit of the rule more completely than a mutable database ever could. Rule 17Ad-17 requires transfer agents to run “lost securityholder” searches using database matching to locate holders who have gone unresponsive, an obligation that applies just as much to a tokenized fund as to a paper one, since a wallet address alone tells a transfer agent nothing about whether the underlying beneficial owner can still be reached.

Layered on top of all this is the SEC’s 2022 proposal to expand the formal definition of “transfer agent” to explicitly capture entities performing these functions for crypto asset securities, and to require transfer agents holding customer assets to meet new safeguarding standards. That proposal has moved slowly and, as of this writing, has not been finalized, which means the current legal basis for on-chain transfer agency rests on a combination of existing Section 17A obligations, no-action-style interpretive positions, and the state corporate-law amendments described earlier rather than on a single, purpose-built federal rule.

A Worked Example: Moving 40,000 Tokenized Fund Shares Between Custodians

Numbers make the mechanics concrete. Say an institutional investor holds 250,000 shares of a tokenized government money-market fund with a stable $1.00 net asset value — a $250,000 position — custodied through Prime Broker A’s wallet infrastructure. The investor is switching a portion of that position to Prime Broker B and instructs a transfer of 40,000 shares, worth $40,000.

Here is roughly how that instruction moves through a mirrored-model on-chain transfer agent:

Step 1 — Instruction and identity check. The investor or its custodian submits a transfer instruction to the transfer agent, naming the destination wallet controlled by Prime Broker B. If that wallet has never received this fund’s token before, the transfer agent (or its delegated identity-verification partner) runs a KYC and sanctions check on the underlying beneficial owner behind the wallet — typically a one- to three-business-day process the first time, and effectively instantaneous on every transfer after that, since the wallet is now permanently registered in the token’s identity registry.

Step 2 — On-chain execution. Once the destination wallet is whitelisted, the transfer agent (or the investor directly, depending on the platform) submits the token transfer to the smart contract. The contract’s compliance module checks that both wallets are eligible, that no lock-up applies, and that the transfer size does not breach any holding limit, then moves the tokens. On Ethereum this typically confirms within 12 to 15 seconds; on a faster settlement chain such as Solana or Polygon, confirmation can land in one to two seconds.

Step 3 — Off-chain reconciliation. Because the transfer agent’s internal database — not the chain — is the legally authoritative record in this model, an automated reconciliation job picks up the on-chain event and updates the master shareholder register, typically within the same business day and no later than the next overnight batch cycle.

Step 4 — Cost comparison. The on-chain leg of this transfer costs the network gas fee, generally somewhere between $0.50 and $5 depending on network congestion at the time. Compare that to a comparable legacy transfer: a Direct Registration System (book-entry) transfer through a traditional transfer agent commonly runs $15 to $75 in processing fees, and if the investor had instead been holding a physical certificate that needed replacement because it was lost, the surety bond premium alone — typically 2% to 6% of the position’s value to indemnify the issuer against a duplicate claim — would have added roughly $800 to $2,400 in cost on a $40,000 position, before any reissuance fee.

The settlement-time gap is the more dramatic number. A physical certificate transfer can take one to two weeks door to door once notarization and mailing are factored in. A book-entry transfer processed by a traditional transfer agent generally clears within the Rule 17Ad-2 turnaround window of up to three business days. A broker-to-broker transfer settled through the Depository Trust Company, since the U.S. equities market moved to a T+1 cycle in May 2024, generally finalizes one business day after trade date. The on-chain leg above settled in under fifteen seconds.

Traditional vs. Hybrid vs. Native On-Chain Transfer Agents at a Glance

Common Mistakes Issuers and Investors Make

Treating a compliant token as a freely tradable one. A permissioned security token is not a bearer instrument. Sending it to an unwhitelisted wallet, whether by mistake or to test something on a personal address, will simply cause the transaction to revert — and a surprising number of first-time institutional users burn hours troubleshooting a “broken” transfer that was never going to succeed by design.

Assuming on-chain settlement removes the need for reconciliation. In a mirrored model, the token and the internal ledger can drift out of sync if a reconciliation job fails silently, a bridge to a secondary chain lags, or a manual off-chain correction is entered without a matching on-chain adjustment. Skipping daily reconciliation checks because “the blockchain is the source of truth” is a category error in a hybrid architecture where it explicitly is not.

Confusing a whitelisted wallet with a verified person. Identity registries check the wallet at the moment it is onboarded. They do not automatically re-check the underlying owner against updated sanctions lists, deceased-holder databases, or changed accreditation status unless someone builds a periodic re-screening process. A stale whitelist is a compliance gap that looks, from the outside, exactly like a healthy one.

Ignoring bridge and cross-chain risk. Once a fund’s token exists on more than one network — as BUIDL’s does — an investor moving value between chains is relying on a bridge, not just the transfer agent’s smart contract. Bridges have historically been one of the more exploited pieces of crypto infrastructure, and a transfer agent’s compliance controls on the origin chain do not automatically extend to how a bridge represents that balance on the destination chain.

Overlooking the state corporate-law question. Some issuers build a technically excellent tokenized register without first confirming that the state where the company is incorporated actually recognizes a blockchain-based stock ledger as authoritative. Absent an amendment like Delaware’s Section 224, a “native” on-chain register may be an operationally real but legally unrecognized ledger — which is precisely why most large programs default to the mirrored model instead.

Underestimating the lost-holder obligation. A wallet address that stops transacting is not the same thing as a “found” holder. Transfer agents still have to run the database-matching searches required under Rule 17Ad-17, and a beneficial owner who changes custodians, dies, or simply goes inactive on-chain can trigger the same escheatment timeline as a shareholder who stopped opening paper mail decades ago.

Practical Checklist Before Launching or Using an On-Chain Transfer Agent

• Confirm whether the issuer’s state of incorporation recognizes distributed ledgers as valid stock ledgers, or whether the program will rely on a mirrored off-chain record instead.
• Verify the transfer agent’s Form TA-1 registration status and confirm which entity — not just which platform — is the SEC-registered transfer agent of record.
• Choose a permissioned token standard (ERC-3643, ERC-1400, or an equivalent) with an on-chain identity registry rather than a freely transferable token.
• Document the reconciliation cadence between the on-chain ledger and any off-chain books of record, and who is accountable when the two disagree.
• Build a periodic re-screening process for whitelisted wallets, not just a one-time onboarding check.
• Map every chain the token can live on, and identify the bridge or mirroring mechanism used to move it between them.
• Confirm the transfer agent’s turnaround-time reporting under Rule 17Ad-2 covers on-chain transfers, not just legacy book-entry activity.
• Review the lost-securityholder search process under Rule 17Ad-17 as applied to wallet-based holders.
• Obtain independent smart-contract and compliance-module audit reports before relying on automated transfer restrictions.
• Confirm custody and insurance arrangements for the private keys or institutional custody solution controlling any wallet holding client assets.

Key Takeaways

• An on-chain transfer agent performs the same Section 17A functions as any registered transfer agent; the blockchain changes how fast transfers settle and how restrictions are enforced, not the underlying legal obligations.
• Most large, live programs — including BlackRock’s BUIDL and Franklin Templeton’s OnChain fund — use a hybrid model where an off-chain database stays legally authoritative and the token is a fast-settling mirror.
• A native on-chain register, where the blockchain itself is the official stock ledger, is only valid where state corporate law says so — Delaware’s Section 224 amendment being the clearest example.
• Permissioned token standards like ERC-3643 enforce KYC and eligibility rules at the moment of transfer, blocking non-compliant transactions before they settle rather than catching them afterward.
• On-chain settlement can cut transfer time from days to seconds and transfer cost from tens of dollars to a few dollars in gas fees, but it does not remove reconciliation, re-screening, or lost-holder obligations.

Frequently Asked Questions

What is an on-chain transfer agent?

An on-chain transfer agent is a SEC-registered transfer agent that records securities ownership using a blockchain, either as a fast-settling mirror of a legally authoritative off-chain database (the hybrid model) or, where state corporate law permits it, as the official stock ledger itself. It still performs the same core functions as any transfer agent — issuing, registering transfers, and maintaining holder records — just on different underlying infrastructure.

Is a blockchain record of stock ownership legally binding?

It can be, but only where the issuer’s state of incorporation has amended its corporate code to say so. Delaware did this in 2017 through Section 224 of its General Corporation Law, and Nevada and Wyoming have similar provisions. Absent that kind of statutory recognition, a blockchain token is typically treated as a representation of ownership rather than the ownership record itself, which is why most large issuers keep an off-chain database as the legally controlling ledger.

How do KYC and AML checks work when shares are tokenized?

Compliant security tokens are usually built on a permissioned standard, such as ERC-3643, that pairs every wallet with an on-chain identity record created after a KYC and sanctions check. A transfer only executes if both the sending and receiving wallet are already registered as eligible; if either one is not, the smart contract blocks the transaction automatically rather than letting it settle and flagging it for review afterward.

What happens if an on-chain transfer fails a whitelist check?

The transaction simply reverts — it never settles, and no shares or tokens change hands. The sender typically still pays the network gas fee for the attempted transaction even though it failed, since gas covers the computation the network performed to check eligibility and reject the transfer, not the successful completion of a transfer.

Are on-chain transfer agents regulated by the SEC?

Yes. Any entity performing transfer agent functions — issuing, registering transfers, or maintaining ownership records — for a security registered under the Exchange Act generally has to register with the SEC under Section 17A, file Form TA-1, and comply with the Rule 17Ad series covering turnaround times, recordkeeping, and lost-securityholder searches, regardless of whether its ledger runs on a blockchain or a conventional database. The SEC proposed in 2022 to explicitly extend and clarify these obligations for crypto asset securities, though that proposal remained unfinalized as of this writing.

References

• U.S. Securities and Exchange Act of 1934, Section 17A — registration and regulation of transfer agents.
• SEC Rule 17Ad-2 (turnaround times), Rule 17Ad-7 (recordkeeping), and Rule 17Ad-17 (lost securityholders).
• Delaware General Corporation Law, Section 224, as amended 2017 — distributed ledger stock ledgers.
• SEC proposed rule, “Amendments to the National Market System Plan Governing the Consolidated Audit Trail” and related 2022 transfer agent modernization proposal.
• Franklin Templeton OnChain U.S. Government Money Fund prospectus disclosures.
• BlackRock USD Institutional Digital Liquidity Fund (BUIDL) offering documents and Securitize Markets LLC transfer agent disclosures.
• For a broader primer on how tokenized ownership records interact with real-world assets generally, see our real-world asset tokenization guide.