VSC-8: Protocol-Native Stablecoin Standard
Quantum-resistant minting. Unbreakable governance-controlled supply caps. Mint-only emergency freezes. Epoch rate-limited allowances. Protocol-native multi-sig. Timelocked role changes with guardian override. All enforced by the protocol -- not a contract that a proxy admin can rewrite.
VSC-8 is Vexidus's dedicated stablecoin standard -- purpose-built for regulated fiat-backed tokens. Unlike EVM chains where stablecoins are smart contracts that can be exploited via proxy upgrades, flash loans, or raw calls, VSC-8 is enforced at the protocol level by the state machine itself.
No bytecode. No proxy admin risk. No bypassing blacklists. Six security layers that cannot be circumvented because they are the protocol.
Why VSC-8 Exists
As stablecoin regulation matures globally -- MiCA in Europe, the GENIUS Act in the US, MAS frameworks in Singapore -- issuers face increasing scrutiny over reserve protection, operational security, and key management. Current smart contract architectures cannot provide protocol-level guarantees for these requirements.
On Ethereum, anyone can deploy an ERC-20 and call it "USDC." The real Circle USDC contract has no protocol-level advantage over a fake one -- both are just bytecode. Stablecoin issuers must rely on contract-level logic that a proxy admin could theoretically rewrite.
Vexidus eliminates this entirely. VSC-8 tokens are:
- Canonical -- one token per stablecoin, enforced by the protocol. No impersonation possible.
- Issuer-controlled -- the real issuer holds all operational roles (mint, pause, blacklist) with protocol-level authority.
- Cross-chain unified -- USDC bridged from Ethereum, Solana, Base, Arbitrum, and Polygon all map to the same canonical VSC-8 token. No fragmented liquidity.
- Quantum-ready -- optional Dilithium3 post-quantum key requirement per token, available today.
Six Security Layers
Every VSC-8 token has six independent security layers, all enforced by the state machine.
Layer 1: Epoch Rate Limiting
Every minter has an epoch limit -- a maximum amount that can be minted per epoch (default: ~2.4 hours). Even if a minter key is compromised, damage is capped.
| Parameter | Description | Default |
|---|---|---|
epoch_limit | Maximum mint per epoch | Configurable per minter |
epoch_length | Blocks per epoch | 720 (~2.4 hours at 12s) |
allowance_remaining | Total remaining allowance | Set by master minter |
ERC-20 comparison: Flat allowance -- a compromised minter can drain the entire allowance in one transaction. VSC-8 limits per-epoch exposure.
Layer 2: Multi-Signature for High-Value Mints
Large mints can require N-of-M cosigner authorization at the protocol level. Not an external multisig wallet (like Gnosis Safe on Ethereum) -- built into the token itself.
| Parameter | Description |
|---|---|
mint_threshold | Amount above which multi-sig is required |
required_signers | Number of cosigners needed (N) |
authorized_cosigners | List of authorized cosigner addresses (M) |
Layer 3: Timelocked Role Changes
All role changes (transferring owner, master_minter, pauser, or blacklister) are subject to a configurable timelock. During the delay, the owner or any guardian can cancel the change.
| Operation | Timelock | Emergency Override |
|---|---|---|
| Transfer any role | Yes (default 720 blocks) | Owner or guardian can cancel |
| Add minter | Yes | Owner or guardian can cancel |
| Remove minter | Immediate | Emergency response shouldn't be delayed |
| Full handover | Always timelocked | Highest-impact operation |
ERC-20 comparison: No timelock. A compromised admin key can instantly reassign all roles.
Layer 4: Guardian Emergency Freeze
Designated guardian addresses can immediately freeze minting without affecting existing transfers. This allows security monitoring systems to halt minting if an anomaly is detected, without disrupting holders.
| State | Minting | Transfers |
|---|---|---|
| Normal | Allowed | Allowed |
Paused (paused=true) | Blocked | Blocked |
Mint frozen (mint_frozen=true) | Blocked | Allowed |
- Any guardian can freeze minting immediately (no timelock)
- Only the owner can unfreeze
pausedandmint_frozenare independent controls
Layer 5: Quantum-Resistant Key Requirement
Issuers can enable Dilithium3 post-quantum signatures for all minting operations. When enabled, minter transactions signed with classical Ed25519 keys are rejected -- only Dilithium3-signed operations are accepted.
This makes VSC-8 the only stablecoin standard in crypto with native post-quantum security.
Layer 6: Governance-Controlled Supply Cap
An optional hard supply cap that only governance can increase. The token owner cannot raise it unilaterally. This provides an additional safety net -- even with valid minter keys, the total supply cannot exceed the governance-approved limit.
VSC-8 vs ERC-20 vs SPL Token
| Security Feature | ERC-20 (Ethereum) | SPL Token (Solana) | VSC-8 (Vexidus) |
|---|---|---|---|
| Minter allowance | Flat number, drainable in 1 tx | Single authority, no allowance | Epoch rate-limited (max per window) |
| Multi-sig for minting | External (Gnosis Safe) | No native support | Protocol-native, configurable threshold |
| Timelocked role changes | No | No | Configurable delay, guardian can cancel |
| Emergency mint freeze | No (only full pause) | Freeze = freeze everything | Mint-only freeze, transfers unaffected |
| Quantum-resistant keys | No | No | Dilithium3 requirement per token |
| Supply hard cap | No (infinite mint if compromised) | Optional but owner-controlled | Governance-controlled, owner cannot increase |
| Proxy/upgrade exploit | Proxy admin can rewrite all rules | N/A | Not applicable (protocol-native) |
| Blacklist bypass | Flash loan/raw call can bypass | N/A | Protocol-level, checked before any state change |
| Symbol squatting | Anyone can deploy "USDC" | Anyone can create "USDC" | Reserved symbols, only governance can assign |
Issuer Roles
VSC-8 follows the Circle FiatTokenV2 role model -- four distinct roles with separation of concerns:
| Role | Responsibility | Can Be Transferred |
|---|---|---|
| Owner | Transfer any role, configure timelock, unfreeze minting | Yes (timelocked) |
| Master Minter | Add/remove minters, set allowances and epoch limits | Yes (timelocked) |
| Pauser | Pause/unpause all transfers | Yes (timelocked) |
| Blacklister | Add/remove addresses from blacklist | Yes (timelocked) |
| Guardian | Emergency mint freeze (immediate, no timelock) | Added by owner |
Genesis Stablecoins
Vexidus launches with 18 pre-mapped stablecoins across 10 currencies and 6 continents. Each has a canonical protocol-enforced address, source chain contract mappings for bridge fast-path, and the "Official Stablecoin" badge in explorers.
USD Stablecoins
| Token | Issuer | Regulation | Chains |
|---|---|---|---|
| USDC | Circle | US (multiple licenses), MiCA EMI | Ethereum, Solana, Base, Arbitrum, Polygon, Avalanche |
| USDT | Tether | BVI | Ethereum, Tron, Solana, Arbitrum, Polygon |
| PYUSD | Paxos/PayPal | NYDFS | Ethereum, Solana |
| FDUSD | First Digital | Hong Kong | Ethereum, BNB Chain |
| USDe | Ethena | -- | Ethereum |
| DAI | MakerDAO | Decentralized | Ethereum |
EUR Stablecoins (MiCA Era)
| Token | Issuer | Regulation | Chains |
|---|---|---|---|
| EURC | Circle | MiCA EMI (France) | Ethereum, Solana, Base |
| EURCV | SG-Forge (Societe Generale) | MiCA EMI (French ACPR) | Ethereum |
| EURe | Monerium | MiCA EMI (Iceland) | Ethereum, Polygon, Arbitrum |
| EURS | STASIS | Malta regulated | Ethereum, Polygon, Arbitrum |
Asia-Pacific
| Token | Currency | Issuer | Regulation | Chains |
|---|---|---|---|---|
| JPYC | JPY | JPYC Inc. | Japan Payment Services Act | Ethereum, Polygon, Avalanche |
| XSGD | SGD | StraitsX | MAS (Singapore) | Ethereum, Polygon, Avalanche, Arbitrum |
| IDRT | IDR | PT Rupiah Token Indonesia | Indonesian ecosystem | Ethereum, BNB Chain, Polygon |
Americas
| Token | Currency | Issuer | Regulation | Chains |
|---|---|---|---|---|
| BRZ | BRL | Transfero | Swiss entity | Ethereum, Solana, BNB, Polygon, Avalanche |
| CADC | CAD | PayTrie | Canadian MSB | Ethereum, Polygon, Arbitrum, Base |
Europe, Africa & Oceania
| Token | Currency | Issuer | Regulation | Chains |
|---|---|---|---|---|
| TRYB | TRY | BiLira | Self-attested | Ethereum, Avalanche, BNB, Polygon |
| ZARP | ZAR | Rand Reserve | South African | Ethereum, Base, Polygon |
| NZDS | NZD | Techemynt | NZ FSP registered | Ethereum |
Reserved Symbols
An additional 18 symbols are reserved for stablecoins that are pre-launch, institutional-only, or awaiting regulatory clarity. These cannot be registered as VSC-7 tokens -- they are held exclusively for future VSC-8 issuance.
Reserved: GBPA, KRWQ, MXNT, CNHT, BIDR, CNGN, DDSC, AEUR, TGBP, ARC, TUSD, FRAX, LUSD, BUSD, GUSD, USDP, CUSD, SUSD, RAI, GHO.
Bridge Fast-Path
When a token is bridged into Vexidus via VexBridge, the protocol checks if the source chain contract address matches a known VSC-8 source mapping. If it does, the bridged tokens are credited to the canonical VSC-8 mint address instead of creating a new VSC-7 wrapped token.
This means:
- USDC bridged from Ethereum = same token as USDC bridged from Solana = same token as USDC bridged from Base
- One canonical USDC on Vexidus, not five fragmented wrapped versions
- Unified liquidity across all bridge origins
Impersonation Detection
If a bridged token's symbol matches a reserved stablecoin symbol but the source contract address is not in the official source mappings, the token is flagged with an impersonation warning. It will not receive the "Official Stablecoin" badge and will score 0 points on the verification factor of the reputation system.
Launchpad Origin Detection
Tokens originating from known launchpad contracts (e.g., pump.fun on Solana) are automatically tagged with launch_origin: "launchpad" and receive the "Memecoin" badge in explorers.
Listing Process for Stablecoin Issuers
Path A: Pre-Mapped Issuers (Genesis Stablecoins)
For the 18 stablecoins already pre-mapped at genesis, the process is streamlined:
Step 1 -- Initial Contact
Reach out to the Vexidus Foundation or respond to our outreach. Your token is already registered with a canonical address, source chain mappings, and the "Official Stablecoin" badge.
Step 2 -- Legal Verification
Prove your identity as the authorized representative of the issuing entity. Accepted methods:
- Domain verification -- publish a TXT record or
.well-known/vexidus.jsonon your official domain containing a Vexidus-provided challenge string - Source chain signature -- sign a message from the admin/owner address of your token's contract on Ethereum, Solana, or another source chain
- Corporate documentation -- provide incorporation documents, regulatory licenses, and authorized signatory proof (for regulated issuers)
Two of the three methods are required for handover.
Step 3 -- Key Ceremony
Generate your operational keypairs:
- Ed25519 (standard) -- compatible with existing infrastructure
- Dilithium3 (optional, recommended) -- post-quantum security for minting operations
The Vexidus Foundation can assist with key generation or the issuer can generate independently using the Vexidus SDK or CLI.
Step 4 -- Role Handover
The Foundation executes a StableHandover transaction, which is always timelocked (minimum 720 blocks / ~2.4 hours). During the timelock period:
- The handover details are publicly visible on-chain
- The Foundation or any guardian can cancel if an issue is detected
- After the timelock expires, all four roles (owner, master_minter, pauser, blacklister) transfer atomically to the issuer's keys
Step 5 -- Configuration
The issuer now has full autonomous control. Recommended first steps:
- Configure minter addresses and epoch limits
- Set up guardian addresses for emergency freeze capability
- Optionally enable multi-sig for high-value mints
- Optionally enable Dilithium3 quantum key requirement
- Set a governance-approved supply cap (via Foundation governance initially)
Step 6 -- Operational
The issuer operates their stablecoin independently. The Vexidus protocol enforces all security layers automatically. No further Foundation involvement is required for day-to-day operations.
Path B: New Stablecoin Issuers
For stablecoins not in the genesis registry:
Step 1 -- Application
Submit an application to the Vexidus Foundation including:
- Token name, symbol, decimals
- Issuing entity name and jurisdiction
- Regulatory licenses held (if any)
- Source chain contract addresses (for bridge mapping)
- Intended use case and target market
- Reserve attestation or audit reports
Step 2 -- Governance Review
The application is reviewed by the Vexidus Foundation (during testnet/early mainnet) or by protocol governance vote (post-activation via VSC-88).
Review criteria:
- Regulatory standing -- licensed issuers are prioritized
- Reserve transparency -- proof of reserves or regular attestations
- Technical readiness -- source chain contracts are deployed and operational
- Market demand -- demonstrated user base or clear market need
- Symbol uniqueness -- no conflict with existing or reserved symbols
Step 3 -- Token Creation
Upon approval, the governance authority executes CreateStableToken. This:
- Creates a canonical VSC-8 token with a deterministic mint address
- Registers source chain contract mappings for bridge fast-path
- Adds the symbol to the reserved list
- Assigns the "Official Stablecoin" badge
Step 4 -- Handover & Configuration
Same as Path A Steps 2-6. Legal verification, key ceremony, timelocked handover, issuer configuration.
Timeline
| Phase | Path A (Pre-Mapped) | Path B (New Issuer) |
|---|---|---|
| Initial contact | Day 1 | Day 1 |
| Legal verification | Days 2-5 | Days 2-5 |
| Governance review | N/A (already approved) | Days 5-14 |
| Key ceremony | Day 5-6 | Day 14-15 |
| Timelocked handover | Day 6-7 (~2.4hr timelock) | Day 15-16 |
| Operational | Day 7+ | Day 16+ |
RPC Endpoints
Write Operations
| Method | Description | Auth |
|---|---|---|
vex_createStableToken | Create a new VSC-8 token | Governance only |
vex_stableMint | Mint tokens | Authorized minter |
vex_stableBurn | Burn tokens | Any holder |
vex_stablePause | Pause/unpause transfers | Pauser role |
vex_stableBlacklist | Add/remove from blacklist | Blacklister role |
vex_stableTransferRole | Transfer a role (timelocked) | Owner only |
vex_stableConfigureMinter | Add/remove/configure minter | Master minter |
vex_stableHandover | Atomic handover of all roles (timelocked) | Owner only |
Read Operations
| Method | Description |
|---|---|
vex_getStablecoinInfo | Full stablecoin state (roles, config, security settings) |
vex_listStablecoins | List all VSC-8 tokens |
vex_isBlacklisted | Check if an address is blacklisted for a specific token |
Try It: List All Genesis Stablecoins
Query the live testnet to see all 18 pre-mapped VSC-8 stablecoins:
curl -s https://testnet.vexidus.io \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"method": "vex_listStablecoins",
"params": [50],
"id": 1
}' | jq .
Try It: Query a Specific Stablecoin
Pass a symbol or mint address to inspect its full state -- roles, security config, source chain mappings:
curl -s https://testnet.vexidus.io \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"method": "vex_getStablecoinInfo",
"params": ["USDC"],
"id": 1
}' | jq .
These examples hit the live Vexidus testnet at testnet.vexidus.io. Run them from any terminal to see real VSC-8 token state. After the beta genesis restart (~March 1, 2026), all 18 stablecoins will be queryable with full security configuration.
Reputation Scoring
VSC-8 tokens benefit from Factor 8 (Verification Status) in the Vexidus reputation system, worth up to 15 points:
| Status | Points | Description |
|---|---|---|
| Issuer-Held | 15 | Issuer has completed handover and controls the token |
| Verified | 12 | Governance has verified the issuer |
| Pending | 10 | Pre-mapped at genesis, awaiting issuer handover |
| Native VSC-7 | 8 | Standard native token (not VSC-8) |
| Bridged (clean) | 5 | Bridged token with no warnings |
| Launchpad origin | 3 | Originated from a known launchpad |
| Impersonation | 0 | Symbol matches reserved but source contract doesn't match |
This means VSC-8 stablecoins with completed issuer handover automatically receive the highest verification score, while impersonation attempts are scored at zero.
Contact
Stablecoin issuers interested in listing on Vexidus can reach the Foundation at:
- Email: TBA
- Twitter/X: @VexidusCorp
- GitHub: github.com/Mashiyu-Devs/Vexidus