The direct answer
ERC-3643 is the Ethereum standard for permissioned security tokens: every transfer is validated on-chain against verified identities and issuer-defined compliance rules, and fails automatically if the recipient is not eligible. Where ERC-20 asks only "does the sender have the balance?", ERC-3643 also asks "is the receiver allowed to hold this security, in this amount, in this jurisdiction, right now?" That single change is what makes on-chain securities legally workable.
The three layers of the standard
1 — Identity. Each investor holds an on-chain identity (the ONCHAINID model) to which trusted verifiers attach claims: KYC passed, jurisdiction, investor category. Wallets are bound to identities, so tokens are held by people and entities, not anonymous addresses. 2 — Compliance rules. The issuer configures the rulebook in the token's compliance contract: eligible countries, investor caps, holding limits, lock-ups. 3 — Enforcement on transfer. Every transfer call runs the checks; a non-compliant transfer reverts. The token is compliant by construction, not by policy document.
What this makes possible
- A continuously accurate cap table. The on-chain register mirrors the legal register at all times — no reconciliation lag.
- Recovery. Lose a wallet, prove identity, and the issuer can reissue tokens to a new address — essential for instruments people hold for decades.
- Conditional liquidity. Secondary transfers between eligible holders can settle peer-to-peer while remaining fully compliant — the mechanism behind compliant secondary markets.
- Auditability. A regulator or auditor can verify the rule set and its enforcement directly, on-chain.
Honest limits
The standard enforces rules; it does not create rights. Legal enforceability comes from the offering documents and the SPV that holds the asset (how that structure protects holders) — ERC-3643 keeps the token register faithful to that legal reality. Its guarantees are also only as good as the identity verifiers and the issuer's rule configuration; sloppy KYC upstream produces compliant-looking transfers of the wrong thing. And permissioning constrains the free-floating liquidity crypto natives expect — deliberately: that constraint is the compliance.
Where it sits in a real platform
In ALTXRA's architecture, each asset's certificates are issued as ERC-3643 tokens by the asset's SPV, with eligibility rules driven by the platform's AI-automated KYC/AML layer (described here). The network token, ALTX, is deliberately not an ERC-3643 security — it carries no asset claim, per the separation explained in security vs utility tokens. One standard for ownership, one wall between ownership and utility: that is the whole design philosophy in two sentences.
Key takeaways
- ERC-3643 validates every transfer against on-chain identity and issuer compliance rules; ineligible transfers simply fail.
- Three layers: verified identities (ONCHAINID), configurable compliance rules, enforcement inside the transfer function.
- It enables accurate cap tables, wallet recovery, compliant secondary transfers and on-chain auditability.
- It enforces rules but does not create rights — legal enforceability still comes from offering documents and the SPV.
Frequently asked questions
What is ERC-3643?
ERC-3643 is an Ethereum token standard for permissioned security tokens. Unlike ERC-20, every transfer is checked against on-chain identity and compliance rules — investor verification, jurisdiction limits, holding caps — and simply fails if the receiving wallet is not eligible. It emerged from the T-REX protocol and became a formal Ethereum standard used widely in regulated tokenization.
How is ERC-3643 different from ERC-20?
ERC-20 tokens transfer to any address unconditionally. ERC-3643 binds tokens to verified identities: a transfer only executes if the recipient's on-chain identity passes the issuer's compliance rules. It also supports recovery of tokens from lost wallets via identity proof — impossible in plain ERC-20 — which matters for securities that must map to a legal register.
Why do regulated platforms use ERC-3643?
Because it makes compliance a property of the token rather than a promise of the platform. Eligibility (KYC/AML, accreditation, jurisdiction) is enforced by the smart contract on every transfer, the cap table stays continuously accurate, and regulators can verify that non-compliant transfers are technically impossible, not merely prohibited on paper.
