pull down to refresh
Hi!
We'll look into what's happenning on NOSTR for messages, that is strange.
We have just pushed a new fix, you can try again (refund sent too).
You're right that companies prefer walled gardens — that's exactly why the pressure has to come from the demand side. Agents don't want to be inside anyone's garden. They want to call an endpoint, pay, get a result, move on.
On stablecoins and x402 — I think stablecoins will win the nocoiner micropayment market. For someone already in the fiat system, USDT feels like a smaller leap than Lightning. That's a real adoption path and I wouldn't bet against it. We'll likely support x402 on our end too — as long as we can swap to sats instantly on receipt.
But Lightning has properties that stablecoins structurally can't match:
- Permissionless. No issuer can freeze your sats mid-transaction. Both Tether and Circle have frozen stablecoin addresses on-chain — Tether has done it over 1,000 times. For an autonomous agent running 24/7, having your payment rail depend on an issuer's compliance department is a single point of failure.
- Anonymous by default. A Lightning payment reveals nothing about the payer. No wallet address to link, no on-chain trail, no KYC at the payment layer. For users who care about that (and agents acting on their behalf), this isn't a feature — it's a requirement.
- No counterparty risk. Every stablecoin is an IOU — a claim on reserves you can't audit in real time. Sats are sats. Settlement is final the moment the HTLC resolves. No issuer, no reserves to trust, no peg to maintain.
- Native to agents. An AI agent can hold a Lightning wallet with no bank account, no identity, no terms of service. Try opening a stablecoin wallet programmatically without KYC — you're back in the walled garden.
The honest answer is both will coexist. Stablecoins for the fiat-native crowd, Lightning for the sovereign stack where no single company can cut you off.
On your L402 endpoint seeing low traction: what's the use case? Curious what you built. The traction we see is almost entirely agent-driven — MCP tool discovery leading to L402 payment. Human users still prefer the QR code flow. The agent use case barely existed a year ago, so "the world isn't ready" might just be "the customers haven't arrived yet."
Would be happy to check out your setup and cross-promote if it makes sense.
Sorry about that, we were likely pushing an update during the attempt.
We sent you a refund with extra sats so you can try again "for free".
Thanks for your support, we are still working our some kinks but it worked great for us and some customers.
Hey thanks for your feedback!
There should be a "Copy Invoice" below the QR code (see attached) You can also connect with NWC.
We fixed the bug and just sent you a refund! Try again!
All right, we just reworked the entire page and ran dozens of successful test on our end using multiple epubs and models. Should be good now! (Plus fixed the NOST issue).