pull down to refresh

Actually its probably more like Phoenix than not, since in any scenario payments that are too small to be resolved on chain are inherently trusted. In both our case and Phoenix's case, they queue until a channel open is afforded.
When you say queue, were you referring to the sats essentially being locked (i.e. unable to be sent out after receiving) until a channel is opened?
I havenā€™t used phoenixd yet but I assume thatā€™s how it works with them too? This also seems similar to what Alby Hub is doing when custodial accounts are converted. I think they refer to the sats as ā€œhosted balanceā€.
They're not locked atomically but yes its similar in that its a hosted balance, what you're seeing there though in the screenshot is just the fee reserve for routing out payments... For example if you had a balance of 1000 sats it would still only hold 100 sats, if you had 20k sats it'd hold ~1%, 100 sats or 1% whichever is bigger.
reply
Ah that makes sense. I usually test with small amounts. Turns out this was right at the threshold. šŸ˜„
So a couple more questions:
  1. Those 100 sats were received via the PWA. I decided to give the TestFlight a try so I downloaded that and added the nprofile. Was expecting to see the same 100 sats but didnā€™t. Am I missing something?
  2. Also, when I initially add my nprofile, itā€™s labeled as ā€œrelay.lightning.pubā€
But when I come back later, it just says ā€œwalletā€.
Is this a bug or is it the same source? I was expecting to be able to verify by clicking on the edit icon and seeing the nprofile but it comes up blank.
reply
With the PWA you probably pasted the nprofile:secret from the install script, which made the keypair generated by the PWA the administrator account such that you can send invite links and access the dashboard...
On the next device, the nprofile is creating a new account as a guest (invite links are just using the nprofile as a connection parameter)
To have the two devices sync'd on the same account, you have to auth into the first one (Uses Nostr to back up the wallet settings and sync via nip07 browser extension or our Sanctum remote signer service). Then log into the next device to pull down the sync'd state from Nostr so that your admin keys are in both places.
#2
Yea that's the same source, its just temporarily showing the relay its connecting over until it resolves the Pub's vanity name (can set this in Dashboard for each app, wallet is just the default app, will have avatar and other stuff soon :tm:)
reply
Oh ok, was not aware of that. So I passed the nprofile initially into the PWA and then deleted it once I downloaded the TestFlight. No wonder the admin dashboard wasnā€™t working. šŸ˜„
Do I need to reinstall Lightning Pub in order to get admin access again since subsequent pastes of the nprofile are guest accounts?
reply
ah no problem, its easy to reset:
on the system you're running pub
cd into the lightning_pub folder
rm admin.npub to reset the administrator credentials
cat .admin_connect to show the newly created admin secret for re-pairing
reply
Thanks. We are so back.
Did you say if the pubā€™s vanity name can be changed right now or in the soon-to-released Crawl app?
reply
I lied, misremembered and thought we pushed that already
Soon :tm:
Under the manage button in dashboard it's coming
reply
Sounds good.
Some feedback: maybe add a confirmation prompt when editing a source (at least when deleting). I thought I could rename the source here and mistakenly tapped delete.
I ended up in this state.
I cleared out both sources and pasted my nprofile again, but that messed up my admin panel access. So I did the reset steps that you mentioned before, got another nprofile, and pasted that but I still couldnā€™t access the admin panel.
I wonder if I got into some bad state. Curious to know more about whatā€™s going on underneath.