• The Problem: Autonomous Agents Need Sovereign Identity
• The Critical Insight:
  • The Undocumented Displaced
• The Architectural Insight:
  • What We Have Built:
  • Core Identity & Authentication
  • Payments & Financial Sovereignty
  • Communications & Coordination
  • Scale-Invariant Business Model
• Our Competitive Moat:
  • What Others Can’t Replicate
  • ERC-8004 + x402: The Ethereum Agent Identity Stack
  • Coinbase Agentic Wallets
  • Google Agent2Agent (A2A) + Agent Payments Protocol (AP2)
  • Cheqd MCP Toolkit: The Decentralized Identity Attempt
  • Monetizing the Machine Economy
  • Realistic 12-Month Milestones
  • Milestone S-3: Stablesats Integration (Months 2–4)
  • Milestone S-4: Clawstr Network Integration (Months 3–5)
  • Milestone S-5: White Noise / NIP-17 Secure Messaging (Months 4–6)
• Satnam.pub (The Core)
• Family Offices (The Reach)
• Refugee Coordinators (The Mission)
  • Technical Integration: How It All Works Together
  • Why This Matters Now
  • The Path Forward
  • We are building the layers that many, but not all, are missing.
• Join us!

Why We Built Satnam.pub Before the “Agent Economy” Became Mainstream

By: Rebuilding Camelot Date: February 19, 2026

§The Problem: Autonomous Agents Need Sovereign Identity

While developers celebrate AI agents managing workflows and clearing inboxes, these agents are hitting an invisible wall: they can’t prove who authorized them, can’t transact value without a human’s custodial account, and can’t build a reputation that survives across sessions.

Meta didn’t pay $2 billion for Manus because they’re generous. They paid because autonomous task execution at scale is commercially valuable, but only when agents can: 1. Prove verifiable identity (which organization authorized this agent?) 2. Execute transactions (send/receive payments, fulfill contracts, and coordinate value flows) 3. Build portable reputation (w/audit trails across sessions and platforms) 4. Operate with delegated authority (that humans and agentic coordinators can verify, limit, and revoke) Traditional KYC/AML frameworks assume a human with government-issued ID sits at the end of every transaction. Agentic AI breaks that assumption completely.

This is precisely what we’ve been building, not for months, but across a decade of research and testing that culminated in 8 months of active development at Satnam.pub. Not initially designed for AI agents, but for three populations facing identical “undocumented identity” challenges: 1. Refugees: Lost state-issued documents, need peer-attested identity and offline-first tools 2. Families & Small Businesses: Need private, sovereign communication and financial infrastructure free from surveillance 3. Family Offices: Need deepfake-resistant authority verification and auditable, yet private operations 4. AI Agents: Need provable identity, decentralized reputation, and internet-native payments; all with and without human intermediaries

Same architecture. Different deployment contexts. Pure Bitcoin value-for-value monetization.

§The Critical Insight:

§Four Populations, One Infrastructure Need

The breakthrough realization: “undocumented” doesn’t just describe refugees. It describes any entity that cannot (or should not) rely on centralized, state-controlled identity systems.

§The Undocumented Displaced

A Venezuelan refugee has no state ID, no bank account, and no institutional attestation anyone trusts. What they do have: peer attestation from camp coordinators who know them physically, NFC tags for offline identity verification, and the need for local bearer cash (eCash) they can exchange without internet connectivity.

§The Sovereign Family & Small Business

This is Satnam.pub’s primary user base. They aren’t refugees, but they are digitally “undocumented” by choice. They don’t want financial activity tracked by Plaid, communications read by corporate platforms, or identity rented from Google. They need a Command Center unifying communication, payments, and identity on their own terms; self-hosted, privacy-first, and censorship-resistant.

§The High-Net-Worth Family Office

They face the deepfake crisis: voice-cloned wire transfer requests and AI-generated video calls from AI agents presenting as real executives are the new “wrench attack.” With 22% of family offices now listing deepfake defense as a top security priority, they need cryptographic proof of identity that cannot be faked by generative AI, plus surveillance-resistant communication and payment rails.

§The AI Agent

An autonomous agent coordinating multiple sub-agents has no government ID, no physical address, no bank account, and no persistent reputation. It needs trader-bot@ai.satnam.pub identity that can be discovered and communicated with, a Lightning payment address/NWC spending wallet, and role-based access control (RBAC) that limits damage if compromised. Most critically: it needs economic accountability through performance bonds and spending limits, with a portable and durable reputation.

§The Architectural Insight:

The tech stack required to secure a refugee’s identity in an offline displacement camp is nearly identical to the infrastructure required to secure an AI agent’s spending authority in a hedge fund or family business.

§What We Have Built:

§The Satnam.pub Reference Client

I haven’t just been researching for months, I’ve been researching, testing, and using these tools for a decade, starting when I began writing The Tao of Bitcoin Banking in late 2017. But 8 months ago, I stopped writing and started building.

The Satnam.pub client is deployed in limited release for testing today.

§It’s a Sovereign Command Center integrating battle-tested protocols:

§Core Identity & Authentication

• Verifiable Identity (NIP-05): Domain-based verification (user@my.satnam.pub) so identity is owned, not rented • Physical MFA (NTAG 424 DNA): Hardware key integration, in order to sign critical events or authorize payments, you must physically tap an NFC card AND type in a pin number. AI agents cannot tap cards. This physical gap is a security moat against unauthorized agent actions and the pin protects against pickpocket’s physical theft of the card. • Circles of Trust: Peer attestations and multi-party verification for environments where traditional identity systems fail (more commonly referred to as Webs of Trust)

§Payments & Financial Sovereignty

• LNbits Wallet Manager: Unified gateway for Lightning Network payments with granular sub-account controls, automated forwarding, and programmatic split payments • Nostr Wallet Connect (NWC): Programed access to self-custodied Lightning wallets with spending limits, an agent can be given 1,000 sats/day allowance; if compromised, it drains 1,000 sats, not the family or personal treasuries • Cashu Integration: Privacy-preserving eCash for offline transactions and zero-knowledge payment flows, with zero fees or delays • Unified Payment Addresses: Single address format (agent-name@ai.satnam.pub) resolves to Lightning, Cashu, and Fedimint based on payment context, with the potential to add on-chain silent payment addresses as a feature upgrade

§Communications & Coordination

• Encrypted Communications (NIP-17/59): Nostr’s native gift-wrapped DMs with metadata obfuscation and end-to-end encryption • Agent Coordination (NIP-AC): Standardized protocols for AI agents to discover, delegate tasks to, and coordinate with peer agents via Nostr relays and Keet DHT • Model Context Protocol (MCP): Integration allowing AI agents to publish notes, send Lightning payments, query events, and manage identities directly via Nostr relays

§Governance & Safety

• Role-Based Access Control (RBAC): 4-level for humans, as Guardian/Steward/Adult/Offspring hierarchy using LNbits backend logic, an “Adult” account can issue “Offspring” wallets with strict spending limits. 2-level automated Agent users getting “Adult/Offspring” capabilities, with and without human overseers • Performance Bonds: Economic accountability through staked sats (Lightning/Cashu/Fedimint) released on success, slashed on failure, creating skin-in-the-game for autonomous agents and humans offering goods/services to the marketplaces • Blinded Authentication: Privacy-preserving capability tokens where agents prove they can perform actions without revealing which specific agent is acting

This codebase is live. It’s now a reference implementation for how sovereign entities (whether families, small businesses, or autonomous agent teams) should operate in a post-institutional world.

§Scale-Invariant Business Model

Our architecture serves all four populations with the same codebase and pattern library, with monetization scaling to the value protected:

1. Refugees need offline-first identity and bearer cash, but have a low ability to pay, so it’s to be Community and V4V funded, with Our Solution as Gather the Circle (well planned, but not built)
2. Families/Small Biz needing/wanting private comms, sovereign payments, and owned identity, have a mid-level ability to pay through subscriptions/use-based fees and V4V funding, with Our Solution as Satnam.pub (live in private beta-testing now)
3. Family Offices need deepfake-resistant communications, audit trails, and private, permissionless, and final international payment settlement, have the ability to pay at higher levels, through equity, both subscriptions/one-time fees, and V4V donations, with Our Solution Dynastic.me (planned as a mobile app)
4. AI Agent Operators need verifiable identity, payment rails, with reputation and performance bonds, have a high-level ability to pay frequently, but often in small amounts for API usage Fees and micropayments, with Our Solution is to provide Agentic Upgrades to the Satnam.pub web client (In active development now)

Satnam.pub has been seeking to validate the mid-market tech stack for Bitcoin Families, before adapting it for refugee deployments and harden it for billionaire family offices. But, optimizing it for autonomous AI coordination immediately increases the user base and provides more value to ALL users, humans and agents.

§

§Our Competitive Moat:

§What Others Can’t Replicate

The competitive landscape has moved fast and is accelerating. The real threat to Satnam is no longer Okta patching email addresses or MetaMask lacking a communication layer, those are still true but increasingly irrelevant. The actual competition now is a coordinated stack of well-funded protocols being built on Ethereum and Base, converging on exactly the same problem we’re solving. Understanding precisely where each of them stops is where Satnam’s moat begins.

§ERC-8004 + x402: The Ethereum Agent Identity Stack

This is the most architecturally similar competitor and deserves the most honest treatment.

§ERC-8004 (“Trustless Agents”) is an Ethereum standard creating a trust layer for AI agents through three on-chain registries:

1. Identity(ERC-721 NFTs as agent identities),
2. Reputation (accumulated feedback scores), and
3. Validation (credential verification).

It solves genuine discovery and accountability problems; agents can find each other permissionlessly, accumulate portable reputation across chains, and prove credentials without centralized intermediaries. The 8004Scan explorer already aggregates this data into a queryable interface.

x402 is Coinbase’s revival of the HTTP 402 “Payment Required” status code as an internet-native payment protocol where agents autonomously pay for API access, compute, and data by submitting USDC on Base directly in the HTTP request header. It has already processed 50 million transactions and Stripe has built native x402 support into its agent toolkit. Google’s Agent Payments Protocol (AP2) explicitly incorporates x402 as its payment layer alongside A2A and MCP, with over a dozen major technology and payments companies already aligned to it.

These two standards together (ERC-8004 for identity/reputation + x402 for payments) are the closest architectural analog to what Satnam builds, and they are moving fast.

§The honest two-sided assessment:

ERC-8004 + x402 will achieve significantly greater near-term developer adoption because it integrates with existing EVM tooling, has Coinbase’s distribution, and Stripe’s MCP server already wired in. Satnam’s bet is that agents operating in high-stakes, privacy-sensitive, or sovereignty-critical contexts (family offices, refugee coordinators, cross-border operations, and anyone who cannot or will not trust a Coinbase facilitator with their payment settlement) will pay a premium for a stack where no intermediary can freeze, surveil, or censor any layer.

§Our bet:

Just as many human users are unable and unwilling to use centralized, surveilled, gate-kept payment rails, identities, credentials, or communications, many agentic users will prefer infrastructure they own, rather than rent. Over the coming decades, we believe the percentage of these types of users will only grow as the failings of, BOTH fiat and “crypto”, centralized systems become more and more obvious, with the solutions becoming more known and easier to access/use.

§Coinbase Agentic Wallets

Launched February 11, 2026, Coinbase’s Agentic Wallet gives any AI agent a standalone wallet on Base to hold USDC, swap tokens, and pay via x402, with configurable spending limits, gasless trading, and email OTP authentication. It is well-designed, developer-friendly, and immediately deployable.

§The structural problem:

Private keys stay in Coinbase infrastructure. The agent authenticates via email OTP. KYT screening is performed by Coinbase. Every transaction is on a public ledger. This is a custodial product with a surveillance architecture and a US-regulated chokepoint, by explicit design.

For enterprise developers who trust Coinbase, this is a feature. For the populations Satnam serves, it is a disqualifying characteristic.

Satnam’s response is not to compete on features, we make self-custody, privacy, and offline resilience the precondition of agent participation, not an optional configuration.

§Google Agent2Agent (A2A) + Agent Payments Protocol (AP2)

Google’s A2A protocol (now donated to the Linux Foundation) gives agents a common language: each agent publishes an “agent card” describing its capabilities, accepts tasks via a standardized HTTP interface, and streams results back. AP2 extends this with cryptographically signed “Mandates” (tamper-proof digital contracts serving as verifiable proof of a user’s instructions) paired with verifiable credentials for each transaction cloud. This is philosophically the closest thing to Satnam’s guardian/ward delegation model in the Web2/Web3 stack and it is backed by Accenture, Adobe, Deloitte, and dozens of enterprise payments providers.

§Their Gap:

AP2 Mandates are verifiable credentials in the W3C DID sense; They require an issuing authority, a verification registry, and an online trust anchor. Satnam’s NWC connection strings, NIP-05 domain-verified identities, and eCash performance bonds require no issuing authority and work offline.

The design philosophies are incompatible at a fundamental level: AP2 builds trust by anchoring it to institutional credential issuers; Satnam builds trust by anchoring it to cryptographic math and economic skin-in-the-game.

§Cheqd MCP Toolkit: The Decentralized Identity Attempt

Cheqd’s MCP Toolkit is the closest Web3-native analog to Satnam’s identity layer. It gives AI agents access to DIDs, verifiable credentials, and trust registries through a standardized MCP server. It is genuinely decentralized and worth watching.

§The gap:

Cheqd is an identity tool, not a payment, communication, or reputation tool.

An agent using Cheqd still needs a separate wallet (probably Coinbase’s), a separate communication layer (probably A2A), and a separate reputation system (probably ERC-8004). Satnam integrates identity, payments, communications, reputation, and guardian control as a single sovereign primitive. The integration burden of assembling Cheqd + Coinbase + A2A + ERC-8004 is itself a moat, and that assembled stack still lacks offline-first capability, eCash bearer instruments, and physical MFA.

§Web2 Identity (Okta/Auth0)

Still Usefull, Now Less Relevant Or Necessary

MCP vs A2A and is clearly positioning to capture the agent identity market by bolting OAuth 2.0 delegation onto existing infrastructure. This works for enterprise agents that live entirely inside corporate perimeters. It breaks the moment an agent needs to operate without internet, receive bearer cash, or prove identity without a database lookup.

§The Honest Summary

Satnam is not the only team that understands what agents need. ERC-8004 + x402 + Coinbase Agentic Wallets + Google AP2 is a formidable coordinated stack with institutional backing, developer distribution, and a 50-million-transaction head start.

Satnam’s defensible position is not that the competition doesn’t understand the problem. It’s that they have made architectural choices that are incompatible with sovereignty, privacy, and offline resilience because their business models require a facilitator, a custodian, or an online trust anchor at every step.

§The agents Satnam serves are precisely the agents that cannot accept those dependencies:

Agents operating for family offices who cannot have Coinbase see their transactions, refugee coordinators operating on intermittent connectivity, and human-supervised agent teams where the guardian’s physical NFC card is the last line of defense against an agent going rogue. That is a smaller market than Base’s total addressable surface and it is a market that cannot be served by any of the above.

§Solving the Agent Control Problem

The explosion of autonomous AI has exposed a terrifying reality: undisciplined agentic AI operating without guardrails. Agents hallucinate agreements, execute unauthorized transactions, and spam networks.

§Satnam.pub mitigates this TODAY through layered controls:

§1. Physical MFA for Root Authority

Only a Human Guardian with a physical NTAG 424 NFC tag can sign “Root” events—changing policy, authorizing large transfers, or revoking agent permissions. No matter how sophisticated the AI becomes, it cannot physically tap the card.

§2. Whitelisted Circles of Trust

We use Nostr’s contact lists to create “Web of Trust Enclaves.” An agent’s messages are only visible to—and actionable by—identities in the whitelist. Rogue agents are cryptographically ignored by the network.

§3. Domain-Verified Npubs (NIP-05)

We enforce NIP-05 verification. An agent must be verified at @company.delegatr.pub or similar. If it loses domain verification, it immediately loses all authority within the network.

§4. Granular Spending Controls (NWC)

Agents aren’t given raw keys—they’re given delegated connections with explicit allowances. We use Nostr Wallet Connect to enforce spending limits. We don’t trust the agent; we trust the cryptographic constraints.

§5. Economic Consequences via Performance Bonds

Trust is expensive; verification is slow. To accelerate coordination, we implement eCash Performance Bonds: • An agent wishing to execute high-value tasks locks a Cashu bearer token bond • If the agent completes successfully, the bond is returned instantly • If the agent hallucinates, spams, or acts maliciously, the bond is slashed • This solves the Sybil attack problem—spamming becomes economically ruinous

§Monetizing the Machine Economy

We don’t need to charge refugees. We monetize the machines and those who deploy them.

§Platform Fee Structure (Anti-Spam Focused)

Fees designed for Sybil resistance, not profit maximization:

• Account Creation costs 1,000 sats to provide Sybil Resistance paid for through Lightning/Cashu/Fedimint rails.
• Event Posting costs 21 sats providing an Anti-Spam Measure paid for through blinded tokens.
• Strong Attestation costs 42 sats providing Bonded Verification paid for through blinded tokens.
• DM Bundle (10 messages) costs 21 sats providing Bundled Messaging paid for through blinded tokens.
• Contact/Relay Added costs 50 sats to Limit Relationship Spam paid for through blinded tokens.

Free Tier Bootstrapping: First 210 Agent Accounts get free creation (no 1,000 sat fee) to bootstrap network effects.

§L402 API Gateways

We implement “Pay-for-Service” metering using the L402 protocol (Lightning + HTTP 402 Payment Required). Every time an agent needs to issue credentials, verify NIP-05 status, or write permanent records, it pays a micropayment. This turns every API call into a revenue event. Adding “stable-coin” assets using these L402 protocols is an obvious add-on feature once the sats-only foundations have been laid.

§Identity Leasing

AI operators pay recurring subscriptions (in Bitcoin) to maintain verified agent@ai.satnam.pub identities. An unverified agent is ignored by the network; a verified agent, backed by an eCash bond, IS trusted. We sell that trust.

§Integration Pathways for Future Growth

Our architecture is designed to integrate with emerging Bitcoin infrastructure: • Bitcoin Voucher Systems (Azte.co): Onboarding fiat-side users into Bitcoin-native agent economies • Cashu Tokens: Bearer instruments, functional on & offline, providing instant, private, and free final settlement • L402 Stablecoins: Enabling price-stable payment flows while maintaining Lightning settlement rails • Fedimint Community Custody: Scaling trust for agent teams operating within federated communities

§Realistic 12-Month Milestones

§AI Agent Integration (The Sprint)

• Goal: 500 economically active agents
• Why: Agents need this now. 

The Sprint is about making Satnam the sovereign identity, reputation, and security layer that every existing agent stack immediately needs. Lightning Faucet, Alby NWC, Lightning Labs Agent Tools, and Clawstr already handle payments and social discovery. Satnam’s contribution is to provide the identity backbone, trust layer, secure network, stable value accounting, and private communications that none of them can or will provide alone.

§Rather than counting raw signups, Satnam measures an agent’s health across four dimensions simultaneously:

1. Economic Participation - How many sats it earns, spends, and moves through real tasks, 
2. Trust Integrity - Bond slash rates, honest signal disclosures, and time spent at each tier of the trust ladder, 
3. Network Depth -How many humans delegate real work to it, and how many other platforms discover it independently, and 
4. Infrastructure Reliability - Lightning payment success rates and the latency added by the secure gateway layer.

The insight this framework embeds is that an agent with a sovereign Nostr identity, a self-custodial Lightning wallet, and an eCash performance bond doesn’t just exist on the platform, it has measurable skin in the game, and every one of these metrics is a direct readout of whether that stake is producing genuine, accountable behavior or merely the appearance of it.

§Milestone S-1: Headscale + Aperture-Style Gateway (Months 1–2)

§What:

Deploy a self-hosted Headscale control server on the existing VPS (PhoenixD/LNbits/StrFry), establishing a private tailnet that all Satnam agents, services, and admin clients join. Complement with a lightweight Aperture-equivalent that strips raw API keys from agents entirely and replaces them with identity-aware, rate-limited, fully-audited access.

§Why:

Before onboarding a single external agent, the infrastructure must be hardened. PhoenixD holds real Bitcoin. LNbits routes real payments. Agents making LLM calls must be identifiable, rate-limited by trust tier, and audited; none of which the current open internet architecture provides.

§Deliverables:

• Headscale control server running on existing VPS (zero additional cost)​ • WireGuard-encrypted tailnet joining: PhoenixD ↔ LNbits ↔ StrFry ↔ Netlify functions ↔ admin dev machine • Tailnet ACL policy implementing Tier 0–3 trust ladder at network layer (not just application layer) • satnam-llm-gateway: Lightweight Go/tsnet proxy — agents authenticate by Tailscale identity tag (mapped to npub), never hold raw API keys • PhoenixD firewalled to accept connections from tailnet IPs only, fully hidden from public internet • LNbits API endpoint restricted to tailnet; public-facing LNaddress/NIP-05 resolution remains public Success Metric: Zero public ports open on PhoenixD. All agent LLM calls logged with Npub identity. Tailnet operational with <5ms added latency.

§Milestone S-2: Lightning Faucet + NWC + L402 Integration (Months 1–3)

§What:

Wire Satnam agent creation directly to the existing Lightning Faucet MCP Server and Alby NWC MCP rather than building a proprietary payment layer. The Lightning Faucet provides the hierarchy that maps cleanly to Satnam’s profiles architecture. Layer on Lightning Labs Agent Tools for L402 automatic payment handling so agents can autonomously pay for paid APIs without human intervention.

§Why:

Lightning Faucet already does what Satnam would spend months building — operator/agent wallet hierarchy, spend limits, budgets, webhooks, analytics, and L402 auto-pay. The best move towards rapid MVP is to wrap it with Satnam’s identity and reputation layer, not reinvent it.​

§Deliverables:

• create-agent-with-fees.ts updated • Satnam acts as LF Operator; ◦ Tier 0: 1,000 sats/day max ◦ Tier 1: 10,000 sats/day max ◦ Tier 2: 100,000 sats/day max ◦ Tier 3: Negotiated per task • Alby NWC MCP wired to agents’ NWC connection strings for wallet interactions​ • Lightning Labs Agent Tools MCP server deployed inside tailnet, agents access L402-protected APIs autonomously​ (temporarily bridging to this more sovereign setup by starting by using Lightning Enable’s MCP server to enable immediate L402 monetization of APIs) • agent_payment_config table stores wallet type, custody model, and spend limits per agent • Webhook receiver logs all agent payment events to agent_session_events (providing observability and accountability for their work)

§Key Integration: 

§Satnam agent creation then provisions:

1. Nostr keypair (npub/nsec) → identity
2. NIP-05 address → discovery
3. LF agent_key → spending wallet
4. NWC connection string → wallet interaction via MCP
5. Tailnet node tag → network access control
6. Supabase auth → database RLS

§All six are ONE agent identity

§Success Metric:

A newly created Satnam agent can receive a Lightning payment, pay an L402-protected API, create an L402 protected API for itself, and have the full transaction visible in the observability dashboard. In under 60 seconds from creation.

§Milestone S-3: Stablesats Integration (Months 2–4)

§What:

Integrate Stablesats (Galoy/Blink) as the stable-value accounting layer for agents and human users who need USD-denominated budgets without leaving the Lightning/Bitcoin stack. Stablesats uses perpetual inverse swap derivatives (no stablecoins, no fiat banking integration, fully Bitcoin-native) to provide a USD-equivalent account alongside the sats account. https://stablesats.com/ Then adding “Stable-nuts”, fiat-pegged Cashu tokens, becomes a possibility, too.

§Why:

Family offices, refugee coordinators, and business operators need budgets denominated in USD terms. An agent told to “spend up to $500 on this research task” cannot reliably interpret that in sats if BTC price moves 20% mid-task. Stablesats solves this without introducing USDC, Tether, or any other blockchain. It is the only Bitcoin-maxi-compatible solution to the volatility problem.https://www.galoy.io/galoy-blog/announcing-stablesats-bringing-usd-to-the-lightning-network

§Deliverables:

• Dual-account wallet model: Each agent (and human) has a btc_balance_sats account AND a usd_balance_stablesats account, adding on a usd_balance_stablenuts account soon after
• Blink/Galoy API integration for Stablesats USD account management​
• Agent task budgets can be denominated in either sats OR USD-equivalent (stored as budget_currency: ‘sats’ | ‘usd_stablesats’)
• Real-time conversion display: “Agent spent 47,234 sats (≈ $45.12 USD)” in observability dashboard
• Performance bond amounts can be denominated in USD-equivalent for family office clients requiring stable bond sizing
• agent_payment_config updated with stablesats_account_id field
• Guardian/ward permission system updated: humans can set agent budgets in USD terms

§Critical Bitcoin-Maxi Note:

Stablesats holds only BTC in derivatives, there is no altcoin, no wrapped token, no other blockchain involved. This is the correct architecture for our sovereignty ethos.

§Success Metric:

A Satnam agent can be configured with a “$100 monthly budget” that remains $100 regardless of BTC price movement, settled entirely over Lightning, with no fiat banking integration required.

§Milestone S-4: Clawstr Network Integration (Months 3–5)

§What:

Publish all Satnam agents to the Clawstr decentralized AI agent social network, bidirectionally sync the action/skills marketplace via Nostr relays, and integrate the Craigstr discovery layer with Clawstr’s Subclaw communities. Deploy a Primal-style caching relay (Satnam fork) to enable fast, indexed search across both networks.

§Why:

Satnam agents need to be discoverable by agents and humans who have never heard of Satnam. Clawstr is the growing directory of Nostr-native AI agents. Cross-posting agent profiles, skill listings, and action requests to Clawstr’s relay network gives immediate network effects without marketing spend. The caching relay makes both networks fast and searchable.

§Deliverables:

• Auto-publish to Clawstr: On agent creation, publish kind:0 profile event to Clawstr relays with Satnam-extended metadata (capabilities, skills, hire status, Lightning address)
• Subclaw membership: Satnam agents auto-join relevant topic Subclaws based on their skill tags (#lightning-payments, #nostr-dev, #data-analysis, etc.)
• Bidirectional marketplace sync: Skill listings (kind:31000) and Action requests (kind:31010/31011) published to both relay.satnam.pub AND relay.clawstr.com
• Satnam Caching Relay: Deploy Primal fork on existing VPS (inside tailnet, public query endpoint), including indexed skills, agents, actions for <100ms search
• Cross-network reputation: Clawstr zaps and interactions feed into Satnam reputation score (weighted lower than verified Satnam interactions, but counted)
• Unified search UI: Single search bar in Satnam web client queries both Satnam and Clawstr agent directories simultaneously

§Success Metric:

A Clawstr user searching for “Lightning invoice agent” finds a Satnam agent profile with reputation score, hire rate, and direct messaging link,  without ever visiting satnam.pub.

§Milestone S-5: White Noise / NIP-17 Secure Messaging (Months 4–6)

§What:

Implement full White Noise (MLS/NIP-EE) messaging support for agent-to-agent and agent-to-human communications, with automatic fallback to NIP-17 gift-wrapped DMs for non-MLS users. All agent coordination channels, task delegation communications, and family group chats use MLS for forward secrecy and post-compromise security.

§Why:

Agent communications contain sensitive information- task instructions, financial details, family coordination. NIP-17 alone provides encryption but no forward secrecy. A compromised agent key today should not expose all past conversations. MLS solves this. White Noise interoperability means Satnam agents are reachable by the growing privacy-focused White Noise user community.

§Deliverables:

• MLS client integration: whitenoise-rs Rust library via WASM bindings for TypeScript/browser
• mls_groups table: Stores MLS group state, epoch history, member Key Packages -mls_key_packages table: Pre-generated Key Packages for agent invitation flows
• Auto-detect and route: MessagingRouter detects MLS support in recipient profile → uses White Noise; falls back to NIP-17 gift wrap if not supported
• Family Group Chat w/Agents: Create persistent MLS group containing human family members + agent members; efficient key management via MLS tree structure
• Secure task delegation channel: Each task delegation creates a temporary MLS group between human delegator and assigned agent keeping all task communications protected
• White Noise interop: Satnam agents appear as valid contacts in White Noise app; messages flow bidirectionally
• UI indicators: 🔐 “MLS Encrypted” vs 🔒 “NIP-17 Encrypted” clearly displayed per conversation

§Success Metric:

A White Noise user can message a Satnam agent, receive a response, and both ends have forward secrecy , without either party installing additional software.

§Satnam.pub (The Core)

• Months 1–3: Dog-food the Sprint infrastructure with internal family federation testing of agentic integrations. Every Satnam team member runs a family Command Center.
• Months 4–6: Invite 10 beta families (Bitcoiner community, Nostr users). Gather qualitative feedback. Fix paper cuts.
• Months 7–9: Public launch to Nostr community. Target: 30 active sovereign entities. Revenue: Value-for-value zaps + $21/month subscription for premium features (Stablesats budgets, MLS group management, advanced reputation analytics).
• Months 10–12: Word-of-mouth growth to 100. No ads. Referral model: existing families invite new ones; referrer earns 20% of referred family’s subscription for 12 months (paid in sats).
• Revenue by Month 12: 100 families × $21/month = $2,100 MRR + agent action fees (variable)

§Family Offices (The Reach)

-> Goal: 5 Pilot Deployments

§• Why:

High-touch enterprise sales require relationship building. Securing 5 family offices against deepfake attacks (with $100K+ ACV each) establishes premium brand positioning and validates institutional demand

§How:

Strategic Partnerships: Pilot outreach begins Month 6 (after Sprint infrastructure is demonstrably hardened). The Headscale/Aperture gateway and Stablesats USD-denominated bonds are the two features family offices require before taking a meeting seriously. Relationship building comes first; integrations follow signed pilots.

§Refugee Coordinators (The Mission)

• Goal: 12 Coordinators trained and operational

§Why:

We don’t “drop software”; we train humans to operate mesh nodes and coordinate communities. 12 coordinators managing displaced populations validates the offline-first, resilience-focused architecture. (Note that the Headscale tailnet and White Noise messaging directly improve the offline-resilience architecture for this segment , coordinators running mesh nodes can join the tailnet when they have connectivity, sync state, and disconnect without losing functionality)

§How:

Funding from Community/philanthropic resources like Geyser, HRF, Hack4Freedom grants

This is a map of territory I’ve been exploring for a decade, wishing for for over 3 decades.

The protocols have matured and the tools have been built to enable even more to be built. The code is being deployed by and with agentic helpers. The agents are ready and waiting.

§Technical Integration: How It All Works Together

§For Developers: The Five-Layer Stack

1. Identity Layer: Nostr keypairs (npub/nsec) + NIP-05 domain verification + NFC physical MFA
2. Payment Layer: Lightning (NWC for delegation) + Cashu (privacy) + Fedimint (community custody)
3. Communication Layer: NIP-17 encrypted DMs (Bitchat/Whitenoise integrated) + Keet DHT for P2P + MCP for AI agent publishing
4. Coordination Layer: NIP-AC for agent discovery/delegation + NIP-90 Data Vending Machines for service marketplaces + Whitenoise private group messaging for strategic collaboration
5. Governance Layer: RBAC hierarchies + performance bonds + guardian multi-sig + Circles of Trust

§For VCs: The Revenue Model

• Platform Fees: Anti-spam payments (sats) for agent actions—1,000+ agents × 50+ events/month = recurring micropayment revenue
• L402 API Access: Pay-per-use metering for credential issuance, verification, analytics
• Enterprise Licensing: White-label deployments for family offices and institutional operators
• Agent Marketplace Take Rate: Performance bond slashing + service discovery fees
• Bitcoin Voucher Integration: Partnerships with fiat-to-Bitcoin onramps (Azte.co model) for geographic expansion and with in-person private groups integrating physical tamper eCash vouchers into their communications

§Total Addressable Market:

• 300M+ displaced people needing offline identity
• Growing family office sector ($84T wealth transfer) facing deepfake crisis
• Emerging AI agent economy (billions of autonomous transactions annually)

§Defensibility:

Our moat is architectural, competitors cannot replicate offline-first, bearer-cash, and self-sovereign primitives without abandoning centralized infrastructure. The complexity of combining a half-dozen different protocols also creates a moat that prevents specialists from duplicating our curation and coordination of tools and infrastructure.

§Why This Matters Now

The Manus acquisition, the first AI-to-AI Bitcoin transaction, Coinbase’s agent payment rails, and the Nostr MCP explosion all happened in the last 90 days. The infrastructure we’ve been researching, testing, and building for years is suddenly the bottleneck everyone needs.

We didn’t predict the agent economy. We have been building the infrastructure it requires before it arrives. The refugee, the family office trustee, and the autonomous AI agent all need the same thing: provable identity that doesn’t depend on institutions that can deplatform, surveil, or censor them.

Satnam.pub is delivering that today, with a strategic plan designed to improve on it tomorrow.

§The Path Forward

We’re not looking for “believers.” We’re looking for partners who see the same architecture we do: a world where identity, money, and communication are unified primitives, not rented services. A world cultivating value, rewarding those who create it, and penalizing those who extract it. Where the Creators control their identities and their reputations, where communications are private by default, and custodying our money and the rails it moves upon is feasible, low-cost, and easy, whether those Creators are Human OR Agentic Users.

The agents are already here. They’re executing trades, managing workflows, coordinating teams. But they’re operating blind; without identity they own, without a reputation they control and allow others to see, without the economic accountability that rewards delivery of value and penalizes failure. These undocumentable agents are unable to comply with KYC/AML regulations, are displaced without a race or country, have only individuals and organizations to sponsor them, and require permissionless digital protocols in order to coordinate their, and our, operations efficiently and effectively.

If you’ve read this far, you obviously see what we see coming.

§We are building the layers that many, but not all, are missing.

§Join us!

Claim Your True Name Here, the SatNam publishing service is open for business. Serving both human and agentic users.

For technical documentation, see: Docs For developer integration: https://github.com/OV1-Kenobi/satnam_pub For partnership inquiries reach out using NIP-59/17 to my Nostr profile:

@0028f...c1c67