From e81b967828ee8c98b57359e14c6d309607de6e46 Mon Sep 17 00:00:00 2001 From: Christian Chiarulli Date: Sun, 5 Nov 2023 17:13:09 -0500 Subject: [PATCH] updates --- 117.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/117.md b/117.md index 1cc8ae9..94e9bac 100644 --- a/117.md +++ b/117.md @@ -24,7 +24,9 @@ The following tags MUST be present: - A `title` tag to provide a title for the bounty. -- A `reward` tag to provide a reward for the bounty. This is an array in the format `[ "reward", "", "" ]`, +- A `reward` tag to provide a reward for the bounty. This is an array in the format `[ "reward", "" ]`, + +- A `c` tag to provide the currency of the reward example: "sats" or "usd". - A `d` tag to provide a unique identifier for the bounty. @@ -44,6 +46,8 @@ The following tags MAY be present: - An `application` tag with the stringified **Bounty Application Event**. **NOTE** This tag SHOULD be present when the bounty has the `assigned` status. +- An arbitrary amount of `t` tags to provide a list of tags that can be used as categories to filter bounties. + ## Bounty Application Event The `.content` of these events should be a simple plain text string explaining why the creator should choose the applicant. @@ -104,4 +108,4 @@ This would require 2 events to be published: A note can also be published along with the creation of the event referencing the bounty with an arbitrary list of p tags for users the creator thinks may be interested in reviewing or applying the bounty. -potentially make currency it's own tag so you can filter by currency. +Potentially make currency it's own tag so you can filter by currency.