Transfer Agent Protocol
We use Open Cap Table Format and convert it into smart contracts. The onchain cap table is the source of truth; the offchain database is its mirror.
Current Status
The protocol is live on Plume Mainnet . This documentation covers the live stack.
Who deploys what: the protocol builder ships contracts and may run a shared demo factory; a licensed transfer agent deploys their own CapTableFactory (book of business); issuers mint cap tables through a factory and become ADMIN of that table. Factory addresses are unique per deploy — see Deploy factory and the Development Guide.
Protocol Specification
The protocol has three major components.
-
Smart contracts create primary ownership records onchain first. These records are then synced with the offchain database.
-
Offchain database stores the cap table data. We’re currently using a MongoDB that stores cap table data in the Open Cap Table Format.
-
Product UI submits day-to-day writes directly from the issuer ADMIN wallet. The server API supplies reads, metadata registration, and an optional server-signed automation path. The event poller mirrors confirmed contract events into MongoDB.