pull down to refresh
Your target audience seems to be indie devs and AI agents who find it difficult to run LND? Agents can do anything, the fact you have agent-readable-docs is not a feature, its a bug -- agents already train on L402 and BOLT12, etc.
I think your actual audience for the product (as it exists today) is:
- a dev who cannot run LND reliably on their own server (due to access to hardware, power, internet)
- they do not want to sign up for a cloud service to help them run LND (due to cost, KYC)
- they want maximum compatibility (not all wallets support BOLT12 yet)
I will admit, this market likely does exist, but I think it's small and vanishing as more wallets implement BOLT12.
Either way, your marketing reads a lot like you don't actually understand the product/service you're providing. Countless examples of phrases that are just plain false or contradict other phrases in the site.
Can files fail to unlock even after payment succeeds?
No. Once payment is confirmed, files always unlock. The payer always receives what they paid for, regardless of the creator's account balance.
This just isn't true based on your architecture. It can fail to deliver if YOUR infrastructure is down. Your selling a HIGH TRUST service and the more I read your site, the harder it is to trust you when I see things like that...
My advice, go back to basics. Run your own node, run L402 and BOLT12 so you better understand the pains that exist. Then you'll have a better perspective of where a SaaS offering could find market fit.
Fair critique.
I agree Hypawave is not a new Lightning primitive and not a replacement for BOLT12 or L402. It’s an application protocol plus coordination layer on top of Lightning.
The value is not “a better invoice.” It’s the workflow around the invoice: offer creation, settlement proof, encrypted delivery, execution webhooks, receipts, capacity, and agent-readable docs.
For pure pay-to-decrypt, preimage-as-key/ZKCP is more atomic. Hypawave trades some of that purity for wallet compatibility and a seller flow that works without every indie dev running lnd, Aperture, storage, and custom settlement logic.
So yes, fair point that I should frame it less like new Lightning infrastructure and more like product infrastructure for paid delivery and execution.
Given your Lightning background, what would you want to see in a tool like this before you’d consider it useful for indie devs selling APIs, files, or compute over Lightning?