nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-23 00:45:53 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

updates

Browse Source
This commit is contained in:
Christian Chiarulli 2023-11-05 17:13:09 -05:00
parent 6355182ca8
commit e81b967828
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
117.md
View File

@ -24,7 +24,9 @@ The following tags MUST be present:
- A `title` tag to provide a title for the bounty. - 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", "<number>", "<currency>" ]`, - A `reward` tag to provide a reward for the bounty. This is an array in the format `[ "reward", "<number>" ]`,
- 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. - 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 `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 ## Bounty Application Event
The `.content` of these events should be a simple plain text string explaining why the creator should choose the applicant. 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. 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.