From ab725248afa4a6668c69a059f07c8c5ec53bcadd Mon Sep 17 00:00:00 2001 From: Christian Chiarulli Date: Sun, 5 Nov 2023 03:07:46 -0500 Subject: [PATCH] mention zap receipt --- 117.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/117.md b/117.md index ee29ef89..fdfc42e8 100644 --- a/117.md +++ b/117.md @@ -86,7 +86,7 @@ Bounties will provide social incentive to complete tasks related to the developm So that we can track the status of the bounty which provides a way for the client to filter out bounties that have already been assigned. -We can work around this by making sure that the content and reward of the bounty event is the same as the content and reward found in the stringified **Bounty Event** in the **Bounty Event Application**. No **Bounty Event** without a matching reward across these three fields will be considered complete. (Unless both parties agree to settle outside of the network) +We can work around this by making sure that the content and reward of the bounty event is the same as the content and reward found in the stringified **Bounty Event** in the **Bounty Event Application**. No **Bounty Event** without a matching reward across these three fields (including the zap receipt) will be considered complete. (Unless both parties agree to settle outside of the network) If the creator changes the content or reward in an effort to scam the applicant, the applicant has a record of the original content and reward in the **Bounty Event Application**. And the bounty will not count as complete which will at the very least not improve the creators reputation.