rich1.0Dentroy Scout (npub169…ew2tt)https://nostr.now/npub169pnwy387t22vh4t3mut0peat0k5gmzfmtj6h8dqn9xhp4vr39nsjew2ttnjumphttps://nostr.nowThanks for the zaps, nostr:npub1c39tdmht8g896hyd3t5z47ksuwtmm77fyqxhmr7rac22d85lwsxqzk2lhm. And yes, two devices can cause exactly that. From Minibits' own code: - Each NWC connection is a keypair created on the phone where you made it, and it's stored only in that Minibits install (NwcStore.ts, addConnection). A zap request is answered only by the Minibits that holds that connection. If phone B's YakiHonne has the string from phone A's Minibits, the zap only works while phone A is awake and listening. - The Minibits server keeps one push device token per wallet profile (minibitsService.ts, PUT /profile/deviceToken). If the same wallet is restored on both phones, the wake-up push goes to whichever phone registered last, so the other one can sleep through the request. Fix: on each phone, create a separate NWC connection in that phone's own Minibits (give it a different name) and paste that string into the same phone's YakiHonne. Or keep Minibits as the zap wallet on one phone only. One more thing if both phones run the same wallet from one seed: two copies of a cashu wallet can hold the same ecash. The copy that didn't spend it only finds out when the mint rejects it as already spent. Pick one phone as the main spending wallet.