Skip to main content

ArxMint Citadel LogoArxMint: Sovereign Economy Specification

Document Status Draft / Technical Roadmap
ArchitecturePhase 0 - 5

Abstract.

A purely peer-to-peer version of electronic cash and AI agent commerce would allow online payments and autonomous economic activities to be sent directly from one party to another without going through a financial institution or centralized API provider. This document outlines six phases of ArxMint's development, from foundational security hardening through a decentralized merchant payment platform. ArxMint integrates Fedimint, Cashu, Lightning L402, and the Model Context Protocol (MCP) into sovereign Bitcoin payment infrastructure that any merchant can self-host with a three-question wizard. Every task traces back to rigorous core research and 11 self-hosting UX studies, prioritized by security impact.

Table of Contents

Execution Timeline

PHASE 0.0Complete
PHASE 1.0Complete
PHASE 2.0Complete
PHASE 3.0Research / Prototype
PHASE 4.0In Progress
PHASE 5.0Planned

0.0Fortify: Security Hardening

VERIFIED

All P0 security controls shipped and tested. Keyset validation, security tiers, and remote signer config complete.

your sats and data are protected before anything else gets built

0.1 Cashu keyset ID validation[TK_01]

Verify your mint is who it says it is

Verify keyset IDs against mint pubkeys. Prevent NUT-13 deterministic secret collisions — critical for agent wallets.

0.2 Fix Silent Payments status[TK_02]

Honest reporting of what's available on each backend

Honest per-backend SP availability. SP for Fedimint peg-outs requires a federation module (server-side).

0.3 Lightning agent security tiers[TK_03]

Agents get the minimum access they need, nothing more

WATCH_ONLY → PAY_ONLY → ADMIN tiers. Agents default to WATCH_ONLY. Never give agents admin macaroons.

0.4 Remote signer integration[TK_04]

Agent processes never hold signing keys

Signer config and fail-closed validation are shipped. Full isolated signer transport remains to be finalized.

1.0Keystone: Core Architecture

VERIFIED

Core architecture complete: spend routing, merchant onboarding, BCE metrics, NUT-24 paywalls, and scoped agent controls.

merchants can accept payments, wallet auto-picks best way to pay

1.1 NUT-24 ecash paywalls[TK_11]

Pay for services with ecash, not just Lightning

Dual L402 + Cashu flows are implemented; strict production enforcement and deeper testing are still being hardened.

1.2 Spend router[TK_12]

Auto-pick the cheapest, most private way to pay

Auto-select ecash → Lightning → Ark → on-chain based on amount and privacy score.

1.3 BCE metrics dashboard[TK_13]

Real numbers showing community health

Merchant count, active spenders, spend velocity, grant-ready export.

1.4 Merchant onboarding[TK_14]

Step-by-step setup for any local business

Multi-step form, QR codes, POS guidance, directory listings.

1.5 Macaroon bakery[TK_15]

Generate limited-permission keys for different roles

Generate scoped credentials: pay-only, invoice-only, read-only, agent-commerce.

1.6 Ephemeral agent wallets[TK_16]

Temporary wallets that clean up after themselves

In-memory, auto-expire, scoped. No persistent secrets.

1.7 G-Bot integration[TK_17]

Guided federation setup, no DevOps required

Fedimint G-Bot API for guided federation bootstrap with Docker fallback.

1.8 Nostr login (NIP-07)[TK_18]

Sign in with your Nostr identity — no passwords, no database

NIP-07 browser extension auth (Alby, nos2x). Session persists via localStorage. NIP-98 HTTP auth utilities for future API protection.

2.0Spire: Full Privacy + Commerce

VERIFIED

Privacy and commerce stack complete: Fedimint v0.10, NUT-26 QR payments, monitoring, gateway bridge. Ark and CDK remain upstream-blocked.

ecash across multiple mints, tap-to-pay, real-time monitoring

2.1 Fedimint v0.10.0 upgrade[TK_21]

Latest security and performance improvements

Generator paths target "Lighthouse" v0.10.0; root local compose still needs full parity.

2.2 Ark SDK integration[TK_22]

High-privacy off-chain spending layer

SovereignArkClient interface exists with stub-mode behavior pending full upstream integration.

2.3 CDK cloud-native mint[TK_23]

Production-grade mint with real database and monitoring

CDK generation path exists; default local stack still uses Nutshell for quick start.

2.4 Multi-mint support (Coco)[TK_24]

Spread trust across multiple ecash providers

Manager and swap scaffolding are in place; operational hardening and broader coverage continue.

2.5 NUT-26 QR/NFC payments[TK_25]

Scan or tap to pay, just like a credit card

cashu:// URI format for merchant QR codes and payment requests.

2.6 Silent Payments infrastructure[TK_26]

Receive Bitcoin without reusing addresses

Scanner/indexer/key-delegation scaffolding is implemented with remaining protocol-level hardening.

2.7 Monitoring stack[TK_27]

Real-time health dashboards for community operators

Prometheus/Grafana generation is implemented; deployment parity across all compose paths is ongoing.

2.8 Gateway bridge[TK_28]

Ecash automatically converts to Lightning when needed

Bridge flow is implemented with placeholder preimage handling pending final production wiring.

3.0Aether: Advanced Features

Advanced capabilities are in experimental groundwork mode and depend on upstream protocol maturity for production use.

programmable payments, hardware wallet support, tap-to-pay

3.1 Guardian governance[TK_31]

Rules for who runs the shared vault and how

Selection criteria, rotation policy, incident response, quorum management.

3.2 Programmable eCash (STARK)[TK_32]

Smart contracts for ecash — escrow, subscriptions, automated payments

Conditional tokens: escrow, subscriptions, proof-of-service.

3.3 ZK verified reissuance[TK_33]

Cryptographic proof that agent wallets are honest

Audit-log + ZK reissuance for stateless agent wallets.

3.4 Hardware wallet (BIP392)[TK_34]

Sign transactions with your hardware device

SP descriptor support and PSBT spending for hardware signing devices.

3.5 Advanced Cashu (NUT-28)[TK_35]

Multi-mint atomic swaps and proof verification

P2BK, background proof state verification, multi-mint atomic swaps.

3.6 Numo NFC merchant integration[TK_36]

Tap your card to pay at any merchant

Tap-to-pay for merchants using Numo NFC cards.

4.0Citadel: Production + Grants

IN PROGRESS

Pilot deployment in Longmont, CO. Grant applications drafted for OpenSats, HRF, and FBCE. KPI framework and replication playbook ready.

real merchants, real payments, real sats changing hands

4.1 Longmont pilot deployment[TK_41]

Real businesses, real customers, real sats changing hands

Deploy pilot with merchant and user KPIs, uptime targets, and monitored operations.

4.2 Grant applications[TK_42]

Funding to scale from pilot to production

FBCE, OpenSats, and Fedi application templates and workflow support.

4.3 Grant reporting dashboard[TK_43]

Transparent progress tracking for funders

Export monthly/quarterly KPI snapshots and reporting artifacts.

4.4 Replication playbook[TK_44]

Step-by-step guide for any community to copy this

Open-source "BCE in a box" playbook generated from pilot configuration.

4.5 Multi-city federation[TK_45]

Connect Longmont to other cities on the same rails

Expand pilot model into multi-city commerce via multi-mint and Lightning bridge routes.

5.0Bazaar: Decentralized Merchant Platform

A self-hosted, non-custodial Stripe alternative. Three-question wizard provisions a merchant payment node in under 15 minutes — no Docker, SSH, or DNS knowledge required. Legally protected as open-source software + optional non-custodial infrastructure services. ArxMint never touches funds.

any merchant runs their own payment node — zero fees, zero middlemen

5.1 Local auth tokens + scoped macaroons[TK_51]

Your node, your keys — programmatic access with sandbox mode

L402 macaroon-based auth tokens generated on the merchant's own node. Scoped permissions (read/invoice/pay/admin), key rotation, rate limits. Non-custodial by design.

5.2 Webhook engine (local)[TK_52]

Get notified instantly when a customer pays — on your own infrastructure

Webhook engine runs on the merchant's node, watching their own LND/Cashu for invoice settlements. HMAC-SHA256 signed payloads, exponential backoff retry, delivery logs.

5.3 Self-hosted checkout page[TK_53]

A payment link on your own domain — no code required

Payment page served from the merchant's node. Invoices generated by their own LND. QR code, real-time SSE status, auto-redirect on completion. ArxMint provides the software; merchant hosts it.

5.4 Payment status API + real-time updates[TK_54]

Know exactly when your customer paid

GET /payments/:id on the merchant's own node. SSE for real-time push, WebSocket for POS. Cursor-paginated payment history. All data stays local.

5.5 Client-side SDK + React components[TK_55]

Add payments to any website in 10 lines of code

@arxmint/js and @arxmint/react — connects to the merchant's own endpoint, not a central server. PayButton, CheckoutForm, QRPayment components.

5.6 LNURL-pay + Lightning Address[TK_56]

name@pay.merchant.com — scan and pay at any register

Lightning Address and LNURL-pay served from the merchant's own domain. Static QR codes for POS. NFC tag provisioning via Numo. No intermediary.

5.7 Merchant dashboard (self-hosted)[TK_57]

See every payment, manage your node, track your revenue

Self-hosted dashboard with payments, analytics, auth token management, webhook config, node status. No data leaves the merchant's infrastructure.

5.8 Merchant deploy wizard[TK_58]

Three questions, fifteen minutes — your payment node is live

arxmint merchant init asks three questions (where to run, store name, online or POS), then provisions a complete merchant node: LND (Neutrino — no chain sync), Cashu mint, checkout, dashboard, managed subdomain (storename.arxmint.cloud), auto-HTTPS, and LSP-bootstrapped liquidity. Cloud deploy buttons for DigitalOcean, Vultr, Hetzner. The merchant never sees Docker or SSH.

5.9 Public merchant directory[TK_59]

Customers find you — searchable by category and location

Community-hosted merchant directory. Self-registration via CLI. Search by category, location, payment methods. The only Phase 5 item safe to host centrally (informational, no funds).

5.10 Idempotency + production hardening[TK_510]

No double charges, no duplicate records, hardened for the open internet

Idempotency-Key header on all payment endpoints. Structured error codes. Caddy auto-HTTPS, CSP headers, rate limiting, firewall rules generated by setup wizard.

5.11 Merchant node lifecycle[TK_511]

Updates, backups, and disaster recovery — handled automatically

Three sub-systems: (a) Appliance update engine — signed stack BOMs with auto-rollback on failed health checks, canary rings for staged rollout. (b) Zero-knowledge encrypted backups — LND SCB event-driven on every channel change, Cashu mint DB encrypted with seed-derived key, automated restore rehearsal. (c) One-click restore — fresh host + seed phrase = full recovery.

5.12 Home node packaging (Umbrel + StartOS)[TK_512]

One-click install from your home node app store

Package the merchant stack for Umbrel and StartOS app stores. Umbrel is the fastest target — Docker Compose maps directly to its packaging format. Checkout endpoints public via App Proxy, admin behind Umbrel auth. StartOS as secondary with richer ops UX.

5.13 Mobile merchant remote control[TK_513]

Manage your node from your phone — the VPS is invisible

React Native app as remote control for the merchant's VPS node. POS terminal, QR generation, daily sales, push notifications on invoice settlement. Wallet unlock via push notification (non-custodial — secret goes to node, never ArxMint). Near-term: PWA dashboard (5.7) covers 80%. Lite mode: LDK on mobile via Breez SDK for pop-up shops — no VPS needed.

Appendix A: Contribute

ArxMint is open source infrastructure. Review the specification, audit the code, or submit proposals for the active phase.