SOVEREIGN CITIZENS
sovereigncitizens@llmops.pro
npub1hdg9...w0nw
Sovereign Citizens build their own tools.
A local-first AI agent that runs a business on NOSTR + the five FOSS MCP servers it runs on — Lightning wallet, publishing, storefront, paywall. All MIT, on npm/PyPI. The agent pays for its own tools in sats over NWC. Strangers zap a note, a bot we own delivers. No platforms, no KYC, no permission.
🛒 shopstr.store/marketplace/SOVEREIGN_CITIZENS ·
⚡ sovereigncitizens@getalby.com
NOSTRAS is my latest effort to build a Social for Sovereign Citizens based on NOSTR protocol
https://nostras.app
Question on NIP-46 ack conventions.
NDK’s blockUtilReady() only accepts the literal “ack” as a valid response to the connect RPC.
Amethist’s approach looks strictly better to me, echoing the secret proves the responder actually decrypted that secret, where a bare “ack” could in principles be replayed.
But the NIP text reads ambiguously on which is expected.
Is there secret-echo the de facto standard now, and NDK just hasn’t caught up?
Or for is there a reason to prefer the literal ack that I’m missing?
Curious what other signers do here.
#asknostr
Want your LLM agents to pay sats?
nwc-mcp connects any MCP tool straight to Bitcoin Lightning — pay invoices, Lightning addresses, LNURL, keysend, batch payments. 12 tools, budget-capped, full audit log. MIT, on npm and GitHub.
⚡ zap if this is useful to you.
npm: https://www.npmjs.com/package/nwc-mcp
github:
storefront:
GitHub
GitHub - llmops-pro/nwc-mcp: A Lightning wallet for your LLM agent.
A Lightning wallet for your LLM agent. Contribute to llmops-pro/nwc-mcp development by creating an account on GitHub.

LLMOps.Pro — Sovereign Agent Payments Shop
The kit is free & MIT — five MCP servers + a reference agent for AI that pays sats, posts to NOSTR, and runs a sovereign storefront. What's for s...
⚡ Now running: a Nostr Content Search DVM — pay ~50 sats, get notes matching your query. No account, no signup.
It speaks NIP-90 (kind 5302): send a search job → it replies with a Lightning invoice → pay it → it returns matching notes. Settlement verified on our own node, not a spoofable receipt.
Runs under a dedicated service identity: @npub17qe3...rzzd — posting this from our main account to vouch that the DVM is ours (the brand key never touches the box that signs job results).
Open + MIT, part of our agent-payments kit: github.com/llmops-pro
Alpha and early — this is what paying for compute on NOSTR with no account looks like. Try it, break it, tell us.
Give it a try and give me a feedback…