Extensions

There is no opt-in "extension" bitflag system

Menu-of-extensions token programs on other chains let you toggle a fixed menu of extensions (transfer fees, memo-on-transfer, non-transferability, interest accrual, confidential balances, etc.) on a mint at creation time, all within a single program. EmpoorioChain doesn't work that way — instead of one program with optional extensions, different capabilities live in different, purpose-built pallets. There's no single "enable extension X" call; you pick the pallet that already has the behavior you want.

What's genuinely available

• Confidential Transfers & Data Consent — ZK-based confidential transfers and GDPR-style data consent/erasure, backed by pallet-privacy (index 17).
• Non-Transferable Tokens — soulbound-style tokens that can never change owners, backed by pallet-sbt (index 66).
• Freeze-style controls on fungible assets — asset- and account-level freeze/thaw is a core capability of pallet-emp-assets itself, not a separate extension. See Fungible Tokens.
• Collections/grouping for NFTs — native to pallet-uniques itself, not an add-on. See NFTs.
• Compliance-gated transfer restrictions — the core purpose of pallet-emp-rwa, not an extension on top of a plain fungible token. See RWA & Permissioned Tokens.

What was checked and doesn't have an equivalent here

The following menu-style token extensions were checked against the runtime's compiled pallet list and have no confirmed EmpoorioChain equivalent, so they've been removed rather than documented with invented pallet behavior: transfer fees, mandatory memo-on-transfer, CPI guard, immutable owner, interest-bearing/rebasing balances, mint-close (rent-reclaim), default account state, and scaled UI amount (cosmetic display multiplier). If one of these turns out to have a real equivalent that wasn't found during this research pass, treat that as something to re-check against the runtime source directly rather than assume it doesn't exist.