V4V.app v2 Is now RUNNING.... ALL GOOD! ✅

✅ Update: Thursday 19th 05:24 UTC

The site as actually working yesterday afternoon and a few transactions went through. Everything is looking good. Thank you for patience again!

Update: 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.

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.

---

That was a bit of a saga

On Wednesday last week I took v4v.app down to switch my infrastructure over from the original code I wrote over two years ago to something I've been working on for a year or more.

The goal is that the back end is more robust, easier to maintain, and potentially understandable for someone else to run.

Along the way AI arrived and helped me build a complete accounting system (which the first version completely lacked) as well as a bunch of extra features and documentation which I hope will help me decentralise this as soon as I can.

And no sooner did I get things working this morning than some urgent technical work by @privex took everything off line, but it's coming back right now.

The Upgrade

But just as I was getting ready to launch, Binance pulled a small rug out from under me. It wasn't as bad as I first thought, but it involved me working feverishly to replace a whole lot of code I wrote months ago and had tested thoroughly.

Binance Hive BTC market

Binance removed their market for trading HIVE against BTC. They didn't stop dealing with HIVE—you can still trade it for USDT and USDC—but the direct pair with BTC went away. I had been using that (automated via the API) to keep my balances topped up. Suddenly I couldn't use that code anymore. This was a little complicated because they had a minimum trade size of 10,000 sats, which meant I had to batch up transactions: quite a lot of code went into this.

But it turns out Binance has a much simpler (for me) Swap interface that just lets me swap almost any amount of HIVE (as small as 0.001) for BTC, and fees are built into the rate. This is fabulous, and I remember wanting to use it before but there was one glitch.

Binance's testnet doesn't support swaps, so if you want to write code for it, you're playing with real money!

Well, I had no choice but to tell Claude (hehe) to replace my whole Binance market-based system with a swap-based version, and then I had to test it (because again, this is live money).

What's Changed?

For users there isn't a lot to see, but there are significant changes behind the scenes—especially in the way Keepsats can be used (that's sats held on v4v.app). Previously the only way to use them was via the interactive front end.

Custom JSON and Magi / VSC

There is now a Hive custom_json interface and I will be documenting and explaining that to other developers soon.

This custom_json interface is hugely important because it is a stepping stone to being able to store and trade HIVE/HBD for BTC on @magi.network. As soon as that is available, my new code will be easy to integrate with it when it is fully live. The ultimate goal is that I won't be storing any Keepsats and the balances will be controlled on Magi's real blockchain.

Status Page

I've had a placeholder for a Status Page forever! That got fixed. It will pull fees and balances in real time. You can see this page above.

Transaction History

The transactions view page (on the Wallet Tab - History) is the one which has changed the most dramatically. It's a window directly into the accounting system so it might seem a bit confusing—this is because behind the scenes, sats and HIVE are converted and moved around in separate operations.

The little Hive symbols link to the exact transaction in a block explorer. This system gives me a lot more traceability.

I will do a bigger explanation of how to read this in a future post.

Tweaks

I will be watching transactions very carefully now, hopefully all will work as I hope (gulp) and if it doesn't I'll fix it!

Thank you for your patience with this.

---

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 342 on PeakD
Support Proposal 342 with Hivesigner
Support Proposal 342 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