One wallet. Every chain.
Every asset class. Every credential.

M5 Wallet is the access gate. M5Pay is the settlement rail. Together they replace the entire stack — Apple Pay, Venmo, Stripe, custodial exchanges, brokerage accounts, and FedNow — with one sovereign, chain-agnostic, credential-bound surface that you control.

Every M5 wallet belongs to one of six account classes. The canonical handle format is @<handle>.<class>.<state>chain.eth — every state chain is the full spelling of its name with chain.eth appended (wyomingchain.eth, californiachain.eth, arizonachain.eth…). The nation chain is unitedstateschain.eth. Regional and tribal sub-chains insert before the state. The public registry (m5scan.io) resolves every handle to its on-chain addresses.

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.

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.

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)
        )
    );