Is it safe to unplug and plug-in an Umbrel Lightning node with a wallet with Bitcoin in it?
I’m trying to exit the node safely, but it’s asking for my username and password and not accepting what I had saved 🤦♂️ so I guess I have to just turn it off.
It looks like I have the Lightning node wallet key. Is that all I need to access funds?
podverse://lnpay/connect-wallet/<api key>/<wallet key>
When the user presses that button, Podverse would open and say “Wallet successfully connected!”
One of the perks of using this approach is you could connect the same wallet to multiple podcast apps, so you don’t have to manage your funds in multiple wallets.
@adam mentioned on today’s episode that the “connect to this wallet button” is impossible given the way mobile devices work. I just want to clarify that it IS possible to make a button like this work if you are using a custodial wallet API like LNPay.
All that our mobile apps need to send Bitcoin transactions via LNPay is the user’s API Key and Wallet key, and that can be easily passed to any iOS or Android mobile app in a custom URL.
Join us at 6pm UTC today for our weekly developer roundtable.
Find your timezone at the page below.
9:00 pm IDT
8:00 pm CEST
7:00 pm BST
6:00 pm UTC
2:00 pm EDT
1:00 pm CDT
12:00 pm MDT
11:00 am PDT
We're having a hard time finding a clean solution for this problem. It seems like any direction we choose in has significant trade-offs. Would love to share more info and get feedback from the community on the approach we're thinking of using.
A topic I'd like to bring up in Saturday's Podcasting 2.0 meeting: what are best practices for handling tiny boost transactions?
You are boosting a value of 100 sats for a podcast. If you're boosting No Agenda, the current splits are:
Which adds up to 101, so the values would end up being split as:
Since we can't send a fraction of a sat, what should we do with the remainders?
Also, should we even send a micro-transaction below 10 sats?
In this video, 10 sats are streamed to the value tag recipients every 10 seconds. They are not sent right away, but rather added to a transaction queue.
Every 20 seconds, the transactions are bundled into a single transaction per recipient, and sent if the amount for that recipient adds up to more than 10 sats.
For less than 10 sats, the transactions remain in the queue until the bundled recipient amount is > 10 sats.
In production the intervals will be 1 min stream / 10 min per bundling.
Podverse Streaming Sats demo:
We're still days away before we have everything polished up and ready for testers, but it's getting there!
Sneak peak of the new Podverse transcript feature 👀
Video demo: http://somup.com/crfDlsFiIU
This should be available in the Podverse Beta release this Sunday.
@mitch @brianoflondon This is what I do for fun .. https://github.com/cisene/podcast-map/blob/master/podcast-url-formats.xml
Intended for all stake holders of podcasting who are interested in improving the eco system