Just a couple of issues:
nostr:nprofile1qqs93adzxqyt5k58xzjrta50rrdqkyxw2wxxu2495xmczgrkxpx4nacprpmhxue69uhhyetvv9ujumn0w3hhx6rf9emkjm30qyv8wumn8ghj7un9d3shjtnnd9sk6um5wghxxmmd9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcvaycfj down at the bottom took a few attempts with my fat finger. 
Ohh good catch!
strange
I've been donated sats from others through last few days
maybe something #minibits related? if it's at my receiver end. A bit to New years eavy for me to dive into atm
I've checked it. Your minibits lightning address returned error because you had dozens of unpaid not yet expired invoices (likely never paid zaps) and they hit the limit set as a dos attack precaution.
I've increased the limit few times up, so should not be an issue anymore.
Is there a way we can create invoices that expire? For zaps, the invoices should be really short term.
I used to have 30 min expiry on minibits mint when used lnbits as a node middleware but now the mint is directly integrated to lnd with their 24h default.
Raised an issue to nutshell to enable to set custom expiry but not yet implemented afaik.
That's why I raised significantly the unpaid invoices dos limit per address yesterday.
