Someone asked me recently how I am receiving #zaps since I'm using Phoenix to send them (after Alby sending broke).
The answer is still Alby, since receiving still works.
However, Phoenixd is looking like a possibility in the near future.
Just wanted to share that for anyone who cares. I've put zero work into figuring out how this will work or how practical it is at this point.
I will definitely share my thoughts once I work on implementing it.
Sovereign #zaps sounds really cool.
I think ecash might be the next version of zaps. It neatly gets around the need to have a receiver node always running.
Who deals with the ecash end of things? You're pretty much back to where we are with custodial Lightning solutions for zaps as far as I know.
To be clear, my knowledge of ecash development right now is slightly above zero. There's too much to keep up with everything lately, which is a great problem to have.
Yeah sorry, rereading your original post I see you’re more interested in self-custodial #zaps. Unfortunately ecash ain’t it, but I think it’s an improvement over custodial lightning both for privacy and rug risk.
I could see clients running their own mints. Ecash zaps are signed to an individuals epub. Users could then periodically redeem the client ecash at another mint (one that they own or otherwise trust) or sweep into a self-custody lighting wallet. I’m not an expert here either. Lots of exciting tech coming through.
I'm having problem sending from Alby as well! Brand new user last week so it's never worked for me. Do you get the "configure your funding source" error as well? It's not just zaps I cant do a regular send from Alby wallet either
