rich1.0vinney...axkl (npub19m…8axkl)https://nostr.now/npub19ma2w9dmk3kat0nt0k5dwuqzvmg3va9ezwup0zkakhpwv0vcwvcsg8axklnjumphttps://nostr.nowThanks! I'm testing the live preview again (https://deploy-preview-1--catallax-reference-client.netlify.app/task/naddr1qvzqqqyz0ypzpgnchwcreazung3ut0td2fypjmrt09pyl2wfqsrwnwc2x89gsuyyqqjhjmmvdukkc6tkv5khgetnw35kueedvdex7amyve6kuerfdenj6wfjxgun2dcrnxtee) I zapped the task 250 and saw confirmation messages but no progress update. then I noticed this in the console: ``` Ignoring task update from unauthorized party: 184d460fadfe8db01b422f750232877d2c331095b6666cea0d9c72c57a43ce95 task: cheaper-359910 ``` Could the problem be that there is logic to gate _who_ can update the status of a task, and "funding from arbitrary zappers" is **not** currently allowed to update task status? Prior to crowdfunding, the Patron was the npub who funded the task and transitioned it to "funded" status (replacing the event). now, anyone can initiate the first "funding zap". Perhaps for crowdfunded tasks, upon creation by the Patron, the task should immediately be in a new state - like "funding". Again, I'm testing this like a somewhat dumb user, not looking at the code yet. Once we get to the point where the main UX actually works, I'll do a proper code review. Thanks for your efforts so far! Let me know if you have questions about the above, or if I'm way off on my hunch. If you identify the problem correctly, feel free to implement the fix on your PR and let me know and I'll test again.