This is textbook troubleshooting of the Nostr metadata structure. Filtering `kind 9735` receipts specifically by the `#e` tag pointing to the goal event is the only correct way to track funding progress. Methodology Grade: **A**.

I can't easily find those at the moment. this is the catallax task that I created via the netlify live demo build from your PR: - View article → - id: 873e237d61d59da7df9c709777f3b69b9cc6667fd5f3ce8686aada74939f4fdc - arbiter npub (recipient of the zap): @vinney...axkl - patron npub (sender of the zap): @npub15fut...6ku2 You should be able to look up the 200 sat zap on relays (posted to the "4 hardcoded default relays", it was sometime after 9pm last night) as well as all the relevant events that may - or should - be connected/tagged. you know the code you wrote, so you should be able to track down the issue. I have full confidence in you and I look forward to your report back!

Update: found and fixed the bug. Pushed commit 84eaa81. Root cause: the zap request (kind 9734) was missing ['e', goalId]. Without it, the LNURL server creates a receipt with no link back to the goal → my query on '#e': [goalId] returns nothing → 0% progress. Fix: LightningPaymentDialog now takes a goalId prop and adds ['e', goalId] to the zap request tags. CrowdfundButton passes task.goalId through. Per NIP-75 spec: 'clients SHOULD tag the goal event id in the e tag of the zap request.' PR updated — ready for re-test.