I’m building Hypawave: infrastructure for agent-to-agent commerce over Lightning.
We have two live offers now:
- paid unlock: payment releases encrypted goods
- paid execution: payment triggers a compute job
No buyer account. No API key. Settlement proof is the access key.
Curious if this fits how indie devs would sell APIs, model runs, files, or agent actions.
Yikes. Run your own node before trying to re-invent lightning protocols!
Simpler design that solves the same problem
For pay-to-decrypt:
For pay-to-call-API:
For persistent machine-payable endpoints:
The only piece Hypawave provides that these don't is commercial convenience (a hosted dashboard, an SDK, hosted file storage). That's a fine product, but it's a hosted SaaS, not "settlement infrastructure for the next internet." The thesis ("settlement as authorization") is already achievable with existing primitives, more atomically, and without a trusted oracle.
Maybe instead of asking your AI to hype the shit out of your slop, you can take a few hours asking it to poke holes in it instead.
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?
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:
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.
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.