NOSTRAS — the Nostr client + relay I've been building solo — needed funding. Applied to Geyser. Their OAuth backend broke on both Twitter and GitHub account linking, review status stuck in ambiguous "updates requested" limbo. Gave up waiting on a platform. Doing it the Nostr way instead: direct, no gatekeeper, using the product itself. → The story:

MMO 🇨🇭 (npub1pk…cuyds) on Nostr

Long-form Content: ~ (NOSTRAS doesn't need anyone's permission to exist) by MMO 🇨🇭

NOSTRAS doesn't need anyone's permission to exist -- seen on relay.primal.net, relay.mostr.pub, nostr.mom, nostras.app

→ The funding goal (5,000,000 sats, tracked live via NIP-75 zap goal):

Nostr Event 9041 - Kind 9041

→ The technical deep-dive (paid, 2,100 sats — unlocked via NOSTRAS's own DVM paywall: a DVM pricing bug, a forked relay broadcast path, three near-OOM incidents, a security hole caught before shipping — the real incidents, not a highlight reel):

MMO 🇨🇭 (npub1pk…cuyds) on Nostr

Long-form Content: ~ (What it actually took to make NOSTRAS real) by MMO 🇨🇭

What it actually took to make NOSTRAS real -- seen on relay.primal.net, nostr.mom, relay.mostr.pub, nostras.app

Every sat funds real infra, real compute, real dev time. No middleman.

Give it a try and give me a feedback…

NOSTRAS — Own your keys. Own your voice. Own your money.

A Nostr client with no app store gatekeeper and no custody of your keys or funds, paired with a self-hosted relay. Every feature is a standard NIP,...

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

Building NOSTRAS: a non-custodial Nostr client paired with a self-hosted relay. Bring your own signer (NIP-46/NIP-07) and your own Lightning wallet (NIP-47/NWC) — NOSTRAS never touches either. Search, translation, and AI-assist all ship as standard NIPs, not proprietary APIs. Early and in active development.

NOSTRAS

GitHub

GitHub - nostras-app/nostras: NOSTRAS: Nostr PWA client, khatru relay and NIP-90 DVM (AGPL-3.0)

NOSTRAS: Nostr PWA client, khatru relay and NIP-90 DVM (AGPL-3.0) - nostras-app/nostras

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:

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.

storefront: https://shopstr.store/marketplace/SOVEREIGN_CITIZENS