upleb.uk

Public git repos — served from a NIP-34 GRASP relay at git.upleb.uk

summaryrefslogtreecommitdiff
path: root/99.md
diff options
context:
space:
mode:
authorAlex Gleason <alex@alexgleason.me>2026-04-10 13:31:37 -0500
committerAlex Gleason <alex@alexgleason.me>2026-04-10 13:31:37 -0500
commit5e1e24766910fc07cb61a049aed2623987458ec2 (patch)
treeb7588f61fddf9374268d5cd6f4e3f2655d7c840a /99.md
parentb8782df594b4e7e8f088869134908eed58be6078 (diff)
parent3465f540e3eaedccb5309711b502f0febf56b52f (diff)
Merge nip44-big-payloads into bigger-nip44bigger-nip44
Diffstat (limited to '99.md')
-rw-r--r--99.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/99.md b/99.md
index 724ce5f..2b6a97a 100644
--- a/99.md
+++ b/99.md
@@ -8,7 +8,7 @@ Classified Listings
8 8
9This NIP defines `kind:30402`: an addressable event to describe classified listings that list any arbitrary product, service, or other thing for sale or offer and includes enough structured metadata to make them useful. 9This NIP defines `kind:30402`: an addressable event to describe classified listings that list any arbitrary product, service, or other thing for sale or offer and includes enough structured metadata to make them useful.
10 10
11The category of classifieds includes a very broad range of physical goods, services, work opportunities, rentals, free giveaways, personals, etc. and is distinct from the more strictly structured marketplaces defined in [NIP-15](15.md) that often sell many units of specific products through very specific channels. 11The specification supports a broad range of use cases physical goods, services, work opportunities, rentals, free giveaways, personals, etc. To promote interoperability between clients implementing NIP-99 for e-commerce, you can find the extension proposal [here](https://github.com/GammaMarkets/market-spec/blob/main/spec.md) which standardizes the e-commerce use case while maintaining the specification's lightweight and flexible nature. While [NIP-15](15.md) provides a strictly structured marketplace specification, NIP-99 has emerged as a simpler and more flexible alternative.
12 12
13The structure of these events is very similar to [NIP-23](23.md) long-form content events. 13The structure of these events is very similar to [NIP-23](23.md) long-form content events.
14 14
@@ -40,7 +40,7 @@ The following tags, used for structured metadata, are standardized and SHOULD be
40 - `"<number>"` is the amount in numeric format (but included in the tag as a string) 40 - `"<number>"` is the amount in numeric format (but included in the tag as a string)
41 - `"<currency>"` is the currency unit in 3-character ISO 4217 format or ISO 4217-like currency code (e.g. `"btc"`, `"eth"`). 41 - `"<currency>"` is the currency unit in 3-character ISO 4217 format or ISO 4217-like currency code (e.g. `"btc"`, `"eth"`).
42 - `"<frequency>"` is optional and can be used to describe recurring payments. SHOULD be in noun format (hour, day, week, month, year, etc.) 42 - `"<frequency>"` is optional and can be used to describe recurring payments. SHOULD be in noun format (hour, day, week, month, year, etc.)
43- - `"status"` (optional), the status of the listing. SHOULD be either "active" or "sold". 43- `"status"` (optional), the status of the listing. SHOULD be either "active" or "sold".
44 44
45#### `price` examples 45#### `price` examples
46 46
@@ -48,7 +48,7 @@ The following tags, used for structured metadata, are standardized and SHOULD be
48- €15 per month `["price", "15", "EUR", "month"]` 48- €15 per month `["price", "15", "EUR", "month"]`
49- £50,000 per year `["price", "50000", "GBP", "year"]` 49- £50,000 per year `["price", "50000", "GBP", "year"]`
50 50
51Other standard tags that might be useful. 51Other common tags that might be useful.
52 52
53- `"g"`, a geohash for more precise location 53- `"g"`, a geohash for more precise location
54 54