SHAMWARIPAY — MONETARY SYSTEM
CBDC-NATIVE 5 CURRENCY TYPES QUANTUM-SAFE NO SMART CONTRACTS

Stablecoins & CBDCs
on Shamwari

Shamwari is one of the few blockchain platforms purpose-built for state-issued digital currency and regulated stable value instruments. Five native currency types, a SOVEREIGN genesis flag, a dedicated BetaChain CBDC architecture, and 13 programmable tax types — all enforced at the consensus layer, not the application layer.

SOVEREIGN
5
Native currency types
enforced by consensus
134
Central banks globally
exploring CBDC issuance
13
Programmable tax types
in ShamwariPay
$13.7T
CBDC market projection
by 2030 (BIS)
CURRENCY ARCHITECTURE

Five types. One unified monetary system.

ShamwariPay encodes five distinct currency types at the protocol level. Each carries a different issuer relationship, reserve model, and regulatory footprint. All five settle on the same ledger, are subject to the same quantum-safe cryptography, and share the same compliance infrastructure.

CURRENCY_CBDC
Central Bank Digital Currency
Direct digital liability of the sovereign monetary authority. Legal tender, issued and redeemed by the central bank. The highest-trust currency type on the platform.
SOVEREIGN flag stamped at genesis
Non-deletable once issued
BetaChain deployment model
Full fee settlement capability
Retail & wholesale tiers supported
CURRENCY_STABLE
Regulated Stablecoin
Issued by a licensed private entity. Pegged to a fiat reference (USD, ZWG, BRL) and backed by verifiable on- or off-chain reserves. Requires regulator authorisation.
Issuer identity bound at creation
Reserve ratio enforced in protocol
Regulator revocation rights
Cross-chain bridge compatible
Programmable redemption windows
CURRENCY_DEPOSIT
Deposit Token
Tokenised commercial bank deposit. 1:1 representation of a balance held at a regulated bank. Combines programmability with existing deposit insurance frameworks.
Bank-issued, bank-redeemed
Deposit guarantee scheme eligible
KYC inherited from issuing bank
Interest-bearing variants
Intraday settlement finality
CURRENCY_EMONEY
E-Money Token
Prepaid electronic value stored in the protocol. Licensed under the national e-money framework. Ideal for mobile money operators, payment institutions, and fintech issuers.
Float-backed model
Capped balance limits (configurable)
Merchant settlement native
Offline-capable transaction model
Consumer protection rules encoded
CURRENCY_NATIVE
Native Protocol Currency
The base monetary unit of the Shamwari MainChain. Powers consensus fee settlement and bootstrap liquidity before a CBDC or stablecoin is deployed by an operator.
Fee settlement on MainChain
DEX base pair on Totem Exchange
Block reward distribution
DAO governance weight
Staking & forging collateral
All five currency types share one security baseline.
Every transaction across all five types is signed with ML-DSA-2 (NIST FIPS 204) and key-encapsulated with ML-KEM-512 (NIST FIPS 203). No currency on Shamwari is vulnerable to harvest-now, decrypt-later attacks. Quantum safety is not an add-on — it is the only mode the protocol knows.
SOVEREIGN CURRENCY TYPE

A protocol flag for central bank money.

When a BetaChain is configured as a CBDC chain, the fee currency — the token the chain uses to settle consensus — is automatically stamped SOVEREIGN at genesis. This is a permanent, consensus-enforced designation with four concrete consequences.

Protocol behaviour
Non-deletable
Once a SOVEREIGN currency exists on a chain, no transaction — including one signed by the issuer — can delete it. The monetary unit is as permanent as the ledger itself.
Fee settlement authority
All transaction fees on the BetaChain settle in the SOVEREIGN currency automatically. No operator configuration is required — the chain is hard-wired at genesis to denominate fees in the central bank token.
Genesis-only stamping
The SOVEREIGN flag is applied once, at chain creation, via the genesis JSON loader. It cannot be retrofitted to an existing currency, preventing later attempts to elevate a token's status without a chain restart.
Idempotency-guarded
The betaChainCurrency() initialisation is guarded against double-execution. The SOVEREIGN currency is created exactly once, even across node restarts and blockchain replays.
Genesis JSON — CBDC chain
// shamwari_genesis_[CHAIN].json { "chain": { "name": "Reserve Bank Digital Dollar", "chainId": "SHAMWARI-RBDD", "type": "BETACHAIN" }, "feeToken": { "code": "RBDD", "name": "RB Digital Dollar", "currencyType": "CURRENCY_CBDC", // ← Set by protocol at genesis: "sovereign": true, "deletable": false }, "issuer": { "account": "CENTRAL_BANK_ACCOUNT_ID", "mintAuthority": "MINT_POLICY_ACCOUNT_ID" } }
Why this matters for monetary policy
A CBDC platform where the fee token can be deleted is a CBDC platform with a single point of failure. Shamwari eliminates this risk at the protocol layer — the fee token and the monetary unit are constitutionally locked, as they are in every functioning monetary system.
BETACHAIN DEPLOYMENT MODEL

An entire central bank infrastructure on one chain.

BetaChains are permissioned child chains deployed by sovereign or institutional operators. Each BetaChain is a self-contained financial jurisdiction — its own fee token, its own governance rules, its own account permissions — secured by the Shamwari MainChain and post-quantum cryptography.

Shamwari MainChain
ML-DSA-2 · ML-KEM-512
Consensus anchor
Cross-chain settlement
BetaChain (CBDC)
SOVEREIGN fee token
Central bank controls
Retail + wholesale rails
End Participants
Citizens, businesses
PSPs, commercial banks
Government accounts
Tiered CBDC Architecture
BetaChains natively support two-tier CBDC models, where the central bank issues to commercial banks, who then distribute to retail participants — exactly mirroring the physical cash distribution model.
Tier-1: Central bank ↔ Commercial banks
Tier-2: Commercial banks ↔ Citizens
Balance caps per account tier
Interbank settlement natively on-chain
Wholesale CBDC Settlement
For inter-bank and government settlement use cases, BetaChains can be configured as wholesale rails where access is gated to KYC-verified institutional participants only.
Atomic delivery-vs-payment
RTGS replacement on-chain
Treasury bond tokenisation ready
Cross-chain FX settlement (mBridge-pattern)
Programmable Money Controls
Central banks retain full programmatic control over the monetary instrument. Unlike legacy programmable money approaches, all controls are consensus-enforced — not in a smart contract that can be exploited.
Expiry dates on individual notes
Targeted stimulus (sector-locked spending)
Negative interest rate capability
Transaction velocity limits per account
Cross-Chain Interoperability
Multiple BetaChains can settle against each other through the MainChain. A Zimbabwe CBDC BetaChain and a Kenya e-money BetaChain can transact without leaving the Shamwari ecosystem.
MainChain-mediated atomic swaps
Corridor FX rates set by protocol
Remittance settlement under 3 seconds
No correspondent banking required
No smart contracts. No exploitable programmability.
Every "programmable money" feature described above is implemented as a native transaction type or consensus rule — not as a smart contract. This is not a minor distinction. Smart contract exploits have drained over $3.8B from DeFi protocols. For a CBDC carrying the savings of millions of citizens, protocol-native is the only responsible choice.
MONETARY CONTROLS

Every lever a central bank needs. None it doesn't.

Shamwari gives CBDC and stablecoin issuers the full toolkit of a modern monetary authority — encoded in the protocol, not in off-chain policy documents that participants can ignore.

Mint & Burn Authority
The issuer account holds exclusive mint rights. New currency units are created via a signed CURRENCY_ISSUANCE transaction. Burn is permanent and consensus-finalised within the next block.
13 Programmable Tax Types
VAT, capital gains, withholding, Tobin tax, stamp duty and eight further types are native to ShamwariPay. Tax is calculated and withheld at the transaction level — no post-settlement reconciliation.
Freeze & Sanction Controls
Regulator-designated accounts can be frozen at the consensus layer. A frozen account cannot send or receive the affected currency — enforced by every validating node, not just the issuer's own API.
Supply Cap Configuration
Maximum supply can be set at creation and updated by the issuer within configurable bounds. Hard caps prevent algorithmic hyperinflation. The cap is a consensus rule, not an API gate a bad actor can bypass.
Time-Locked Vaults
Users and issuers can lock balances in time-locked vaults with block-height precision. Useful for salary advances, government stimulus disbursement, and bond coupon payments without counterparty risk.
Interest Accrual
Native block-height interest accrual is available on savings and vault accounts. Central banks can offer positive or negative interest rates on retail CBDC balances without any smart contract middleware.
COMPLIANCE & PRIVACY

Regulatory-grade from the first block.

The most persistent objection to CBDC adoption is surveillance risk — the fear that programmable state money becomes a financial panopticon. Shamwari addresses this directly with privacy-preserving design choices that do not require sacrificing auditability.

Control / Feature CBDC Stablecoin Deposit Token E-Money Notes
SOVEREIGN flag Yes No No No Genesis-only, consensus-enforced
Non-deletable currency Yes No No No Permanent monetary anchor
KYC / AML enforcement Yes Yes Yes Yes All types, consensus-enforced
Account freeze capability Yes Yes Yes Partial E-money: balance limit only
Programmable expiry Yes Optional No Optional Block-height precision
Interest accrual Yes No Yes No Native, no smart contract
ML-DSA-2 signing Yes Yes Yes Yes NIST FIPS 204, all tx types
Fee settlement in currency Yes Operator Operator Operator CBDC fee settlement is automatic
Cross-chain settlement Yes Yes Limited Limited Via MainChain atomic swap
Regulator account at genesis Yes Yes Yes Yes All types require regulator account
Privacy by design, auditability by requirement
Shamwari does not make privacy vs. auditability a binary choice. Transaction details are encrypted end-to-end using ML-KEM-512. Regulators with the appropriate account-level permission can decrypt and audit specific transaction streams without exposing data to other chain participants. Citizens' balances are not a public ledger.
RAIL COMPARISON

Why not Ethereum, Stellar, or Ripple?

Every existing CBDC rail was either retrofitted from a general-purpose chain, built before post-quantum cryptography standards existed, or requires smart contract programmability — introducing the very complexity regulators are trying to avoid.

Shamwari
CBDC-NATIVE · PQC · NO CONTRACTS
Purpose-built for CBDC & stablecoins
ML-DSA-2 + ML-KEM-512 from genesis
SOVEREIGN currency type in protocol
13 native tax types
Zero smart contract surface
Native KYC & account permissioning
BetaChain two-tier model
RBZ / IPEC / SECZ engagement active
Ethereum / EVM Chains
GENERAL PURPOSE
CBDC = smart contract, not native type
ECDSA — quantum-vulnerable
No SOVEREIGN concept at protocol level
Tax via off-chain middleware only
$3.8B+ smart contract exploit history
KYC is application-layer, bypassable
No native two-tier CBDC model
Regulatory status unclear in most markets
Stellar / XRP Ledger
PAYMENT FOCUSED
Payments-focused, not monetary system
ECDSA — quantum-vulnerable
No SOVEREIGN flag in protocol
No native tax infrastructure
Limited smart contract surface
KYC via anchor model (off-chain)
Two-tier via anchor intermediaries
Limited emerging market regulatory traction
R3 Corda / Hyperledger
ENTERPRISE DLT
Enterprise DLT, not public chain
Some PQC migration in progress
No SOVEREIGN protocol type
Tax via CorDapps (custom development)
Smart contract / CorDapp surface
Strong KYC model
Two-tier CBDC feasible
High cost, long procurement cycles
MARKET CONTEXT

The largest monetary upgrade in a generation.

The shift from physical cash to programmable digital currency is not a product category — it is monetary infrastructure. The window to establish the underlying rails is narrow, and it is open right now in every Shamwari target market.

134
Countries exploring CBDC
as of Q1 2025 (BIS)
$13.7T
Projected CBDC market
by 2030
$200B+
Africa stablecoin transaction
volume in 2024
11
African central banks in
active CBDC pilots
Africa
The continent moving fastest on CBDC

Nigeria's eNaira was the first African CBDC launch. Ghana, Rwanda, Kenya, Tanzania, and South Africa all have active research or pilot programmes. Zimbabwe's ZiG digitalisation creates a direct Shamwari opportunity — the RBZ has already confirmed a direct licence path via partner bank engagement.

RBZ Engaged ZiG Digitalisation $48B Remittance Corridor
MENA
Sovereign wealth meets digital currency ambition

Saudi Arabia's Project Aber, UAE's mBridge participation, and Bahrain's CBDC sandbox represent a region actively building digital monetary infrastructure. Shamwari's BetaChain multi-CBDC model directly addresses the cross-border settlement need across Gulf currencies.

mBridge Compatible Project Aber Pattern Multi-CBDC Settlement
LATAM
Inflation-proof digital currency demand

Brazil's Drex CBDC, Argentina's chronic dollarisation pressure, and Venezuela's failed Petro attempt all point to a region that needs a robust, programmable, quantum-safe monetary layer. Stablecoin adoption in Argentina is already the highest per-capita globally.

Drex-Pattern Ready Stablecoin Native
ASEAN
Real-time payments infrastructure demand

Thailand's e-Baht, Singapore's MAS Digital Money pilot, and the Philippines BSP CBDC research represent a region already leading in real-time payment adoption. The ASEAN multilateral CBDC settlement corridor is a direct BetaChain multi-chain use case.

MAS-Pattern Alignment ASEAN Corridor Settlement
BUILD WITH SHAMWARI

The CBDC infrastructure
your central bank needs is ready.

Full source code, BetaChain deployment documentation, and testnet access available now. If you represent a central bank, regulatory authority, or licensed financial institution, reach out directly.