What issues are you having? What open issues on GitHub?
based on my experience and all of the open issues on github, zeuspay is not working well at all recently. nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 any eta on a stable update?
Discussion
I'm curious too. Zeus has been working great for me.
i see your ln address is getalby. this is not related to getalby + zeus which has generally worked well on nostr. the issues above have to do with node-in-a-phone zeuspay ln address over nostr
I see. My addressiss getalby because I am moving and my node is going offline. But I never used the integrated node/wallet as my zap address, so I can't speak to that.
nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 thanks for the reply.
here are just a few of the current issues i'm seeing with: zeuspay (node-in-a-phone) client: #amethyst
every week i receive multiple notifications from people on noster saying they tried to zap me multiple times and it didn't go through...i ask them to send it directly i.e. just send to my zeuspay address and not zapping my note and it goes through.
this happens often and frequently results in people zapping me multiple times because it seems like the transaction didn't go through
many times i will get a timeout error trying to zap someone (could not fetch invoice, unable to create lightning invoice before sending the zap, could not resolve (alby link), only to swipe back and try again, then it says payment is in-transit
when i try to zap someone i will get 1 of at least 3 different errors (all my settings are default) this happens about 40% of the time atm
auto-redeem simply doesn't work. i keep having to manually redeem
the little mailbox notifying me of zaps to redeem has stopped displaying after upgrading from beta, so i have to go into settings, address, then redeem
there are currently 209 open issues with pull requests including 57 open bug issues on github
#m=image%2Fjpeg&dim=1440x1440&blurhash=U46Hft4%2CE0%255%3FZM%23M%7CkQEHRVxvtK-aD%7Dow%255&x=a2f23549036c054b40db3fd00e43acb9f0511ba706a014df7c1956ff07aa62eb
#m=image%2Fjpeg&dim=1440x1440&blurhash=U25O58Sr4m%24pS%3B-rV%5DIl00aj-%3DR%7Em%7D9ptP-a&x=acb307e303029f6841e0e25b4efdb6a86f803e18d144e3bd3a02cd1cbc8e5ce9
#m=image%2Fjpeg&dim=1440x1440&blurhash=U25hDeOO0J%24pE%3F-ZRoD%7D00Rk%3FIoc%23x9ptO%3FK&x=111aa0e501e8f076411854e1a60df7423227515cc108fc588c023a913d8fdfe5
#m=image%2Fjpeg&dim=720x835&blurhash=%7B46b0%7C%3F%5BI-SJIAVuIBIBNYo_tkbbt7nmi%7Ci%7E-%3BocRjWVRjj%5BjZayR6RPWEj%5Dj%5BkBa_kB00M_xukCt7aet7ogNES0X6kCjuafjIjbD%24tQtRR%25ogaen%2CV%5B%25Mt7RjWBayaxfkWUZ*rxVuM%7BoftPtQoy&x=891b20eff772a849647bca87a95de9eed93ec5618b449d96891690d54622082a
We hear you on auto redeem and notifications.
Pulling up other LNURLs like from that screenshot from Primal isn’t a ZP issue though. Invoices are fetched by your Nostr client before being opened in ZEUS.
Other clients not properly displaying payments as in transit is known, but also not a ZP issue per se. Senders’ wallets in question need to improve their UI and accurately reflect in transit hodl payments.
GitHub issue screenshotted doesn’t pertain to ZP per se either but is being addressed in v0.8.1.
np. mostly makes sense. let's hope the other sender's wallets get with it soon. seems to be working fine with alby + zeus nwc. looking forward to the next update