Issuance
5 min
What a transfer agent does when the register is a contract
Tokenizing a security does not remove the transfer agent. It changes the job: less data entry, more rule-writing, and a signature on every rule.

A transfer agent has always done three things: keep the register of who holds a security, check that each transfer is allowed, and pay holders what they are owed. None of that goes away when the register becomes a token contract. What goes away is the gap between a transfer happening and the register knowing about it.
The work moves before the closing
On a paper register, most of the work happened after a trade: checking documents, updating lines, answering the issuer’s questions. On a contract, the same checks run inside every transfer, so the work moves to before the first holder. We read the offering documents, write each restriction as a compliance module, and sign a mapping that shows the clause and the parameter side by side. For Halden Private Credit I that mapping was 31 lines long.
What stays human
Three things, and they should. Approving a verifier whose claims the contract will trust. Executing a forced transfer on a court order or a lost wallet. Deciding, with the issuer, what happens when a clause cannot be expressed as a parameter. That last one is rare, and when it happens we say so in writing before closing.
The result is a register that is right at every block, and a transfer agent whose signature is on the rules rather than on each line.

Élise Wagner
Chief Executive Officer
MORE NOTES FROM THE REGISTER


