Cannot mass zap, using nostr:npub142gywvjkq0dv6nupggyn2euhx4nduwc7yz5f24ah9rpmunr2s39se3xrj0
Discussion
Same. Tried to send 1k, only 28 SATs sent and it error'd out when one of the splits was unzappable.
I forwarded this and error logs to nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg & #minibits
&& changed to an alternative lightingadress in the meantime.
== Best if ofc. if fixed so Amethyst don't halt a zap due to one out of gizzilion people have a broken adress.
You can try a mass zap again; if you want :)
Happy new year!
& thanks for reporting.
It works now, however I have to zap each person individually, is there a way I zap just once and it distributes the zap to everyone with equal amount?
Maybe I'm asking too much, I just thought it would work that way
I reply on the screenshot!
I think a single tap -> many zap works in Amethyst if you got a getalby-wallet connector setup. Otherwise it will have to ask your lightning app for permission on each transaction.
I can't make a test atm. But that's how I remember it working.
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z might have more current input on this.
Yeah; I checked the source code and it seems like this is it.
If 'account.hasWalletConnectSetup' is true it seems like it batch sends and split your zap send by itself.
Otherwise it enters some 'onPayViaIntent' logic, that I think is the list you had to click through