Support Proposal 303 on PeakD
Vote for Brianoflondon's Witness KeyChain or HiveSigner
This is a value for value post: see the explanation in the footer.
Login and Passkeys
I'm going to be deploying a new version of v4v.app soon and it may cause an existing login to force you to log out and log in again. I'm sorry about this but I'm improving the security behind the scenes especially because you can now move and store a KeepSats balance directly on v4v.app.
The new version will probably go live a couple of days after I publish this post. If you ever want to see what my live development looks like dev.v4v.app is where I'm working though that site is up and down like a whore's drawers though it is fully functional and hooked up to the real back end.
If you have any problems with the site (like the sidebar being blank) you can reset everything by clicking on the small round green symbol at the bottom. That will let you reset everything.
Active Key
Specifically because of this, up to know I asked you to sign in with a Hive Posting Key. You might not have even noticed this. I am now switching to require you to log in with your Hive Active key because the system is capable of moving funds in and out of KeepSats.
Passkeys
I introduced Passkeys as a way to associate a hardware token, a password manager or your physical phone itself as a way to log in to v4v.app. First you have to log in with signing a Hive challenge either:
- with Hive Keychain (using the in app browser on a phone or the plugin on a desktop);
- or using HAS (Hive Authentication Service) QR code system which is also very easy on a phone.
When I introduced this I didn't account for what happens if you change your Hive keys for some reason. That's rare but if you lose control of a posting or active key, you can revoke them. I want to honour that.
So now when you set up a Passkey it will record the specific Hive public key you're used. If you change your key, the Passkey will need to be re-added.
The practical upshot of all this is that if you've saved a Passkey, you'll have to do it again. Sorry, I can't upgrade the system without doing this. It won't affect very many people.
Podcasting 2.0 and Alby
One of the main underlying reasons for this is that I'm working to emulate a specific Lightning API which is in use across the Podcasting 2.0 App infrastructure. It provides the wallets which Podcast Apps give to their users in order to stream sats to Podcasts as you listen to them.
But Alby's original system, which was the one adopted by the majority of podcasting apps which wanted to use this whole streaming sats system, was based around Alby holding custodial wallets. Alby (like a few other Lightning wallet providers) really don't want to be custodial wallet holders especially not in the USA so they've withdrawn new wallets.
But this leaves the existing apps which have built around their API in the lurch. This is where I'm stepping in.
Alby Wallet API
The Alby Wallet API is completely open source though I'm actually just using the specification and not their software. This is because my back end isn't only Lightning, it is my KeepSats and Hive Bridge.
Authentication is working
The first step, which will be live on my main site when I publish this, is working which allows authentication. The full documentation is here:
In order to use my infrastructure instead of Alby's the eventual plan is that you will replace just the following two end points:
Authorization URI: https://getalby.com/oauth -> https://v4v.app/oauth
Endpoints URI: https://api.getalby.com/ -> https://api.v4v.app/alby/
That should be it!
So far I only have two working endpoints but this is what I'm working on.
https://devapi.v4v.app/alby/user/value4value
https://devapi.v4v.app/alby/user/me
Every Hive Account is a Lightning Wallet
When this is working, every Hive account will become a lightning wallet which can be used in Podcasting 2.0 apps to send or receive Sats for podcasting.
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 303 on PeakD
Support Proposal 303 with Hivesigner
Support Proposal 303 on Ecency
Vote for Brianoflondon's Witness KeyChain or HiveSigner
