Yes it was a genuine mistake introduced when trying to harden something else. I'm not saying exactly how it was fixed but it is very fixed. And 40,000 never left. It moved to an account and I was able

Both the transactions you received followed lightning payments which came into my node normally. Completely normal. I can't tell where they came from or why they were sent to you but they were.

Lightning is very different from bitcoin but yes the @v4vapp services is unique. Glad you like it.

When a Lightning transaction fails completely the Hive is sent straight back. There are some complex situations where payments stall and my system catches that state and waits for resolution.

It's largely done. You can move sats into and out of Magi with V4V.app. Look back and you'll see in instructions in my blog posts.

Sorry I was a bit unclear: fees for transfers within the Lighting network. Not fees on the BTC main network which are rock bottom 1 sat/Vb most of the time. Hobby routing has almost gone away and the only

Fixed! Really sorry for how long that took, it was an absolutely crazy edge case arising from my switching Lightning node. Your original invoice was paid, change returned as normal.

I've just tried again to perform this transfer and what I thought was a transient connection failure turns out to be a new way of failing I've never seen on Lightning before :-) I think it indicates a

I'm going to try to send the payment later today, still working on fixing the internals, hopefully it will succeed unless you just want the HBD back.

I see the problem, I will put the sats into your keepsats account as soon as I can fix the back end accounting (which has been a bit messed up by this error).

Hi there, just waking up, i'll figure out what went wrong and fix it soon.

Hey I sent you a message about v4vapp on Peakd's system.

Hey I sent you a message about v4vapp on Peakd's system.

Just as I hit publish on this I realise that my Dev Lightning node has been done for a few days and it won't restart.... thankfully it appears that the SSD enclosure has died (2nd time this has happened

Hive has always needed a money making business to be built on top of it. I tried, I didn't succeed. Without a money making business which needs Hive, I'm not sure how we push this along.

I can slim things down and I'm looking at that as part of deciding whether I do the work to move lightning node. If I can get it down to a more manageable level that will help.

It is not getting heavy usage and that is the problem.

Thank you @jza received with gratitude!

Hosting a lightning node in the cloud is not easy. You need a full bitcoin node almost certainly unpruned and with at least 1TB of NVME Disk and more likely 2TB. The most likely path is that I'll have

I have no doubt this phenomenon is widespread but I only have close association with the UK.