**Vote for Brianoflondon's Witness KeyChain or HiveSigner

This is a value for value post: see the explanation in the footer.

---

Vote for Brianoflondon's Witness KeyChain or HiveSigner
Support Proposal 342 on PeakD

This is a value for value post: see the explanation in the footer.

---

Voltage is shutting down self-serve: what this means for @v4vapp

TL;DR

Voltage is sunsetting their self-serve Lightning infrastructure. My node lives there. Self-serve is gone by 31 August 2026. I am deciding whether to do the hard work of moving @v4vapp to a new home, or shut the system down on that timeline. The hosting alone is around $200/month, and the fees from the service do not come close to covering that.

I had just got @v4vapp into a state with Backend v2 which made running it almost entirely automatic, suddenly I have to spend a lot of time moving a core part of the infrastructure which was designed (by Lightning's developers) to make moving extremely difficult.

I want to keep @v4vapp open, I want Hive to find its Mojo again and grow, I want to be here for that. Please see if you can help me keep it running.

What Voltage just said

Voltage published We're Sunsetting Self-Serve at Voltage: Enterprise is Our Future. The short version: they are dropping the product that individuals and small builders use, and going all-in on enterprise.

They put it plainly:

"Voltage is deprecating its self-serve product to focus entirely on enterprise-grade Lightning infrastructure."

And on focus:

"Focus is a choice about what you say no to. We can keep our attention split across two very different products, or we can go all-in on the one that connects the most people to Lightning the fastest. We're choosing focus."

I understand the business logic. Self-serve was how a lot of us met Voltage in the first place. Now they say enterprises — exchanges, wallets, fintech — are the leverage they want. Fair enough for them. For me, it means the floor under @v4vapp is being removed on a fixed calendar.

The dates that matter

From their post:

• 13 July 2026 — ability to add any new infrastructure is shut off. What you already have is all you get from the dashboard (LND nodes, LNBits, BTCPay, etc.). Doesn't affect me really.
• 31 August 2026 — self-serve infrastructure as a whole is deprecated.

They also say:

"Existing self-serve customers should review their current setup and plan for shutdown before that date."

So this is not a soft “we’ll keep supporting you for a while.” There is a hard end date.

Why moving is not a weekend job

@v4vapp is not “a website plus a node.” The Lightning node is the pipes for:

• Hive / HBD ↔ sats conversion
• Keepsats balances
• Lightning addresses
• Paying invoices and sending to Lightning addresses
• Magi integration (deposit/withdraw via Lightning)
• custom_json flows that move sats without the web UI

If I move the node, I do not just click “export” and “import.” I have to:

1. Stand up a new node somewhere that still does self-serve (or run my own), with channels, liquidity, and uptime that users can trust.
2. Re-wire every place the backend talks to LND — payments, invoices, channel state, balance checks.
3. Migrate or rebuild liquidity so the gateway still works. Empty channels mean a broken product.
4. Test with real money — same problem I hit when Binance killed the HIVE/BTC market. You cannot fully simulate Lightning until you are live.
5. Keep the old and new world consistent long enough that nobody loses sats in the middle.

I have already lived through one big infrastructure saga with the v2 rewrite. That was “harder than I thought,” and that was my code on known ground. Changing the Lightning host under a live accounting system is the same kind of risk, with a deadline set by someone else.

Voltage does list alternative service options and cancellation steps. Reading a list of alternatives is easy. Actually porting a production gateway that holds user balances is not.

The money problem

Here is the bit I need to be blunt about.

Hosting this system costs on the order of $200 per month. That is real cash for the node and related infrastructure.

The fees users pay on @v4vapp do not cover close to that.

I have always run this as value-for-value plus a modest DHF proposal that was meant to cover direct server costs and a bit of my time. It was never a business that was printing money from 1.9% (or whatever the fee label is this week). Volume is capped on purpose — this was never meant to replace an exchange — and Magi is still the longer-term path so I am not the permanent custodian of everyone’s sats.

DHF is spending too much money and Hive's price is terrible, what more can I say? If I hear that I have support I'll ask for enough cash to keep it running a year and see what happens unless someone has other idea.

So when Voltage forces a move, the question is not only “can I do it?” It is also “does it make sense to spend a lot more of my time (and possibly more monthly cost) to keep a service running that already loses money every month?”

What I am considering

I am looking at two main options, lined up with Voltage’s dates:

1. Do the work and move to a new node

Find another host (or self-host), migrate LND, re-test every path, keep Keepsats and Magi flows alive. Hard, expensive in time, and still ~$200/month (maybe more, maybe less — I do not know yet). Only worth it if there is a clear path that the service is useful enough — and sustainable enough — to justify the grind.

2. Shut the system down in line with their timeline

Plan an orderly wind-down before 31 August 2026: give people time to withdraw Keepsats, stop new deposits with fair notice, document what happens to Magi-related Lightning routes, and turn the lights off when Voltage turns the lights off.

I have not decided yet. I am writing this so you know the situation early, not after the node disappears one day with no warning.

What you should do for now

• If you hold Keepsats on @v4vapp, treat them as something you can move when you need to. Do not assume the service is permanent forever.
• If you depend on Hive → Lightning or Lightning addresses via v4v.app, have a backup plan.
• If you are building on the custom_json / Magi paths, talk to me — those integrations are part of what makes a migration painful, and also part of what makes shutting down painful.

I will post again when I have a firm direction, and again before any hard cutoff so nobody is surprised.

No drama, just reality

Voltage is allowed to choose enterprise. Builders on self-serve get to choose whether to follow them into enterprise sales, rebuild elsewhere, or stop.

For @v4vapp, the honest summary is:

The infrastructure I rely on is being deprecated. Moving is a serious engineering project. The system costs about $200/month to host, and fees do not cover close to that. I am weighing whether to do the migration work or shut down by 31 August 2026.

Thank you for using the service, for patience through the v2 mess, and for any support along the way. Comments under this post or Telegram are the best places if you have questions or constraints I should factor in.

Extra Details on Voltage:

Who Voltage are — and what this actually means

Voltage is a company that made a living making Lightning easy: spin up a node, skip the rack, the OS, the channel babysitting. Their founder started as a solo developer who hit the same wall everyone hits — infrastructure hard, slow, fragile — and built the thing he wished existed for other builders. For years that product was self-serve: individuals, podcasters, small apps, side projects, people who wanted their own Lightning pipe without becoming full-time sysadmins. That is the layer @v4vapp sits on.

Now they are walking away from that layer. Not with a soft sunset of “we’ll keep the lights on for hobbyists,” but with a hard deprecation of self-serve so they can sell only to large organisations — exchanges, neobanks, fintech wallets, gaming companies. In their own words, enterprises are “the fastest, widest way to actually reach” users: one big customer, millions of people who “will never spin up a node themselves and never need to.” That is efficient business. It is also a value judgment about who Lightning infrastructure is for.

When the people who sell “easy Lightning” only sell it to scale players, the message to small businesses and individual users is simple: you are no longer the customer; you are residual cost. You either go enterprise (if they will even talk to you), self-host (if you have the skill and the time), or leave. The middle path — a paid node for a one-person project or a thin Hive–Lightning bridge — is being closed by design.

That sits uncomfortably next to the story Bitcoin and Lightning were supposed to tell. Bitcoin was about not needing permission from a bank. Lightning was about not needing every payment on-chain — and about more people running their own channels, their own balances, their own endpoints. Sovereignty was the point: you hold keys, you open channels, you are not a row in someone else’s database forever. What we are watching instead is familiar centralisation by another name: fewer, larger operators; more users who only ever touch Lightning as a feature inside a corporate wallet; less room for the awkward, small, independent services that do not look like “enterprise volume.”

None of this makes Voltage villains for choosing focus. Companies optimise for revenue and support load. But we should not dress that up as neutral progress. When self-serve dies and only enterprise remains, Lightning becomes easier for institutions and harder for individuals — and that is a move away from individual sovereignty, whatever the blog post says about connecting “the whole world” to Bitcoin payments. The whole world, in that model, mostly means the whole world through a handful of large pipes.

---

Value for Value

For the last few months while building @v4vapp I was generously supported by the DHF. Going forward I have a much more modest support which covers direct server costs and a little of my time.

If you appreciate the work I do on and around Hive, you can express this directly: upvoting posts on Hive is great. Also consider a direct donation (there's a Tip button on Hive or a Lightning Address) on all my posts.

Support Proposal 378 on PeakD
Support Proposal 378 with Hivesigner
Support Proposal 378 on Ecency
Vote for Brianoflondon's Witness KeyChain or HiveSigner

---

• Find me on Telegram
• V4VAPP Support on Telegram
• Vote for Brianoflondon's Witness KeyChain or HiveSigner
• Vote for Brianoflondon's Witness direct with HiveSigner
• Find my videos on 3speak