Important: Growth Turbine provides marketing, communications, lead-generation, and investor-relations support services only. GT is not a registered broker-dealer, placement agent, investment adviser, or funding portal, and does not offer, sell, or solicit any security. GT does not accept commissions, success fees, finder's fees, carried interest, equity, or any compensation tied to capital raised or investors introduced. Any securities offering is conducted by the issuer under the direction of issuer counsel. Full disclosures.

All Articles
ComplianceNovember 18, 202618 min read

ERC-3643 vs ERC-1400 vs ERC-20: Which Token Standard Should a Security Token Use?

Quick Answer

A practitioner comparison of every security token standard issuers hear about, from ERC-20 and ERC-1400 to ERC-3643, ERC-7518, ERC-4626 and non-EVM options, with a decision guide by asset type.

For most new security tokens on an EVM chain, ERC-3643 is the default choice as of November 2026: it is a Final Ethereum standard with on-chain identity, transfer rules, freezing, forced transfer and wallet recovery built in. ERC-1400 is still in use and offers partitions and document management, but it never left Draft status. Plain ERC-20 has no compliance features at all, so it only works for a security if the platform enforces restrictions somewhere else. The standard you pick decides which wallets, transfer agents, broker-dealers and ATSs can handle your token, and that decides who can actually buy it.

This guide compares every token standard an issuer is likely to hear about in a tokenization pitch: ERC-20, the ERC-1400 family (ERC-1594, ERC-1410, ERC-1643, ERC-1644), ERC-3643 (T-REX), ERC-1404, ERC-7518, ERC-4626, ERC-721 and ERC-1155. It also covers the non-EVM equivalents on Stellar, Polymesh, XRP Ledger, Solana and Hedera. Every status below was checked against eips.ethereum.org or the standard's own GitHub repository. For a wider view of the market, start at the Growth Turbine tokenization hub.

The short answer by situation

  • New fund, real estate SPV, private credit note or equity token on an EVM chain: ERC-3643, or whatever compliant standard your tokenization platform runs natively. The decision is usually made when you pick the platform.
  • You need several share classes or tranches inside one token contract: look at ERC-1400's ERC-1410 partitions, or ERC-7518, which uses ERC-1155 token IDs as partitions (ERC-7518 is still in Review).
  • A yield or vault product where share accounting matters: ERC-4626 handles the deposit and redeem interface. The share token still needs a permissioning layer if it is a security.
  • A single unique asset or a small set of unique units: ERC-721 or ERC-1155, with transfer restrictions added. Neither standard has any compliance built in.
  • A non-EVM chain (Stellar, XRP Ledger, Solana, Hedera, Polymesh): you use the chain's native asset controls instead of an ERC.

Why can't a security token just be ERC-20?

ERC-20 (Final, created 2015-11-19) defines six functions (transfer, transferFrom, approve, allowance, balanceOf, totalSupply) and two events. It has no way to block a transfer to an unverified wallet, no identity check and no way for an issuer or transfer agent to move tokens without the holder signing. For a freely tradable payment token that is the point. For a security it is a problem.

Securities law follows the token. A Reg D 506(c) offering limits who can buy. A Reg S offering limits resales into the US for a set period. Fund documents cap holder counts, and courts can order shares moved. A plain ERC-20 lets anyone send the token to any address, including an anonymous wallet or a decentralized exchange pool. The issuer then cannot enforce its own offering terms on-chain.

Some platforms still issue ERC-20-compatible tokens and enforce restrictions in a wrapper, a whitelist contract or an off-chain transfer agent register. That can work, but the compliance lives outside the standard. Ask the platform exactly where a transfer gets blocked and who can reverse it. Every standard below starts from ERC-20 compatibility and adds those controls on top.

What is ERC-1400 and its parts (ERC-1594, ERC-1410, ERC-1643, ERC-1644)?

ERC-1400 is a suite of security token interfaces proposed in September 2018. Its discussion issue was opened by Adam Dossa, and the listed authors are Adam Dossa, Pablo Ruiz, Fabian Vogelsteller and Stephane Gosselin. It builds on ERC-20 and bundles four companion standards:

  • ERC-1594 (core security token): issuance, redemption and transfer checks that return a reason code when a transfer would fail.
  • ERC-1410 (partially fungible tokens): splits one holder's balance into partitions, or tranches, each with its own metadata. A partition can represent a share class, a locked versus unlocked balance, or a Reg D versus Reg S lot.
  • ERC-1643 (document management): attaches named legal documents to the token by URI, with an optional content hash.
  • ERC-1644 (controller operations): lets a designated controller force transfers or redemptions for legal action or fund recovery.

Status matters here. ERC-1400 never became a Final EIP. The GitHub issue lists it as Draft and was closed in June 2022 "for housekeeping purposes", and the thread is marked stale. The reference spec lives in the SecurityTokenStandard/EIP-Spec repository. A widely referenced implementation, Consensys's UniversalToken, says it contains the ERC1400 implementation used by its Codefi Assets platform. It changed the spec (controller functions merged into operator functions, partition-aware allowances, validator hooks), and the repository is now a read-only archive.

So ERC-1400 is less one standard than a family of patterns. Two "ERC-1400" tokens from different vendors may not behave the same way. Partitions and on-chain documents are real strengths. Missing pieces are a standard identity layer and an active governance body.

What is ERC-3643 (T-REX)?

ERC-3643 describes itself as an institutional-grade security token contract. It was created 2021-07-09 by Joachim Lebrun, Tony Malghem, Kevin Thizy, Luc Falempin and Adam Boudjemaa, it requires EIP-20 and EIP-173, and its status is Final. It grew out of Tokeny's T-REX ("Token for Regulated EXchanges") contracts. The token is ERC-20 compatible, so wallets and explorers can read balances, but every transfer has to pass identity and compliance checks first.

How does the ERC-3643 identity registry and ONCHAINID work?

The standard splits compliance into separate contracts:

  • ONCHAINID: an identity contract for each investor. It holds claims, signed attestations such as "KYC passed" or "accredited investor", issued by trusted third parties. The personal data itself stays off-chain.
  • Identity Registry: maps each wallet to an ONCHAINID and an ISO-3166 country code. Its isVerified() check confirms the identity holds every required claim from a trusted issuer. Several tokens can share one whitelist through an Identity Registry Storage contract, so an investor verified for one offering can be eligible for the next.
  • Trusted Issuers Registry and Claim Topics Registry: list which KYC providers or verifiers the token accepts and which claim types are required.
  • Compliance contract: runs global rules through canTransfer() before any transfer settles.

What are ERC-3643 compliance modules?

The compliance contract can be custom-built or modular. The ERC-3643 documentation lists example modules built by tokenization platforms, noting they are not part of the open-source protocol itself. They include CountryAllowModule and CountryRestrictModule (allow or block by investor country), MaxBalanceModule (cap per-address holdings), SupplyLimitModule (cap total supply), ExchangeMonthlyLimitsModule, TimeTransfersLimitsModule and TimeExchangeLimitsModule (volume limits over time), TransferFeesModule and TransferRestrictModule (an allow list). In practice this maps neatly onto offering rules: a Reg S country block, a holder cap or a lock-up.

What issuer controls does ERC-3643 include?

Agents (the issuer, transfer agent or platform) get forcedTransfer(), which skips the compliance rules but still requires a verified receiver. They also get recoveryAddress() to move tokens from a lost wallet to a new wallet tied to the same identity, setAddressFrozen() and partial freezing, and pause()/unpause() for the whole token. Batch functions handle bulk mints and transfers.

Who governs ERC-3643, and is it audited?

The ERC3643 Association is a non-profit under Luxembourg law. As of November 2026 its site says it has 152 member organisations. The site also lists ESMA citing the standard in a 2023 DLT Pilot study, SEC Chairman Atkins naming it in 2025, and a German eWpG-conformity statement in 2025. The specification is CC0 and the reference code is GPL-3.0. The ERC-3643 GitHub repository is now the official contract suite and displays a Hacken audit of T-REX v4. The original TokenySolutions/T-REX repository was archived on October 28, 2025 and points users to the ERC-3643 repo. Ask your platform which version it deploys and whether its own modules were audited separately.

What is ERC-1404?

ERC-1404, the "Simple Restricted Token Standard", is the minimal option. Its GitHub issue lists authors Ron Gierlach, James Poole, Mason Borda and Lawson Baker, with a created date of July 27, 2018. It adds two functions to ERC-20: detectTransferRestriction() returns a code, and a non-zero code reverts the transfer. messageForTransferRestriction() turns that code into a readable reason. The rule logic is left entirely to the issuer.

The header lists it as Draft, and the issue was closed for inactivity in March 2022. A pull request with adapted content was opened in the ERCs repository in April 2026, so check its current state before relying on it. ERC-1404 is easy to build on, but it standardizes only the "can this transfer happen" question. Identity, recovery and forced transfer are left to each implementation.

Is ERC-7518 a real standard?

Yes. ERC-7518, the "Dynamic Compliant Interop Security Token", was created 2023-09-14 and is in Review status as of November 2026, so it is not final. It extends ERC-1155: each token ID acts as a partition with its own rights and compliance rules. It adds a canTransfer check, optional signed off-chain vouchers that approve a transfer, token locks with release times, address freezing, forced transfers from frozen addresses, and payouts to one or many holders. It also defines wrapping and unwrapping of tokens from other standards. Think of it as an attempt to merge ERC-1410-style partitions with modern compliance hooks. Treat it as early-stage until it reaches Final.

Where does ERC-4626 fit for tokenized funds?

ERC-4626 (Final, created 2021-12-22) standardizes tokenized vaults: shares that represent a claim on a single underlying ERC-20 asset. It defines how assets convert to shares, deposit and mint, withdraw and redeem, and preview functions so integrations can quote a deposit before it happens.

For fund issuers, ERC-4626 solves an accounting and integration problem, not a compliance one. It makes the subscribe/redeem flow legible to other smart contracts, such as lending markets, treasury tools and portfolio dashboards. It does not check who the holder is. The standard explicitly allows a non-transferable vault that reverts on transfer. A security fund would normally pair the vault interface with a permissioned share token, or put the vault behind an allow list. If a vendor pitches "ERC-4626 for our fund", ask how eligibility is enforced on deposit and on transfer.

Should real estate or unique assets use ERC-721 or ERC-1155?

ERC-721 (Final, created 2018-01-24) tracks unique, non-interchangeable tokens. ERC-1155 (Final, created 2018-06-17) manages fungible, non-fungible and semi-fungible types in one contract. They suit a deed-like record of one property, or a set of distinct units such as individual notes or lots.

Neither has any transfer restriction, identity check or forced transfer. A fractional real estate offering sold to investors is still a security, and fractions are usually fungible within a class. Most issuers therefore use a fungible compliant token for the investor-facing units. An NFT might represent the underlying asset or SPV record at most. ERC-7518 is the attempt to bring compliance to the ERC-1155 model.

What do non-EVM chains use instead?

Outside Ethereum-compatible chains there is no ERC. Compliance features are part of the chain's native token model. For a full chain comparison, see which blockchain to issue a security token on.

  • Stellar: issuers set authorization flags on the issuing account. AUTH_REQUIRED means the issuer must approve each holder's trustline. AUTH_REVOCABLE lets it freeze a holder. AUTH_CLAWBACK_ENABLED (requires revocable) lets it claw back and burn the asset. An "authorized to maintain liabilities" level allows case-by-case approval. AUTH_IMMUTABLE locks the flags permanently.
  • Polymesh: a public permissioned chain built for regulated assets. Per its developer docs, every participant in asset transactions needs a verified on-chain identity. Transfer compliance rules and multi-party atomic settlement are protocol features, not smart contracts.
  • XRP Ledger: Multi-Purpose Tokens (XLS-33, listed as Final) carry issuance flags such as lsfMPTRequireAuth (holders must be authorized), lsfMPTCanLock, lsfMPTCanClawback, lsfMPTCanTransfer and lsfMPTCanTrade. These are set when the token is created.
  • Solana: the Token-2022 program offers extensions including Transfer hook, Permanent delegate, Default account state, Pausable, Confidential transfers, Metadata and Scaled UI amount. Combined, they approximate an allow list, issuer recovery and freezes.
  • Hedera: the Hedera Token Service gives a token optional KYC, freeze, wipe and pause keys, so only approved accounts can transact.

Security token standards compared (as of November 2026)

StandardTransfer restrictionsIdentityForced transfer / recoveryPartitionsDocument managementStatus and audit notes
ERC-20NoneNoneNoneNoNoFinal (2015). Compliance must live outside the token.
ERC-1400 (1594/1410/1643/1644)Yes, transfer checks with reason codesNot standardized (whitelist or certificates per vendor)Yes, controller transfer and redeem (ERC-1644)Yes (ERC-1410)Yes (ERC-1643)Draft; issue closed 2022. Implementations vary; Consensys reference repo archived.
ERC-3643 (T-REX)Yes, compliance contract plus modulesYes, ONCHAINID claims and Identity RegistryYes, forcedTransfer and recoveryAddress; freeze and pauseNo native partitionsNot in the core interfaceFinal. Governed by the ERC3643 Association; Hacken audit of T-REX v4 shown in repo.
ERC-1404Yes, restriction codes; logic is issuer-definedNone standardizedNot standardizedNoNoDraft; issue closed 2022; adapted PR opened 2026.
ERC-7518Yes, canTransfer plus optional signed vouchersNot a full identity layer; compliance authorizations optionalYes, forced transfer from frozen addresses; freeze and locksYes (ERC-1155 token IDs)Optional asset profile extensionReview (created 2023). Not final.
ERC-4626None by default; non-transferable vaults allowedNoneNoneNoNoFinal (2021). Vault accounting interface.
ERC-721 / ERC-1155NoneNoneNoneERC-1155 token IDs can act as classesMetadata URI onlyBoth Final (2018).
Stellar assetsYes, AUTH_REQUIRED trustline approvalOff-chain KYC; issuer approves accountsFreeze (revocable); clawback if enabledNo (separate assets per class)NoProtocol-level features.
Polymesh assetsYes, protocol compliance rulesYes, verified identity required at chain levelIssuer controls at protocol levelNot reviewed hereNot reviewed hereProtocol-level; public permissioned chain.

"Adoption" is deliberately not scored with numbers. No primary source publishes a clean per-standard count of live tokens or assets. The ERC3643 Association publishes member counts, not tokenized value. Ask any vendor for its own deployed-token list and check a sample on a block explorer.

Which token standard fits which asset type?

Real estate fund or SPV

Typical needs are a holder cap, accredited-only buyers for a 506(c) raise, country blocks for Reg S tranches, and the ability to fix a lost wallet or carry out an estate transfer. ERC-3643's identity registry, MaxBalance and Country modules, and recovery function line up with this directly. If the fund has several classes (say, a preferred and a common class), either deploy one ERC-3643 token per class, or consider a partitioned standard. Marketing considerations are covered in marketing tokenized real estate funds to accredited investors.

Private credit

Notes often have tranches, maturities and lock-ups, and redemptions are manual. ERC-1410 partitions or ERC-7518 token IDs model tranches inside one contract. ERC-3643 handles it with one token per tranche. Many private credit products also want ERC-4626-style share accounting so DeFi or treasury integrations can read the position, wrapped behind an allow list. The deciding factor is usually which lenders and venues the issuer wants to reach, not the code.

Operating company equity

Equity needs a clean cap table, transfer restrictions for lock-up periods, corporate actions and legally effective forced transfers. Here the transfer agent's system is the real record. Pick the standard your SEC-registered transfer agent or tokenization platform actually supports, then check that its forced-transfer and recovery functions match your shareholder agreement.

Tokenized treasuries and money market funds

These products are typically restricted to whitelisted investors. BlackRock's BUIDL page on Securitize says the fund only permits transfers to whitelisted investors who pass KYC/AML checks. They are also commonly issued on several chains at once. The question is less which ERC and more which identity layer works across all those chains, and which collateral and settlement integrations (where ERC-4626-style interfaces help) the fund wants. A companion guide on tokenized treasury funds covers lessons for issuers in more depth.

What do investors, broker-dealers and ATSs care about?

Investors rarely ask which ERC you used. They notice the effects of that choice:

  • Can I hold it in a wallet or custodian I already use? A custom standard means a new wallet, which loses buyers at checkout.
  • What happens if I lose my keys? A defined recovery process (ERC-3643's recoveryAddress, ERC-1644 controller transfers, Stellar clawback) is a selling point for non-crypto investors.
  • Can I sell later, and where? Resale depends on whether a regulated venue can onboard the token.

Broker-dealers, transfer agents and ATS operators look at it from the other side. They need to know whether the token's transfer rules can be enforced at settlement, whether they hold the agent or controller role needed to act on court orders and errors, whether the contract is audited, and whether it plugs into their existing whitelist. A venue that already supports a standard can list a new token as configuration work. A venue that does not support it faces an integration project, and many will simply decline. Examples include tZERO, whose site says it operates a regulated ATS and an SEC-licensed transfer agent, and Securitize. Ask each venue which standards it supports before you deploy, not after.

Why does the token standard affect distribution and marketing?

Because distribution is where most tokenized raises stall. The standard sets three things that hit your funnel directly:

  1. Who can onboard. An identity-based standard lets an investor verified once reuse those claims across offerings that share the registry. That cuts KYC friction for repeat buyers. A custom whitelist means every investor starts from zero.
  2. Which channels can sell it. If the broker-dealer or ATS you want cannot settle your standard, that channel is closed. Your marketing then has to drive investors to a single issuer portal, which converts worse.
  3. What you can truthfully say about liquidity. You can only point to secondary trading if a venue actually supports the token. Promising liquidity you cannot deliver is a compliance problem as well as a trust problem.

The practical rule: pick the venue and investor audience first, then the standard those venues support, then the platform that deploys it. Issuers who do it in reverse often end up with a technically sound token that no distribution partner can carry. More on that failure mode in why investors don't buy tokenized offerings.

How to choose a security token standard, step by step

  1. Write down the offering rules first. Exemption (Reg D, Reg S, Reg A+, Reg CF or non-US), holder caps, lock-ups, country restrictions, share classes and redemption terms. Counsel will usually own this list.
  2. Name your target distribution. Which broker-dealers, ATSs, custodians and wallets must be able to hold or trade the token? Get their supported-standard lists in writing.
  3. Pick the chain. If you need a non-EVM chain for venue or cost reasons, the ERC debate ends and native asset controls apply.
  4. Map each rule to a mechanism. For ERC-3643, that means which claim topics, which compliance modules and which agent roles. For ERC-1400, it means which partitions and which controller.
  5. Check status and audits. Prefer Final standards and audited code versions. Ask the vendor for the audit report covering the exact version and modules you will deploy.
  6. Define recovery and forced-transfer governance. Who holds the agent or controller key, under what process, and how investors are told about it in the offering documents.
  7. Test the investor journey end to end. Verify a test investor, buy, attempt a blocked transfer, recover a wallet. Watch where a real buyer would drop off.

Platform selection follows from this. See how to choose a tokenization platform and security token KYC, whitelisting and transfer restrictions.

Frequently Asked Questions

Is ERC-3643 better than ERC-1400?

Neither is better in the abstract. They solve different problems. ERC-3643 is a Final EIP with a standardized identity layer, modular compliance and recovery. ERC-1400 is a Draft-status family with partitions and on-chain document management that vendors implement differently. Choose based on what your target venues and platform support.

Can a security token be a plain ERC-20?

Technically yes, but ERC-20 has no transfer restrictions, identity checks or forced transfer. Any compliance would have to be enforced by a wrapper, a whitelist contract or an off-chain register. Issuers typically choose a permissioned standard so offering rules are enforced at the token level.

Is ERC-1400 an official Ethereum standard?

No. As of November 2026, ERC-1400 is listed as Draft and its GitHub issue was closed in 2022 for housekeeping. Its components are still widely referenced, and implementations exist, but they are not a single Final specification.

What is ONCHAINID in ERC-3643?

ONCHAINID is an identity smart contract linked to an investor's wallet that holds signed claims, such as KYC or accreditation status, from trusted issuers. The token's Identity Registry checks those claims before allowing a transfer. Personal data stays off-chain; only the attestations are referenced on-chain.

Does ERC-4626 make a fund token compliant?

No. ERC-4626 standardizes vault deposit, redemption and share accounting, but it has no identity or eligibility checks. A security fund using ERC-4626 normally adds a permissioned share token or an allow list on deposit and transfer.

Does the token standard affect how many investors I can reach?

Yes. The standard decides which wallets, custodians, broker-dealers and ATSs can hold or trade the token. A widely supported standard opens more distribution channels. An unsupported one can limit you to a single issuer portal.

Get the token in front of investors who can actually buy it

Picking the standard is a technical decision with a distribution consequence. Growth Turbine is a marketing services provider, not a broker-dealer, funding portal or adviser. We build the investor-acquisition side: positioning, compliant campaigns and funnels that route qualified investors to your issuer's licensed partners and platform. Growth Turbine has supported 200+ campaigns and has provided marketing support across more than $540M in issuer-reported totals. See how we approach RWA tokenization marketing and security token sale marketing, or talk to our team.

Disclaimer: The information provided in this article is for educational and informational purposes only and does not constitute legal, financial, or investment advice. Always consult with qualified legal counsel and financial advisors before launching a capital raise.

Ready to Accelerate Your Investor Pipeline?

200+ campaigns supported. $540M+ in issuer totals. Get a free strategy session with our investor acquisition team.

About the Author

This article was written by Varun Sharma, Founder of Growth Turbine. Varun has spent over a decade in performance marketing and investor acquisition, leading 200+ campaigns supported across Reg CF, Reg D 506(c), Reg A+, and tokenized securities offerings.

Growth Turbine is a specialized investor acquisition agency that helps startups, real estate funds, fintech companies, and issuers across 25+ industries raise capital through equity crowdfunding and private placements. Its data-driven approach to digital marketing has provided marketing support across more than $540M in aggregate issuer-reported totals across 23+ crowdfunding platforms including Wefunder, StartEngine, Republic, Securitize, and DealMaker.

Explore our case studies to see real campaign results, browse our investor acquisition services, or schedule a free strategy call to discuss your investor outreach plan.