The token standard

ERC-3643: compliance, in code.

Every FUDEX token is an ERC-3643 permissioned token. Unlike ordinary crypto tokens, it checks an on-chain identity registry before every transfer — so a regulated security can live on a public blockchain without breaking the rules.

How it works

Three mechanisms, enforced by the contract.

Identity registry

Every whitelisted wallet is linked to a verified identity held off-chain. The contract consults this registry — not the wallet address alone — before allowing a transfer.

Transfer rules

A transfer to a non-whitelisted wallet doesn't get "flagged" — it fails at the protocol level. Jurisdiction limits and suspensions are enforced the same way.

Agent roles

Only the transfer-agent wallet can mint or burn tokens, and recovery functions let the registrar restore holdings to a verified owner after wallet loss.

Compared

ERC-20 vs ERC-3643.

ERC-20 (ordinary token)ERC-3643 (FUDEX tokens)
Who can hold itAnyone with a walletVerified, whitelisted members only
Transfer checksNone — any address acceptedIdentity registry checked on every transfer
Supply controlVaries by contractMint/burn by transfer-agent wallet only
Lost walletAssets goneRecoverable via identity-verified process
Legal statusUsually noneBook-entry security on a master registry
SuitsOpen crypto assetsRegulated, real-world securities
Why it matters here

The standard makes P2P possible.

Because the contract itself guarantees that every counterparty is verified and every supply change is registrar-authorized, FUDEX members can trade directly with each other — no intermediary needed at trade time. The compliance work happened up front, in the whitelist.

Get whitelisted once. Trade freely.

Verification puts your wallet on the ERC-3643 registry — after that, every trade enforces itself.