Platform Overview

The workflow below reflects the proposed implementation model developed with Olde Monmouth Stock Transfer Co. as Governa's first transfer-agent ("TA") partner. It is organized as a sequence of ten operational stages, each with defined controls and an associated audit trail.

Architecture at a Glance

Authorization & Control Chain

• Issuer authorizes tokenization of a specific class of security
• Transfer Agent (e.g., Olde Monmouth) controls issuance and remains the statutory recordkeeper
• Governa deploys and operates the issuer-authorized smart contract as technology infrastructure
• CUSIP ↔ Security Master Record ↔ Smart Contract Address forms an immutable association
• Tokens mint into a TA-controlled treasury wallet, never directly to investors
• Distribution to shareholders requires TA approval, multi-signature sign-off, and compliance checks
• The DLT ledger and the TA's shareholder database together form an integrated Master Securityholder File

Step 1 — Issuer Onboarding

The transfer agent creates the issuer record inside its white-labeled Governa interface. The record contains conventional securities data: legal issuer name, security/class, CUSIP, authorized and issued/outstanding shares, DTC/DRS information where applicable, restricted or unrestricted status, the applicable exemption or registration statement, and any legends or transfer restrictions. Governa does not originate this data independently — it structures and stores the transfer agent's existing records.

Step 2 — Smart Contract Creation

From the issuer record, the transfer agent authorizes deployment of a smart contract. Governa generates the contract parameters directly from the security record, forming a chain of identifiers: CUSIP → Issuer → Class of Security → Smart Contract Address → Blockchain.

The contract address becomes an additional identifier associated with that class of security. Whether that association constitutes the same legally recognized security across traditional and blockchain records is treated as an open question for SEC staff, not a settled legal conclusion.

Step 3 — Token Creation / Minting

The transfer agent — not Governa acting independently — authorizes token issuance. The number of tokens minted reconciles against the shares the transfer agent is authorized to represent on-chain, typically on a 1:1 basis with outstanding shares. Governa is designed to prevent minting beyond the authorized tokenized position and to maintain an audit trail capturing who authorized the mint, when it occurred, the transaction hash, and the corresponding shareholder-ledger adjustment.

Step 4 — Master / Treasury Wallet

Each issuer or security is assigned a controlled issuance/treasury wallet held by the transfer agent. New tokens mint into this controlled environment rather than directly into investor wallets. From there, the transfer agent authorizes distribution to approved shareholder wallets, producing a clean authorization chain: Issuer authorization → Transfer agent authorization → Mint → Treasury → Verified shareholder wallet.

Step 5 — Investor Wallet Integration

Each shareholder record links a shareholder ID, wallet address, number of shares/tokens, applicable restrictions, acquisition date, and KYC/AML status. Personally identifiable information remains off-chain. Wallet address, asset balance, ownership percentage, share count, purchase date, and transaction ID can reside on-chain, while names, addresses, Social Security or tax ID numbers, and other private information remain within the transfer agent's proprietary system.

Step 6 — Whitelisting and Transfer Restrictions

Before a wallet can receive a security token, it must be approved. The smart contract can enforce restrictions such as Reg D holding periods, affiliate/control restrictions, accredited-investor requirements, jurisdiction restrictions, stop-transfer instructions, frozen wallets, and lost/stolen wallet procedures. This gives the transfer agent control over whether a transaction is legally permitted before it completes.

Step 7 — Multi-Signature Controls

Sensitive administrative functions require multi-party authorization — for example, a 2-of-3 structure involving the transfer agent, the issuer, and a designated compliance/administrator key. Multi-signature approval is proposed for minting, burning, forced transfers, freezing or unfreezing wallets, changing transfer rules, replacing lost wallets, and changing smart-contract administrative permissions.

Step 8 — Master Securityholder File Synchronization

Every token movement corresponds to the legally recognized shareholder record. Governa is designed so that the blockchain ledger and the transfer agent's shareholder database together form an integrated Master Securityholder File architecture — provided recordkeeping, safeguarding, reporting, and examination obligations continue to be met.

Step 9 — Corporate Actions and Governance

Beyond issuance and transfer, the transfer agent can administer record dates, shareholder voting, proxies and consents, dividends, splits and reverse splits, tender or exchange events, lockups, conversions, redemptions, distributions, and other corporate actions through the platform, with the token and shareholder record remaining synchronized throughout each event.

Step 10 — Audit and Compliance Console

Every administrative action generates a permanent audit record capturing who initiated it, who approved it, date and time, shareholder account, wallet, transaction hash, old balance, new balance, restriction status, and reason code. The transfer agent can produce human-readable records on request.