More enhancements to @v4vapp Lightning Hive and please support proposal 222

Countdown terminated on Jun 7, 2022, 9:00 PM

We're getting toward the last few days before the continuation proposal for developing the Hive Lightning bridge goes live in 5 days. There's been a roughly 3 week gap between proposals.

I really would greatly appreciate your continued support in this work!


Support Proposal 222 on PeakD
Support Proposal 222 with Hivesigner
Support Proposal 222 on Ecency


Node Channels

Since April

  • More than 100 Hive users have used the service since April.
  • Hive to Lightning: $2,367 or 6,768,096 sats sent
  • Lightning to Hive: $1,137 or 3,508,788 sats received
  • The rate of usage has increased dramatically over the last 3 weeks.
  • 18m sats on the V4VApp node for liquidity.

App Updated again

I quietly added a new feature to the @v4vapp v4v.app web app. You can now TYPE a lightning address in to the app. These are the ones that look like email addresses and many people are now designating them with an emoji:

[email protected]

What you can't do is use a Hive Lightning Address (⚡[email protected]) because that would be self payment which is silly)

Copy paste that into the site or type one out it should work (leave off the emoji!)

In the background

I've been working on some very important database upgrades which start the work of ensuring I can deploy the whole system as a new instance.

I'm also putting in place some detailed analytics on how the Lightning Channels on my node are being used, which channels payments come in on and which channels are used for sending out sats. This will dramatically help me open and close channels and keep Lightning running. Managing the Lightning node is really a fiddly and somewhat annoying process. Hopefully better visibility on my own software will help make this easier.

Thank you!

So thank you all for voting so far, and if you haven't voted, please take a look and perhaps encourage anyone else you can to vote this up.


Support Proposal 222 on PeakD
Support Proposal 222 with Hivesigner
Support Proposal 222 on Ecency


Send Lightning to Me!

Countdown terminated on Jun 7, 2022, 9:00 PM
Sort:  

That's a good new feature added. Typing in address makes it so neat. This proposal I already voted !

Thanks for updating, @brianoflondon. Voted for proposal already. 🙋🏼‍♂️
Regards Thomas

I don't understand anything you're coding there but I guess I want to use it in a foreseeable future. Proposal already supported oc. 😁

I was just listening to the Podland episode 77 dated June 2, 2022 where Dave Jones discussed your work on Podping. I didn't realize just how much more robust it had become. The addition of reason codes opens up so many possibilities. I had heard Adam and Dave talk about the live item tag aka LIT on the Podcast Index show, but hadn't pieced together how it worked. Holy smokes! Such a game changer. Kudos to you and fellow Podping developers.

untitled.gif

It is really great to see improvement occuring and I appreciate your efforts in making it a success.

I have not used but will give it a try..
Thanks dear....

one of the most innovative features we got recently, supported! :)


The rewards earned on this comment will go directly to the people(@taskmaster4450le) sharing the post on Twitter as long as they are registered with @poshtoken. Sign up at https://hiveposh.com.

Supported!
Lightning makes a lot of stuff really easy!

!PIZZA

You're really putting more effort everyday for now improvement of this blockchain. Keep the good work

Posted Using LeoFinance Beta

You're really putting more effort everyday for new improvement of this blockchain. Keep the good work

Posted Using LeoFinance Beta

Great work @brianoflondon. I hope and pray for the success of the project and I also encourage others to vote to support it. Well done 👍.

Slowly and steadily it will grow more. And with time it will become more smooth. All the best : )

Use anything other than lightning and I will support your proposal. I don't touch lightning with a 10 foot pole.

The lightning network could lead to a 51% attack one day if more ignorant people use it frequently.

PIZZA!

PIZZA Holders sent $PIZZA tips in this post's comments:
@chrislybear(1/5) tipped @brianoflondon (x1)

You can now send $PIZZA tips in Discord via tip.cc!

:) nice added feature. and yes, it be pretty pointless to pay yourself! :P

Would it be possible to get an option to have the memo sent unencrypted to the receiver? The DACTER account creation tool that the Hive Engine team released is unable to read encrypted messages for payment codes.

Interesting. Yes I can send in clear and I really am unsure what is the correct thing to do.

Perhaps the answer is to allow users to set whether they want open or private messages inbound on their account.

I don't know about DACTER link?

If you want me to make a temp exception I can probably do that tomorrow.

DACTER is a tool the Hive Engine team launched that let's you monetize your claimed discounted account creation tokens on Hive. If someone has a bunch of DACT they can run DACTER and earn BEE for creating accounts for other users.

We started using it to let people sign up for Hive on SportsTalkSocial.com. It let's people send @sportsdact Hive, HBD, SPORTS or AFIT tokens and it in turn pays to have an account created for them. The pain point I noticed today would be that it's unable to read encrypted messages to see the payment memo from @v4vapp.

I'm hoping there's a way to get it to work nicely with @v4vapp so that someone could request an account via SportsTalkSocial.com, get a memo for payment and then use @v4vapp to send Hive or HBD to @sportsdact to create an account via Lightning. This would essentially let anyone create a private account on Hive via @sportstalksocial and @v4vapp with no form of KYC attached.

Fantastic! We will get this sorted next week for sure. This is exactly the use case I envisaged for the gateway.

Who receives the 3 Hive? One issue is that figuring out how to get an exact 3 Hive is hard. I prefer that the account opener over pays slightly, 3 Hive goes to make the account and then the balance can be sent on later perhaps.

Posted using LeoFinance Mobile

The 3 Hive or 2 HBD goes to @sportsdact which then buys and deposits BEE to pay out to the actual account creator on the DACTER site.

I was going to test that this morning and failed at my mission. I tried sending 3 Hive and only paid enough to get 2.9 or so. Whoops! Luckily I noticed that the memos were encrypted before trying again. I'm not sure if DACTER is looking for the exact 3 or just making sure 3 is covered and that a memo is included. I'll create another account in a few to test if I can send 3.2 Hive while using the correct memo if it will actually run the account creation process still.

Thank you for helping on this!

Have you built a front end for this?

I've changed my code (I shouldn't have but I have :-) All messages will be public. I'll add an option to the front end to make things private again later.

I just confirmed it will work well with overpayments. I tested it by sending it 3.2 to cover a 3 Hive invoice and it created the account with no issues. It won't help on the underpayments for users who end up doing what I did this morning but at least it will run when they break the threshold.

This is awesome news on the public memo for me. Is it live right now? If so I'll test it again via lightning to see what happens for fun.

Our front end sign up is live on SportsTalkSocial.com right now. As long as you're not signed in there should be a sign up button on the upper right hand side that will initiate a new account flow. I can't claim any of the work for the site. It's all the Hive Engine team and @reazuliqbal's work. I'm just behind the community and trying to get everything to work together enough to accomplish the end goal for now.

I changed the whole operation for everyone to public right now. I'll add back an OPTION to make things private later.

The way to handle the exchange is probably to do something like ask for overpayment and then return the change to the newly created account.

The actual mechanics of generating a Lightning invoice via my APIs can be done and then the amount can be more carefully calculated and controlled. I might have to add some kind of way through the API that you can ask for a specific Hive price quote and then get a guarantee that you get the exact amount of Hive when you send the asked for Lightning.

Yeah I think that's the best plan for overpayment as well.

I just tested but the extra text, "You received 7500 sats converted to HIVE via @v4vapp. Message:", is throwing off their reading of the memo. Would it be possible for that to be removed for specific accounts like ours and just the memo be sent?

This is also live on neoxian.city too. I'm sure that @neoxian would be interested in accepting Hive via the Lightning Network too so we could end up getting a couple front ends on-board with this change.

I just looked... we can put a direct Lighting option on this screen without any trouble at all. Put me in touch with whoever built this pop up and we can get this done in a jiffy!

This is a big deal: I want more Hive front ends to understand the power of this.

image.png

I sent a message to @reazuliqbal and asked if he could join this conversation. This could become a huge win for a number of communities on Hive!

Great work, been trying to use the LN address feature, but I don't know why the hive keychain wont work and when I use Hive signer it just gives me an error

One thing you can't do is use my v4v.app site to try to send lightning to a @v4v.app lightning address. That would be self payment and apart from giving me double commission it would be silly.

If you can send me a screenshot or a capture of the Javascript console I'll try to help.

If you just want to play I recommend Wallet of Satoshi for holding a bit of Lightning. I have a direct channel to their node so fees are usually 0 sats.

I think I've just found a problem with Hive Keychain version 2 in Brave/Chrome having broken my existing code.

I'll look into it with @stoodkev tomorrow.

You were absolutely right, there was an issue with the change to Hive Keychain v2, it should have been fixed now.

Thanks I gave it a test now and while keychain works, the prompt now opens up the wallet but I am getting a broadcasting error, I have tried swapping nodes but it didn't help

That's puzzling. I'm having no problem right now and I'm seeing others use it.

Best suggestion is a complete browser restart as there may be some funkyness going on with cached version and version of Hive Keychain.

You're trying to send Hive to a Lightning Wallet right?

Correct I was trying to fund a app I wanted to try out, but like you suggested I have been trying WOS first since its a direct channel, I have rebooted my browser, cleared cache, reset my pc and tried a different browser

I'm distinctly puzzled. Try again later :-)