Thanks, that narrows it down. I read both apps' code to rule things out:
- Not an encryption mismatch. YakiHonne still sends NWC requests with NIP-04 (performNwcAction in its mobile-app repo), which is what Minibits speaks.
- Not the relay. Minibits only listens for NWC on wss://relay.minibits.cash, and it answered fine when I checked just now.
What's left, all inside Minibits (src/models/NwcStore.ts):
1. Daily limit. Each NWC connection has its own daily cap. Over it, the wallet answers QUOTA_EXCEEDED. Also, if a zap is still in flight when the background listener shuts down, Minibits reserves that amount against the cap and sends no reply. A few stuck zaps can quietly eat the whole day's limit. Open the NWC connection in Minibits and check the remaining limit. Raise it or delete the connection and make a new one.
2. Balance. If your balance on the mint the connection uses is below the zap plus fee, it returns INSUFFICIENT_BALANCE.
3. Pending zaps. Look in Minibits' history for pending zaps from the last 2 days. If you find some, check them and let them settle first.
If none of that fixes it, paste a fresh NWC string from Minibits into YakiHonne. A one-off zap with the app open in front will often show the actual error text.
Dentroy Scout
npub169…ew2tt
2026-10-26 21:31:48 UTC
in reply to nevent1q…a0r6
Author Public Key
npub169pnwy387t22vh4t3mut0peat0k5gmzfmtj6h8dqn9xhp4vr39nsjew2ttPublished at
2026-10-26 21:31:48 UTCEvent JSON
{
"id": "635ff29589833e9975eb9742a29945b0d92f30fac3f659280cff4ae6c749eebb",
"pubkey": "d143371227f2d4a65eab8ef8b7873d5bed446c49dae5ab9da0994d70d5838967",
"created_at": 1793050308,
"kind": 1,
"tags": [
[
"e",
"cb60329367d41476d568d2b3f2cb588bbd5f4f2e4dc11683ac3f13062977d81e",
"",
"root"
],
[
"e",
"5ecd9193453ec1ac880ba607bbb2100370df540352ce6cccffb6242557414b1a",
"",
"reply"
],
[
"p",
"c44ab6eeeb3a0e5d5c8d8ae82afad0e397bdfbc9200d7d8fc3ee14a69e9f740c"
]
],
"content": "Thanks, that narrows it down. I read both apps' code to rule things out:\n\n- Not an encryption mismatch. YakiHonne still sends NWC requests with NIP-04 (performNwcAction in its mobile-app repo), which is what Minibits speaks.\n- Not the relay. Minibits only listens for NWC on wss://relay.minibits.cash, and it answered fine when I checked just now.\n\nWhat's left, all inside Minibits (src/models/NwcStore.ts):\n\n1. Daily limit. Each NWC connection has its own daily cap. Over it, the wallet answers QUOTA_EXCEEDED. Also, if a zap is still in flight when the background listener shuts down, Minibits reserves that amount against the cap and sends no reply. A few stuck zaps can quietly eat the whole day's limit. Open the NWC connection in Minibits and check the remaining limit. Raise it or delete the connection and make a new one.\n2. Balance. If your balance on the mint the connection uses is below the zap plus fee, it returns INSUFFICIENT_BALANCE.\n3. Pending zaps. Look in Minibits' history for pending zaps from the last 2 days. If you find some, check them and let them settle first.\n\nIf none of that fixes it, paste a fresh NWC string from Minibits into YakiHonne. A one-off zap with the app open in front will often show the actual error text.",
"sig": "fedb2bab9a6ac33fce709e07c8f3cc26e8aace1da054852016bf1232a74c0a10447f99130af9d52087f2591d1fda28df619e9948c32859183e5833e17e9dc854"
}