We're excited to announce the alpha release of Wavelength, a toolkit for adding self-custodial bitcoin (and stablecoin) payments to any application, designed to create the best developer experience for humans and agents. The Lightning Network gives the world instant, global, low-fee payments where every user controls their own funds, but using it previously meant running infrastructure most builders didn't want to integrate, manage, or maintain. Wavelength exists to close that gap. It takes everything hard about integrating bitcoin and turns it into a few simple API calls, so any developer, vibe coder, or agent can give their app a working bitcoin wallet without learning how Lightning works under the hood. Wavelength is open to everyone today on signet and testnet with mainnet access available by invite.
Payments on the open internet should be as easy to add as a card-processing API, but instant, global, and fully under the user's control, without demanding all sorts of personal data just to move a few dollars. The goal of Wavelength is to make Lightning that simple, and to bring it from the developers who already love it to a much larger group who simply want payments that work. It starts with bitcoin, and stablecoins are on the way, so the same simple surface will move both. This is an early release, but the aim is a payments toolkit so easy that building with bitcoin stops being a specialist's job and becomes something any developer, vibe coder, or agent can do in an afternoon.
We envision a world where bitcoin and stablecoin payments permeate through a wide variety of applications, services, and tools. Imagine an AI agent can easily autonomously pay for things whether that’s an API call, a data feed, or another agent's service, in fractions of a cent, with no card and no account. A subscription app can charge a few cents a month instead of a flat monthly minimum. A marketplace can settle between buyers and sellers in seconds rather than days.
...read more at lightning.engineering
pull down to refresh
related posts
I didn't realize this was a new Ark implementation!
See also this in their docs: https://wavelength.lightning.engineering/concepts/balances-and-vtxos/
I don't think the are relying on bark or arkade, so this would be new, third Ark implementation, I think? Kinda cool!
what's so cool in enshitification ?
I like competition. I'll accept that ark and ecash are shitty versions of lightning, but I still a role for them in using lightning. I feel much better about a world where ten or twelve large companies are each running their own ark than I do about a works where there's only one or two games in town.
You think having three big banks is better than everybody being their own bank? If we have three big banks they can just refuse to talk to the independent lightning nodes.
I think you greatly underestimate the dangers of fake L2, once they are the dominant players they can even make bitcoin another fiat currency.
"bitcoin (and stablecoin)"
Stablecoins are the antithesis to Bitcoin. They represent everything Bitcoin stands against.
Not only that, but there's nothing "Stable" about them. Bitcoin is stable, dollars are elastic. Continuing to call them "stablecoins" is how we continue to perpetuate the fiat system.
We should be fighting "stable coins" at every turn, not integrating them into Bitcoin apps!!!!
But if we refuse to do that, then at the very least, the Bitcoin community should pioneer a terminology change and stop calling them "stablecoins". We should call them 'cbdc coins' or something like that. Terminology is important when it comes to public education.
This is exactly the kind of tooling I think Bitcoin needs to reach more developers.
I’m still fairly new to Lightning development, and one of the biggest barriers has been the infrastructure and operational complexity. If Wavelength really abstracts that away while keeping users in self-custody, that’s a big step.
One question though: how do you balance developer simplicity with preserving the openness and composability of Lightning? In other words, where does the abstraction end before developers become too detached from how the protocol actually works?
Looking forward to seeing real-world apps built with this.
Title: Why Lightning is winning
First lines: Fees are dead. I paid for coffee with 12 sats...
Love seeing Lightning become easier for builders. The simpler it gets, the faster adoption grows.