Meyer @meyer_btc - 1y
nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 thoughts on the below? Had plenty of inbound capacity. Why did this inbound payment require a channel open? https://image.nostr.build/1b5fe707f1bd3ed51c6c9a3f71cd61ca90d3181f2d98a1acf327dae5a014f75e.jpg
Seems to be persistent regardless of how long I have app opened. Channel status shows good but still giving me the error when I try to redeem my sats from my LNURL
This is the transaction hash I got from sender: 588a6d0bb32b5b7f2dcbec94d264efcf40f6149ab3c9c36ff276ed0a98dfc5b5 Any thoughts? Hate to be a pain but I guess this sort of trial/error is how we make these tools idiot proof for the masses
Interpreting logs is when I start getting lost ha This look ok? https://image.nostr.build/14478a8ae9f4fa3bcecef3524febd4ca2ba6b8a7ed1eda7d99fd47e2e05c99c5.jpg
Going to assume I should be good. I see a successful receive transaction in my history How do I clear out the 2 pending transactions on my LNURL? Reset my npub/nsec? Any other way to get those cleared out? Thanks again for all your help! https://image.nostr.build/c8a74e0a41051cbbaa07712c57d6346c91693715ec190c23a616536df2730a77.jpg
