Start from the asset and the investor, not the standard: if the token is a regulated security, begin with ERC-3643; if it represents many distinct assets or high-volume units, consider ERC-1155 with compliance hooks; if it is a unique document or title, use ERC-721; if it is a fund with subscriptions and redemptions, use ERC-4626 or ERC-7540; and if you need a minimal interoperable compliance layer on any of these, add ERC-7943. The rest of this guide explains how to get to that answer for your case.
Key takeaways
- Answer six questions: fungibility, regulatory status, number of assets, lifecycle (fund vs instrument), trading venues and chain.
- Most projects combine standards — e.g. a title NFT + permissioned shares, or ERC-1155 assets + ERC-20 settlement coin.
- Ecosystem support (custodians, venues, wallets) can outweigh technical elegance.
- Choose early; migrations after issuance are costly and require investor communication.
The six questions
1. Are the units interchangeable?
- Identical units (shares of one class, fund units, grams of gold) → fungible (ERC-20 family).
- Unique items (a specific document, building record, loan agreement) → non-fungible (ERC-721).
- Both, or many classes → multi-token (ERC-1155 / ERC-6909).
2. Is it a security or regulated instrument?
If yes in any target jurisdiction, you need eligibility checks, freezes, forced transfers and recovery. Options: ERC-3643 (full framework), ERC-7943 (minimal interface), ERC-1404 (simple restrictions) or ERC-1400 (partitions).
3. How many assets will you issue?
One instrument per legal entity → one token each (ERC-3643 via factory). A portfolio managed together → ERC-1155 IDs per asset.
4. Is it a fund?
Pooled vehicles with subscriptions, redemptions and NAV → ERC-4626 (instant) or ERC-7540 (queued). Multiple currencies → ERC-7575.
5. Where will it trade and be held?
Check what your custodian, transfer agent, venue and target DeFi protocols support today. A technically perfect standard nobody can custody is a poor choice.
6. Which chain?
EVM chains support all ERCs. On Hedera you can use EVM contracts or the native Hedera Token Service with KYC and freeze flags. See Hedera for RWA and choosing a blockchain.
Recommendations by asset class
| Asset | Typical choice | Why |
|---|---|---|
| Single-property SPV shares | ERC-3643 | Regulated, cross-border investors |
| Property portfolio | ERC-1155 + compliance hooks (or ERC-7943) | One ID per property, shared rules |
| Title / deed record | ERC-721 | Unique, transferable record |
| Loan pools | ERC-1155 or ERC-3643 per pool | Pool-level or loan-level tokens |
| Bonds and notes | ERC-3643, ERC-3525 or ERC-3475 | Eligibility vs slot/class modelling |
| Money-market / credit fund | Permissioned ERC-20 + ERC-7540 | Async subscriptions and redemptions |
| Stablecoin / settlement coin | ERC-20 (+ permit, freeze) | Fungible money |
| Energy units | ERC-1155 / ERC-6909 | High-volume minting and burning |
| Carbon credits | HTS or ERC-1155 by vintage | Series per project/vintage, retirement |
| Bill of lading | ERC-721 / HTS NFT | Unique document of title |
| Credentials, KYC status | ONCHAINID claims or ERC-5192 | Non-transferable attestations |
What we chose and why (from our projects)
- Real estate: ERC-1155 on Hedera, one token class per property, compliance in contract logic — because the client wanted a multi-property platform with one marketplace. Case study.
- Electricity: two ERC-1155 tokens (ENERGY, CONSUMPTION) — batch-friendly units burned 1:1. Case study.
- e-BL: HTS NFT per document — uniqueness and low fees. Case study.
- Carbon: HTS tokens via Hedera Guardian — integrated policy engine and retirement. Case study.
Common mistakes
- Choosing ERC-20 for a security and bolting on a whitelist later.
- Choosing ERC-721 for fungible fractions and wrapping it awkwardly.
- Over-engineering partitions when separate tokens would do.
- Ignoring custody and venue support until launch.
- Forgetting upgrade governance — see ERC-1967 proxies.
A text decision tree
- Is the asset a pooled fund with subscriptions and redemptions? - Yes → Permissioned ERC-20 shares + ERC-7540 (async) or ERC-4626 (instant). Multiple currencies? Add ERC-7575. → Done. - No → continue.
- Is each unit unique (title, document, specific item)? - Yes → ERC-721 (or HTS NFT). Need fractions? Pair with fungible shares in an SPV. → Done. - No → continue.
- Will you issue many distinct assets managed together (portfolio, vintages, series)? - Yes → ERC-1155 (or ERC-6909) with per-ID compliance; consider ERC-7943 for interoperability, or ERC-7518 if partitions matter. → Done. - No → continue.
- Is it a regulated security for external investors? - Yes → ERC-3643 (or ERC-1400 if partitions are central and partners support it). → Done. - No → ERC-20 with appropriate controls (freeze, pause, permit).
Questions for your lawyers that shape the standard
- Is the token the legal register or a mirror?
- Which investor categories, in which countries?
- Lock-ups, holder limits, ownership caps?
- Who may freeze, seize or recover tokens, and on what authority?
- What disclosures must be linked to the token?
Future-proofing your choice
- Prefer finalised standards and audited libraries.
- Implement interface detection (ERC-165) and widely recognised interfaces like ERC-7943 so new venues can integrate.
- Use upgradeable proxies with governance so you can add features.
- Keep compliance logic modular to adapt to regulation.
Frequently asked questions
There is no single best standard. ERC-3643 is the most common for regulated securities; ERC-1155, ERC-721 and fund-vault standards fit other asset types.
Yes, and most platforms do — for example an ERC-721 title, ERC-3643 shares and an ERC-20 settlement coin.
The standard enforces rules; the legal structure defines them. You need both.
Yes — we offer a free 30-minute session to map your asset, investors and jurisdictions to a token design.
HTS tokens have their own model but can be accessed through EVM-compatible interfaces; alternatively deploy ERC contracts on Hedera’s EVM.
Combine standards — for example ERC-721 for the asset record and ERC-3643 for investor shares.
NUVZ is the RWA and Web3 engineering brand of ESS ENN Associates (est. 1993). Our team has designed and shipped tokenization platforms for real estate, education loans, solar PPAs, energy, carbon credits, bank deposits and trade documents. About us · Case studies
This article is for general information only and is not legal, tax or investment advice. Token standards evolve — always confirm the current status of an ERC at eips.ethereum.org and take advice from qualified counsel in each jurisdiction before issuing tokens.
