V4V.app will be down Wednesday 11th February 10am UTC - NOW WORKING
ALL STOP... FOUND AN ISSUE ... THE SITE ISN'T RETURN CHANGE ON HIVE TRANSACTIONS, I NEED TO FIGURE THIS OUT.
The time has come to perform the big v2 upgrade to the v4v.app system.
Updates
Wednesday 18th Feb 12:51 UTC
This is proving a lot harder than I thought. I'm working like crazy but I need to take a deep breath and eat something....
I will fix this but I just need time, sorry.
Tuesday 17th 08:05
I've had a note from @privex so I will probably be down for a bit starting at 09:00 UTC (10:00 CET).
.... from @privex : Our Sweden datacenter has scheduled a maintenance window that will affect your server tomorrow, February 17th at approximately 9am CET. The outage is expected to last until roughly 10am CET, during which your server will be shutdown. The server will be given a soft shutdown command, and after about 15 minutes, a power-off. To prevent any potential data loss or consistency issues, we strongly recommend that you shut down your server before the maintenance window begins.
Tuesday 17th 06:06
IT'S WORKING!!!!! That was an ordeal but hopefully v4v.app is working. You may have to reload to get rid of the annoying pop up but it will disappear soon.
I will write a proper post about the system very soon.
Monday 16th 15:13 UTC
🛑 After being optimistic this morning, I was all set to turn things on an hour ago when one last check and I think I messed something up with the choice of which currency to send when receiving sats. I'm still working.
Monday 16th 06:50 UTC
🛑 Still a little niggle with the way I'm handling custom_json instructions. Need to clear this and I will go live. Stand by.
Sunday 15th 16:49 UTC
🤞 That's it, I'm ready to open this up. Baring any crazy stuff I find tonigt, I'm going to turn it on tomorrow morning probably around 07:00 UTC.
Saturday 14th 19:02 UTC
I've been working all day. I'm largely completed with the Binance replacement system but it is all a bit harder than it could be.
Tomorrow..... I hope.
Friday 13th 16:35 UTC
😀
It's all going to be OK! I found a solution using a different way of trading on Binance, I can't test it on Binance's testnet but it's working and Claude helped me write 1000+ lines of new code to do it a new way.
I've got more testing I need to do but I really hope I can be live tomorrow!
Shabbat Shalom everyone, it's going to be OK!
Friday 13th 107 UTC
😀 Turns out there might be a solution using Binance's swap system and Claude Opus 4.6 in CoPilot is busy re-writing a huge pile of code. If that works I can breath again and hopefully open tomorrow morning.
Friday 13th 13:3:15 UTC
I was just thinking I needed to come here and write that I was almost done setting up v2 and that in light of the fact that I only want to open things up when I can sit and watch what happens for a few hours, I would open tomorrow morning.
However: it now appears that something very troubling has happened. Binance have closed the BTC/Hive market which is essential for me.
Without me having a way to counter trade I really can't afford to run v4v.app. Obviously I can return sats to everyone, but conversions would be a significant risk for me.
I'm going to have to think about this and discuss with @magi.network how close they are to having a reliable pool.
Thursday 12th 15:23 UTC
After battling with Lightning for a while (it eventually started working) I've realised I needed to add some pretty significant functionality to the code concerning bad accounts.
This was prompted by what happened last night.
I'm determined to get the service right and reliable so I'm not rushing. As soon as I can it will be back up but that may not be today.
Thursday 12th 09:21 UTC
Of course nothing with Lightning is easy. As I'm working on the tweaks and changes before I bring the new system online, my development Lightning server (I run two Lightning servers) has decided to stop working and I'm waiting for it to recover itself.
2026-02-12 09:18:28.608 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2026-02-12 09:18:29.492 [INF] CHDB: DB compaction of /data/.lnd/data/graph/mainnet/channel.db successful, 269164544 -> 218710016 bytes (gain=1.23x)
2026-02-12 09:18:29.521 [INF] CHDB: Swapping old DB file from /data/.lnd/data/graph/mainnet/temp-dont-use.db to /data/.lnd/data/graph/mainnet/channel.db
2026-02-12 09:18:29.643 [INF] CHDB: Compacting database file at /data/.lnd/data/chain/bitcoin/mainnet/macaroons.db
2026-02-12 09:18:29.679 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
2026-02-12 09:18:29.694 [INF] CHDB: DB compaction of /data/.lnd/data/chain/bitcoin/mainnet/macaroons.db successful, 32768 -> 32768 bytes (gain=1.00x)
2026-02-12 09:18:29.697 [INF] CHDB: Swapping old DB file from /data/.lnd/data/chain/bitcoin/mainnet/temp-dont-use.db to /data/.lnd/data/chain/bitcoin/mainnet/macaroons.db
2026-02-12 09:18:29.713 [INF] CHDB: Compacting database file at /data/.lnd/data/graph/mainnet/sphinxreplay.db
2026-02-12 09:18:29.752 [INF] CHDB: DB compaction of /data/.lnd/data/graph/mainnet/sphinxreplay.db successful, 32768 -> 32768 bytes (gain=1.00x)
2026-02-12 09:18:29.754 [INF] CHDB: Swapping old DB file from /data/.lnd/data/graph/mainnet/temp-dont-use.db to /data/.lnd/data/graph/mainnet/sphinxreplay.db
2026-02-12 09:18:29.761 [INF] CHDB: Compacting database file at /data/.lnd/data/graph/mainnet/wtclient.db
2026-02-12 09:18:29.859 [ERR] RPCS: [/lnrpc.Lightning/ChannelBalance]: waiting to start, RPC services not available
2026-02-12 09:18:30.264 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
Hopefully this process will just work...
Thursday 12th 08:19 UTC
Unfortunately overnight, despite me shutting down the v4v.app at least one user tried to make a transaction which failed, unfortunately this user thought he was getting support on Discord but got scammed for some other HBD. I will be able to return his original transaction but not what he lost after that.
In light of this I'm making some changes to the way the system operates so I need to fix that before I bring v2 up for the first time.
Updates later.
Wednesday 11th 16:04 UTC
I've made very good progress but I'm not going to get the service back up today. That was always a stretch goal. What I'm doing is pretty complex and I don't want to make mistakes.
I am completely changing the entire internal architecture and the machines this runs on:
- Updated Frontend code
- Updated public facing API
- Completely new database using a cluster on multiple machines
- Completely new back end processing system
As you can see that's quite a few steps. I'm mostly done with 1 and 2, 3 is up and running and 4 is where the biggest work is. I will start that first thing tomorrow morning and hopefully have things up tomorrow.
Wednesday 11th 12:18 UTC
The old v4vapp backend v1 has been taken down. All transfers are suspended. I'm setting to work deploying my new system. It will take me a few hours for sure.
Whilst the work is in progress I will update this post with status updates. I hope to have it completed on Wednesday but I'm going to say that it could take me a couple of days.
I will obviously be transferring Keepsats balances from the old to the new system but anything under 50sats will not transfer across. If you have a tiny balance like that please move it out before Wednesday.
Background
This is a ton of work as this has been an extraordinary big re-write.
It was described in detail in this post
Good luck with the Upgrade! 💪🏻
Good luck friend!☀️
Thanks for informing us!
Everything will be fine, and thank you for your excellent work.
Congratulations @v4vapp! You received a personal badge!
You can view your badges on your board and compare yourself to others in the Ranking
best of luck.. thank you for running this service.
⚠️⚠️⚠️ ALERT ⚠️⚠️⚠️
HIVE coin is currently at a critically low liquidity. It is strongly suggested to withdraw your funds while you still can.
The important thing is that it will look good. Thank you for your work. Let's wait and see the changes this weekend. Thank you for your effort and work. 👏👏👏👏💪👌
⚠️⚠️⚠️ ALERT ⚠️⚠️⚠️
HIVE coin is currently at a critically low liquidity. It is strongly suggested to withdraw your funds while you still can.
Hi. I made a transfer from Hive to Sats and it was deducted, but then it told me that the service is inactive and I can't log in. The notification didn't appear because I was already logged in.
⚠️⚠️⚠️ ALERT ⚠️⚠️⚠️
HIVE coin is currently at a critically low liquidity. It is strongly suggested to withdraw your funds while you still can.
V4V app is still not working with keychain.
No keychain signature window appears to sign into the app, just this message at the bottom of the screen...
AxiosError: Request failed with status code 401I'm guessing this is still a server side issue?
EDIT: Still the same issue as above 20/02/2026 @brianoflondon @v4vapp
Any further news on when V4VAPP will be functioning?
Cheers
Please try to clear the browser cookies and history for the site, download a fresh version. I think you might still have an old version of the site.
Open the menu on the right with the three lines and look down the bottom, you need to see version 2.2.4.
Thanks for your swift response
@brianoflondon
I cleared all browser data on chrome, history, cookies etc and I have the same problem with version 2.2.4 as can be seen in this screenshot. I have even tried logging into V4Vapp using brave browser and the keychain extension, and no joy there either.
I see the problem: go to v4v.app not lnd.v4v.app (maybe you have that bookmarked?)
I'll try to stop that working or redirect it to v4v.app (you can click that link here).
Thanks, I've put in a rule to permanently send lnd.v4v.app to v4v.app without users doing anything, hopefully that fixes this.
Unfortunately that hasn't fixed the issue for me using v4vapp with keychain.
The steps I've taken since last msg are:
Changed to using v4v.app instead of lnd.v4v.app, plus I cleared all my caches before trying with v4v.app.
Tried using brave again with v4v.app... clearing caches and taking shields down etc
I tried downloading the app, and same error unfortunately @brianoflondon :(
I even tried removing the keychain extension from my browser and re-downloading it and firing up a new instance of keychain.
In all instances it returned the same error.
I am really sorry, I think there was a setting I failed to change. Just fixing it right now. Two minutes.... I'll post again when I think it is fixed.
I really hope this is fixed now. Sorry for what you had to do. My fault.
Cheers Brian.
It is working now, confirmed just signed in to v4v.app.
There are a bunch of people on ur latest post on the @brianoflondon account about v4v with the same issue they've highlighted in the comments. Could be worth letting them know it is fixed now.
Thanks again 👍