Tokenized Equity Trading
Regulated tokenized stock trading on compliant exchanges — Reg D, accredited investors, transfer restrictions.
CTR (USD 10,000+)TRAVEL-RULE (USD 3,000+)ENHANCED-DUE-DILIGENCE (USD 50,000+)
Step 1 · Accredited Investor Onboarding — 506(c) VerificationPolicy-EnforcedBlockchain-Native
Opening a brokerage account with accredited-investor verification — income and net-worth documentation, SEC qualification confirmed, and the blue-sky state-level exemptions affirmed before the broker-dealer will route an order.
Investor completes Rule 506(c) accredited-investor verification through the issuer's registered transfer agent (Securitize, Vertalo, Tokeny). Unlike Rule 506(b), the (c) exemption for general solicitation requires affirmative verification, not self-certification: the transfer agent reviews two years of tax returns + a net-worth statement (excluding primary residence, >$1M), or a letter of attestation from a registered investment adviser, CPA, or attorney. Once verified, the investor's wallet is whitelisted in the issuer's ERC-3643 identity registry — the same standard BlackRock BUIDL, Franklin OnChain US Government Money Fund, and Apollo × Securitize tokenized credit funds use. L4 Account and L5 Application are lit, both above the enforcement line — the qualification and KYC record are bank-grade policy-enforced controls maintained by the transfer agent in its registered capacity under the SEC's transfer-agent rules. Builder: call `identityRegistry.isVerified(wallet)` before showing any tokenized-equity UI that would let an unverified address place an order; fetch the investor's claim set via the ONCHAINID resolver so you can gate UI to the correct tranche (accredited-only, QIB-only, qualified-purchaser-only). Verify Investor and Parallel Markets are the two production Rule 506(c) verification vendors at institutional scale. Compliance officer: satisfies C1 (identity claim — accredited status, jurisdictional eligibility, OFAC clear), C5 (licensed-intermediary gate — transfer agent registered under §17A(c), placement agent registered as broker-dealer), and C8 (operational-resilience — the transfer agent's SEC-registered role is the fiduciary anchor for the entire cap table). SEC Securities Act §4(a)(2) + Rule 506(c) govern the exemption; state blue-sky filings (NASAA Rule 506 uniform filing) are a parallel obligation that many issuers overlook. GENIUS §6 (AML/BSA) applies to the transfer agent's compliance program. Honesty marker: 'accredited investor' is a surprisingly porous category — the SEC's 2020 expansion added certain FINRA license holders and 'knowledgeable employees' of private funds, and a spousal-equivalent test; multiple tokenized-equity platforms interpret these edges differently, so an investor verified on one platform may fail verification on another.
Step 2 · Transfer Agent Pre-Approval — Rule 144 + Shareholder CapCode-EnforcedBlockchain-Native
A transfer agent reviewing a stock transfer request — verifying both parties are eligible, the transfer does not violate holding-period restrictions or an issuer lock-up, and the post-transfer shareholder count does not trip the SEC §12(g) registration threshold.
The transfer agent's compliance module pre-approves the trade. Checks in priority order: (1) both counterparties whitelisted in the ERC-3643 identity registry, (2) Rule 144 holding-period compliance (6 months for reporting-company securities, 12 months for non-reporting — the clock is tracked on-chain against the token's original acquisition event), (3) issuer lock-ups (post-IPO, post-private-placement restrictive periods — encoded in the token's transfer-restriction contract), (4) OFAC sanctions screening via the Chainalysis oracle on both addresses, (5) shareholder-count gate under SEC §12(g) — the issuer must stay under 2,000 holders of record (or 500 non-accredited) to avoid mandatory Exchange Act registration. L3 Execution and L4 Account are lit: the registry check and OFAC screen are code-enforced, the §12(g) shareholder-count check is code-enforced at the counter level, but Rule 144 holding-period exceptions (e.g., the 'tacking' rules that permit holding-period credit for pre-conversion holdings) require the transfer agent's manual policy review. Builder: the ERC-3643 `canTransfer(from, to, amount, tokenId)` hook runs at every transfer attempt; a failed pre-approval reverts with a typed error naming the failing check (Rule 144 holding, §12(g) cap, OFAC, etc.) so the front-end can show a precise error to the user and the transfer agent's dashboard can escalate manually if needed. For issuers approaching the §12(g) threshold, expose a `holderCount()` view so the front-end can warn users when they are approaching the 2,000-holder limit. Compliance officer: satisfies C1 (identity re-check at transfer time), C2 (OFAC screening on both legs), C5 (transfer agent's registered role under §17Ad-15 blocks non-compliant transfers), and C13 (market-integrity — shareholder-count tracking prevents an inadvertent crossover into a reporting-company obligation). SEC Rule 144 (§230.144), Rule 15c2-11 (broker-dealer due diligence before quoting), and Rule 15c3-5 (market-access risk controls) all apply to the intermediary side. GENIUS §6 (AML/BSA) re-fires on every pre-approval. Honesty marker: the §12(g) shareholder-count trap is the single most-overlooked risk in tokenized equity — a successful secondary-market deal that crosses 2,000 holders forces the issuer into full Exchange Act reporting (10-K, 10-Q, 8-K, proxy rules), a cost that very few private-company issuers anticipated when they tokenized; several issuers have solved this by restricting secondary-market depth, which undercuts the liquidity promise of tokenization.
Step 3 · Trade Execution — Registered ATSCode-EnforcedBlockchain-Native
Executing a stock trade on a registered ATS — the trade matches inside Reg ATS's negotiated-quote framework, the security transfers, and the payment settles atomically in a DvP analogous to the DTCC/DTC model but collapsed into a single block.
The tokenized equity trades on a registered Alternative Trading System (Securitize Markets LLC, tZERO ATS, INX.One, or Prometheum Ember ATS) operating under SEC Regulation ATS (§§242.300–303). The match produces a trade affirmation; the DvP settles atomically — security token transfers seller→buyer, USDC transfers buyer→seller, in one Ethereum block. L2 Consensus and L3 Execution lit: consensus orders the atomic swap, execution processes the paired transfers. The ERC-3643 contract's transfer-restriction module re-fires at settlement (belt-and-suspenders vs. the Step 2 pre-approval — a stale registry entry between the trade match and settlement would revert the settle call). Builder: the ATS's matching engine should query the ERC-3643 registry on both counterparties at match time AND the settlement contract should re-query at atomic-bind time, because the registry can change state in the ~12s window between match and block confirmation (expired attestation, sanctions listing). Emit a `Traded(securityId, buyer, seller, amount, price, atsId, blockNum)` event for the ATS's best-execution audit trail. For institutional flows, layer the trade over an ISDA CDM-hashed trade ticket (see S2) so the downstream regulatory reports from Step 5 have a canonical cross-reference. Compliance officer: satisfies C6 (reserve-backing on the USDC cash leg — Circle's 1:1 reserves under GENIUS §4 apply to in-transit USDC), C13 (market-integrity — ATS best-execution obligations under Reg ATS plus SEC Rule 605/606 order-routing disclosures), and C14 (investor-protection — the ATS must disclose conflicts of interest and material terms under Regulation ATS-N for NMS stocks; Reg ATS for non-NMS private securities requires the Form ATS-R filing). GENIUS §6 (AML/BSA) sanctions screening is a pre-condition; §9 (custody) applies to the transfer agent holding the custody position post-trade. Honesty marker: 'tokenized equity secondary market' exists but is thin — Securitize Markets, tZERO, and INX handle a handful of trades per day per issuer for most private-company tokens; the headline liquidity claims of tokenization do not yet match the traditional public-equity market's market-maker depth, and off-hours liquidity is especially poor. Institutional mandates that require T+0 settlement at size still prefer CCP-cleared rails where available.
Step 4 · Post-Trade Transfer Restrictions — ERC-3643 Re-CheckCode-EnforcedBlockchain-Native
The permanent-compliance obligation that makes tokenized securities genuinely different from their paper analogues — the transfer-restriction module does not go dormant after settlement; it re-fires on every attempted transfer for the life of the security.
The ERC-3643 compliance module continues to enforce transfer restrictions on every subsequent transfer attempt — whether a secondary-market sale, an OTC block trade, or a peer-to-peer wallet-to-wallet transfer outside any venue. This is the distinctive claim of tokenized equities vs. legacy DTC-held shares: the restrictions are not just documented in a prospectus and enforced by the transfer agent's manual review — they are code-enforced at the token contract level. Restrictions typically encoded: accredited-investor status (re-checked at every transfer), jurisdiction (no US persons for Reg S tranches, no China IPs for certain funds), holding period (Rule 144 clock per token ID), lock-up windows, insider blackout periods, and issuer-call rights. L3 Execution lit and code-enforced: the `canTransfer` hook reverts with a typed error when any rule is violated. Builder: for issuers that want richer restrictions than ERC-3643's out-of-box modules, extend the compliance module with custom hooks — e.g., Franklin OnChain's money-fund implementation uses a custom hook to enforce the fund's $1.00/share NAV peg during transfers, rejecting any transfer at an off-peg price. For cross-venue trades, the restriction re-check means the buyer must already be whitelisted before the trade fires — a KYC-unregistered OTC buyer cannot receive the token. Compliance officer: satisfies C5 (licensed-intermediary gate continues post-settlement), C13 (market-integrity — the on-chain enforcement of transfer restrictions is the strongest-possible implementation of SEC Rule 144A resale restrictions, Reg S foreign-person restrictions, and issuer-specific lock-ups), and C16 (programmable compliance — this is the canonical example of code-enforced ongoing obligations). For issuers operating under Rule 144A, the permanent-whitelist enforcement is arguably a stronger compliance posture than the traditional paper-share model, which relies on CEDE & Co.'s nominee structure and broker-dealer affirmations. Honesty marker: the strength of the transfer-restriction model depends entirely on the quality of the identity claims — a compromised identity provider can mint fake accredited-investor claims that would bypass the on-chain restriction; expect a key-rotation / claim-revocation story to crystallize as the tokenized-equity market matures, because as of April 2026 claim-revocation timeliness is uneven across registry providers.
Step 5 · Cap Table Update — On-Chain Shareholder RegisterPolicy-EnforcedBlockchain-Native
The transfer agent updating the stock register — new owner recorded, old owner removed, cap table current and ready for the next record date's corporate action (dividend, vote, rights offering), just as Computershare or AST would update a traditional issuer's shareholder ledger after a settled trade.
Securitize's transfer-agent system updates the cap table in real-time against the on-chain settlement event. The on-chain ownership IS the cap table — there is no reconciliation between a blockchain tally and a separate shareholder register because the token contract's `balanceOf` + the identity registry's ONCHAINID-to-person mapping IS the register. L4 Account and L5 Application lit on both sides: the cap table update is policy-enforced by the transfer agent's registered role under SEC Rule 17Ad-15 (obligations of registered transfer agents), with on-chain balance updates providing the authoritative source of truth. Corporate actions (dividends, stock splits, proxy votes, rights offerings, tender offers) now flow to the new holder's address — dividend payments via the issuer's paying agent (Computershare, Securitize's built-in paying agent), proxy voting via the transfer agent's vote-collection dashboard, rights offerings via a timed subscription window at the token contract. Builder: the cap table can be read directly from the chain via a `getHolders()` view that iterates the registry + balance pairs; for issuers with frequent corporate actions, maintain an off-chain cache indexed by block height for O(1) historical lookups (the Record Date pattern). For tax reporting, the cost-basis tracking is anchored to the acquisition event's block number and price (from the Step 3 trade), accessible via a `getCostBasis(tokenId, holder)` view. Compliance officer: satisfies C11 (recordkeeping — the cap table + the on-chain transfer history + the identity-registry claim history together form the authoritative shareholder record with a retention floor of 10 years under SEC Rule 17Ad-7(a) for transfer agents), and C12 (audit/attestation — an independent auditor can verify the cap table against the on-chain state without needing cooperation from the transfer agent, strengthening the audit posture). Corporate-action compliance: for dividends, the transfer agent's Rule 17Ad-17 (obligations to locate lost securityholders) is easier to satisfy because the on-chain address is always reachable even if the identity registry's KYC contact info is stale. Honesty marker: 'on-chain IS the cap table' is true for private-company tokenized equity where the transfer agent issues the definitive registry — but for US public equities (NYSE/NASDAQ-listed) the DTC / Cede & Co. nominee structure remains the legal record-of-ownership, and any tokenization would layer on top of rather than replace that structure; the tokenization-replaces-DTC story is a multi-decade project, not a 2026 reality.
Step 6 · Regulatory Reporting — Form D, 1099-B, Blue SkyPolicy-EnforcedBlockchain-Native
Quarterly SEC filing updates and year-end tax reporting — the issuer's perpetual compliance obligations, running on the same recordkeeping machinery that has governed private-company shareholder administration for decades, now anchored to on-chain evidence of each triggering event.
Post-trade reporting obligations crystallize. Form D (SEC Regulation D filing) amendments under Rule 503 fire whenever the issuer's offering details change (new investors, new sub-amount, new state of sale) — for 506(c) offerings, the amendment cadence is significant because each new trade can be a new sale event. State blue-sky notice filings and fees follow Form D by ~15 days for most states. Tax reporting: IRS Form 1099-B for US persons on every sale event, IRS §6045 cost-basis reporting (the cost basis anchored to the on-chain acquisition block), K-1 for pass-through tokenized partnerships (common for Apollo × Securitize tokenized credit funds). For the issuer's annual compliance, Form 10-K equivalent disclosure for §12(g) Exchange Act reporting companies, or the Rule 144A offering-memorandum-equivalent for QIB-only offerings. L5 Application lit only — regulatory reporting is end-of-pipeline, after everything else has settled. Builder: subscribe to an on-chain index of trade events (The Graph or a custom indexer) and auto-generate Form D amendment drafts + 1099-B forms from the indexed events; Securitize's back-office provides this for its issuers, but an issuer running its own transfer-agent shell must build it. Store the reporting-obligation archive in R2/S3-Glacier with the retention floor for the longest-applicable jurisdiction (SEC 17Ad-7 is 10 years for transfer agents; state blue-sky varies). Compliance officer: satisfies C11 (recordkeeping — the full reporting trail anchored to the on-chain trade events has multi-jurisdictional retention floors of 6 years SEC, 10 years SEC transfer-agent, 7 years FINRA, longer for specific state regulators), C12 (audit/attestation — the on-chain trade events are independently verifiable, making the Form D amendment + 1099-B generation auditable against a single source of truth), and C13 (market-integrity regulatory reporting — for SEC-registered ATSs the Form ATS-R quarterly filing fires; for NMS-listed tokens the SEC CAT Rule 613 obligations fire within narrow windows). GENIUS §9 (custody & recordkeeping) applies directly to the transfer agent and paying agent; §4(b) monthly attestation applies where the issuer pays dividends in a stablecoin. Honesty marker: the transfer agent's compliance is perpetual — it does not end at trade settlement. Every future transfer, every corporate action, every cap table change runs through the same compliance pipeline. This is what 'tokenized securities' really means: not just digital trading, but permanent, programmable compliance, which is both the value proposition and the cost center. For issuers weighing tokenization vs. traditional paper-share administration, the annual running cost of tokenization (registry operator fees + transfer-agent cloud infra + audit) is comparable to traditional — but the optionality of future corporate-action automation is distinctive, especially for frequent-dividend funds like BUIDL and Franklin OnChain.
Resolved 6 steps across 1 chain(s). 3 threshold(s) triggered. Frameworks: Bank Secrecy Act, GENIUS Act, OFAC Sanctions Program, FATF Recommendation 16 (Travel Rule), Common Reporting Standard / FATCA.
Transfer Agent OFAC Gate
The Chainalysis oracle check that fires at the transfer-agent pre-approval step — screens both counterparties before the ERC-3643 canTransfer hook allows the Reg D 506(c) trade to settle.