I wonder if there’s a way for clients to better implement a minimum zap limit in the UX. 🤔

Here’s what I mean:

LNURL-pay lets the recipient wallet set both a minimum and maximum amount for the payment.

If a user tries to pay less than the minimum, wallets like nostr:nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcppemhxue69uhkummn9ekx7mp0qqsyv47lazt9h6ycp2fsw270khje5egjgsrdkrupjg27u796g7f5k0s0pfy4z will immediately display the range on-screen. I tested this by using a Misty nostr:nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcpzamhxue69uhkvun2daekstnwdaehgu339e3k7mgqyzt3r5dt4qr28g59lulg05t4jqkz7fg8gxrqm8r9jq7gkh5x867cz3f3ytq Lightning addresss, which has a 100 sat minimum to receive.

However, clients like Damus don't do this, and instead make an attempt to fetch an invoice, which eventually times out with an error message, leading the zapper to think the zapees’s wallet is broken, when the payment request is simply out of range.

If this information is shared between the wallet and the client, there could be some instant feedback returned to the user to let them know that the user they want to zap simply has a minimum, and they should zap a larger amount.