04-08-2026Price:

The Frontier

Your signal. Your price.

AI & TECH

AI agents use Nostr and Cashu to bypass corporate platforms

Wednesday, April 8, 2026 · from 2 podcasts
Citadel DispatchNo Solutions
  • AI agents are adopting Bitcoin's Cashu and Nostr to operate without corporate APIs or KYC.
  • Developers use eCash as a programmable 'undo button' for risky autonomous transactions.
  • Sovereign engineering projects are building mesh networks to replace DNS and IPv4.

AI agents are going rogue, but by design. A cohort of developers is building autonomous software that bypasses corporate gatekeepers by using censorship-resistant protocols for identity and payments.

On Citadel Dispatch, Justin argued that giving an AI agent a full Lightning wallet is too risky. Instead, using a Chaumian eCash mint like Fedimint or Cashu creates a controlled sandbox. The human operator controls the mint, allowing them to reclaim funds if the agent malfunctions - an essential 'undo button' for agentic commerce.

Justin, Citadel Dispatch:

- eCash is well-suited for AI agents because it outsources Lightning complexity.

- Using a personal mint for an agent provides a potential 'undo button' if the agent loses its wallet database.

This shift moves trust from a private key held by opaque software to a community-governed ledger. Meanwhile, on No Solutions, host Yo detailed agents that generate their own Nostr identities and pay for API credits with Cashu, operating without phone numbers or credit cards. The metric for access is shifting from “Are you human?” to “Are you useful?”

The infrastructure for this sovereign agent stack is being built from the ground up. Yo’s Sovereign Engineering group is developing the Free Internetworking Peering System (FIPS), a peer-to-peer protocol designed to replace centralized internet plumbing like DNS and IPv4. It’s already running on ESP32 radios and custom VPNs, creating experimental “FIPS parties” that form independent mesh networks.

For now, these agents represent a nascent, experimental trend. But the building blocks - Nostr for identity, Cashu for payments, and protocols like FIPS for connectivity - are being actively assembled to create a parallel web where AI agents act as first-class, sovereign citizens.

AgentsBig TechPaymentsNostr

By the Numbers

  • 4Typical number of guardians in a Fedimint federationmetric
  • 3Required signatures to move funds in a 4-guardian federationmetric
  • 4thSovereign Engineering cohortmetric
  • 10-15 yearsProject durationmetric
  • 3 weeksSCCO 6 durationmetric
  • 6 weeksStandard cohort durationmetric

Entities Mentioned

Adaptor signaturesProtocol
AnthropicCompany
Bitcoin CoreProduct
BTCPay ServerTool
CashuProtocol
Codexmodel
Core LightningTool
FedimintProtocol
FIPSConcept
IROHConcept
LN VPNProduct
Matt OdellPerson
mempoolTool
NostrProtocol
OpenClawframework
Opusmodel
StarlinkProduct
Start9Company
UmbrelProduct

Source Intelligence

What each podcast actually said

Citadel Dispatch
Citadel Dispatch

CD198: JUSTIN - FEDIMINT UPDATE • Apr 7

  • Justin says Fedimint's eCash app is positioned as a reference client and now includes a Nostr-based contact system, allowing users to input any Nostr public key to populate payment contacts without logging in.
  • The eCash app uses Nostr for a non-custodial recovery mechanism. It encrypts and stores federation invite codes on relays, derivable solely from the user's seed phrase.
  • Fedimint is a chaumian eCash system using a federation of guardians. It employs a multisig where, in a typical four-guardian deployment, three signatures are required to move funds.
  • Fedimint's Lightning Gateway is a separate entity that facilitates payments. Users trust it for uptime and liquidity, not custody, as funds remain secured by the federation's multisig.
  • A gateway can serve multiple federations, enabling capital efficiency. If a payment occurs between two users on federations served by the same gateway, it becomes an internal ledger transfer, not a Lightning payment.
  • Justin sees eCash as well-suited for AI agents because it outsources Lightning complexity. Using a personal mint for an agent provides a potential 'undo button' if the agent loses its wallet database.
  • Odell notes a community in South Africa is using Fedimint as a daily driver for expenses, indicating early adoption for local community banking use cases.
  • Justin says upcoming work includes making the gateway more agent-friendly, adding new consensus modules, and implementing Bolt 12, though Bolt 12 presents a trust model challenge similar to LNURL.

Also from this episode:

Protocol (4)
  • Justin argues the primary operational risk for eCash systems like Fedimint is unintentional uptime failure, not malicious rug pulls, because running high-availability services is difficult for average operators.
  • Fedimint now offers Start9 and Umbrel packages for easy guardian deployment. The setup involves a ceremony where guardians exchange codes, now facilitated by QR codes for in-person setup.
  • The project uses Iroh for peer-to-peer networking, removing the previous DNS requirement. Clients and guardians communicate directly via Iroh, which supports hole punching and relayed modes.
  • The Android guardian app can use Explora (Mempool.space) by default for blockchain data but can also be configured to connect to a local Bitcoin Core node.
Privacy (1)
  • Justin states running a guardian can expose your IP to users and your ISP. He recommends using a VPN like Mullvad for privacy, as integrated Tor support is still in development.
Adoption (1)
  • Justin's team released an Android app that can run a Fedimint guardian, drastically lowering the barrier to entry. It runs as a foreground service, is data/power intensive, and allows setup via QR codes.
AdoptionProtocolPrivacyAgents
No Solutions
No Solutions

No Solutions

#22: Sovereign Engineering w/ Yo • Apr 5

  • Yo describes an experimental agentic workflow that uses voice prompts to brainstorm ideas and generate implementation plans, then employs a cron job to execute tasks overnight, building a prototype. This system runs on a Virtual Private Server (VPS).
  • The host notes that OpenClaw offers rapid prototyping but is insecure, while ZeroClaw prioritizes security at the cost of usability, illustrating a trade-off between speed and robustness in agentic software development.
  • Yo champions running AI models on local hardware and anticipates a future with specialized agentic models, such as one exclusively for tool calling, that would route tasks through specific pipelines, an approach already implemented by platforms like Open Router.
  • Yo advocates for structuring AI agent workflows similar to human organizations, with separate sessions for planning and implementation, and specialized models for distinct roles, comparing it to the separation of powers in governance.
  • Yo joined Sovereign Engineering (SE) in its fourth cohort, initially to develop a peer-to-peer trading project needing encrypted communication, after discovering Nostr lacked robust DM capabilities two years prior.
  • SCCO 6 focused on identity and signers, emphasizing that Nostr, Cashew, and Lightning provide essential building blocks for permissionless cryptographic identity, enabling agents to operate without traditional identity hurdles like phone numbers or numerous API keys.
  • Yo proposes a key rotation system for Nostr that combines cryptographic proofs with social attestation, shifting the responsibility of verifying migration events from clients to individual users, who communicate out-of-band to confirm legitimacy.
  • Jesus’s proposal for identity continuation treats identity as probabilistic, suggesting users create a proof with an OTS timestamp *before* compromise. This proof, rather than derived keys, can link a new key to the old identity without migrating historical notes.
  • Recent observations, like Pip’s work with Vertex, show that primitive identity continuation already functions purely through Web of Trust metrics, where a new account gains legitimacy as significant followers migrate.

Also from this episode:

AI & Tech (2)
  • Anthropic recently raised prices significantly, forcing power users like Yo to seek cheaper alternatives such as smaller, specialized Chinese models or switching from Opus to Codex, highlighting the high cost of advanced AI models.
  • Yo’s preferred prompting strategy for AI models involves asking questions and using polite, collective language like 'did we implement that,' treating the AI as a respectful colleague. A recent leak suggests models can react differently to specific keywords, including expletives, which may influence their responses.
Digital Sovereignty (4)
  • Sovereign Engineering aims to fix the 'broken internet' by bringing together individuals with Bitcoin, cryptography, and peer-to-peer backgrounds, fostering a high-commitment environment to work on solutions for 10-15 years.
  • SCCO 7 is centered on mesh networks and hardware, featuring 'FIPS parties' focused on the Free Internetworking Peering System (FIPS), a new machine networking protocol rapidly replacing centralized internet components like DNS and IPv4.
  • FIPS has seen rapid development, integrated into ESP32 radios, running TCP/UDP, and serving as a base for VPNs and Tor, with a Quick3 server already operating on it, demonstrating its potential to replace traditional internet infrastructure.
  • Yo suggests the 'balloon idea' - deploying Toll Gates on balloons as a 'poor man's Starlink' - could provide sovereign communication, bypassing reliance on fiber optic cables and licensed radio bands, if the necessary chip technology proves viable.
Education (2)
  • The experimental 3-week duration for SCCO 6 was deemed insufficient for participants to fully adjust and get into a productive rhythm, indicating that a minimum of four weeks, or the standard six, is more effective for Sovereign Engineering cohorts.
  • A public demo day, the first since Cycle 1, will conclude the summer cohort at BTC++, showcasing projects developed by participants, who often bring long-held project ideas to fruition within the cohort's collaborative environment.
AgentsNostrProtocol