The technical layer beneath M5 Wallet.
Chain-agnostic settlement matrix, SFI credential gating, ecosystem value-added services, built-in settlement splits, and the developer surface (SDK · MCP · x402). For engineers, partners, treasurers, and regulators. Members should start on the main wallet page.
M5Wallet is chain-agnostic by design. The same handle settles on whatever chain best matches the asset class, jurisdiction, and counterparty. ● live · ● activating (BTC via Lightning Network for M1, L2s for M4; M5 row entirely pending per-nation activation) · ● not supported.
+100 chains
M5Wallet enforces Sovereign Financial Infrastructure (SFI) levels at the credential layer. The wallet checks the holder's SFI credential before unlocking any asset-class operation — minted into the TCID and verified by M5Canon on every transaction. All licensing falls under the foundations we support for open standards — no cloud, compute, or big-tech takeover of the rails. Sovereign Banking-as-a-Service applies across the entire stack — every M5 member can offer BaaS to their own members; the class designations below describe asset types, not service availability.
| Class | Type | Required Credential | Chains |
|---|---|---|---|
| M1 | Utility & Services · Utility tokens, compute, royalties, software licensing, exchange fees, service fees, payments using stablecoins. The everyday transactional layer. BTC accepted via Lightning Network. | SFI L1 | Cosmos EVM · Base · SOL · XRP · BTC (Lightning) |
| M2 | Commodities Exchange · CFTC · The open marketplace from farmers market to international exchange. Consumable and hard assets — BTC, gold, energy, agricultural, RECs, water credits, commodity futures, spot. | SFI L2 · CFTC | All public chains · CFTC-compliant venues |
| M3 | Title-Backed Assets · Real estate, vehicles, land, collectables, unique TCIDs, IP rights, airline tickets — non-fungible, one-of-a-kind real-world titled assets. M3 assets can route through M2 or settle as M3 depending on the transaction contract — sale on open market routes M2, direct title transfer stays M3. | SFI L3 | M5Wallet required · TitleChain anchor |
| M4 | Securities & Retail CBDC · Equity, debt, structured products. CEDECO.eth certifies issuance; DTTC for U.S., Euroclear / CSDs globally. Only M4-credentialed BOI entities can issue CBDCs to retail — the consumer-facing CBDC layer lives here, never at M5. | SFI L4 · BOI | M5Wallet + SwiftBRIDGE · BTC L2 activating |
| M5 | Intergovernmental Settlement Only · Government-to-government interbank exchange. Sets finance rules, sovereign currencies, monetary policy. Never retail. Never CBDC to consumers. All chains pending per-nation activation. | SFI L5 · Sovereign | Sovereign chains only · pending nation activation |
M5 provides the base sovereign rails — settlement, identity, custody, on-chain title. Existing payments and custody players are invited to layer value-added services on top. Because crypto settlement is instant and more efficient than legacy rails, partners can offer better insurance, lending, adjudication, and custody at a fraction of legacy fees. Members opt in to whichever services they want — M5 never holds member value.
// npm install @m5bank/x402-middleware @m5bank/sdk import { m5PaymentRequired } from '@m5bank/x402-middleware'; import { M5Client, AssetClass } from '@m5bank/sdk'; const m5 = new M5Client({ tcid: process.env.M5_TCID, chain: 'californiachain.unitedstateschain.eth', sfiLevel: 2, // L2 = M1+M2 access }); app.get('/api/energy-data', m5PaymentRequired({ amount: '0.05', // TC-USD assetClass: AssetClass.M2, wallet: '@energy.m5bou.santamonica.californiachain.eth', }), handler );
# pip install m5bank-x402 m5bank-sdk from m5bank.x402 import m5_payment_required from m5bank.sdk import M5Client, AssetClass m5 = M5Client( tcid = os.environ["M5_TCID"], chain = "californiachain.unitedstateschain.eth", sfi = 2, ) @app.get("/api/energy-data") @m5_payment_required( amount = "0.05", asset_class = AssetClass.M2, wallet = "@energy.m5bou.santamonica.californiachain.eth", ) async def energy_data(req): return {"data": ...}
// cargo add m5bank-x402 m5bank-sdk use m5bank_x402::M5PaymentRequired; use m5bank_sdk::{M5Client, AssetClass}; let m5 = M5Client::builder() .tcid(std::env::var("M5_TCID")?) .chain("californiachain.unitedstateschain.eth") .sfi_level(2) .build()?; let app = Router::new() .route("/api/energy-data", get(handler).layer( M5PaymentRequired::new() .amount("0.05") .asset_class(AssetClass::M2) ) );
Reserve your handle. Activate when your rails open.
The handle is yours from the day you activate IAM — even before mainnet settlement goes live in your jurisdiction. Hardware ships at activation. SDK is open today.