10 files changed, 132 insertions, 18 deletions

diff --git a/01.md b/01.md
index d6ccfbe..d822bfb 100644
--- a/01.md
+++ b/01.md
@@ -62,11 +62,13 @@ Each tag is an array of strings of arbitrary size, with some conventions around
 
 The first element of the tag array is referred to as the tag _name_ or _key_ and the second as the tag _value_. So we can safely say that the event above has an `e` tag set to `"5c83da77af1dec6d7289834998ad7aafbd9e2191396d75ec3cc27f5a77226f36"`, an `alt` tag set to `"reply"` and so on. All elements after the second do not have a conventional name.
 
-This NIP defines 3 standard tags that can be used accross all event kinds with the same meaning. They are as follows:
+This NIP defines 3 standard tags that can be used across all event kinds with the same meaning. They are as follows:
 
 - The `e` tag, used to refer to an event: `["e", <32-bytes lowercase hex of the id of another event>, <recommended relay URL, optional>]`
 - The `p` tag, used to refer to another user: `["p", <32-bytes lowercase hex of a pubkey>, <recommended relay URL, optional>]`
-- The `a` tag, used to refer to a parameterized replaceable event: `["a", <kind integer>:<32-bytes lowercase hex of a pubkey>:<d tag value>, <recommended relay URL, optional>]`
+- The `a` tag, used to refer to a (maybe parameterized) replaceable event
+    - for a parameterized replaceable event: `["a", <kind integer>:<32-bytes lowercase hex of a pubkey>:<d tag value>, <recommended relay URL, optional>]`
+    - for a non-parameterized replaceable event: `["a", <kind integer>:<32-bytes lowercase hex of a pubkey>:, <recommended relay URL, optional>]`
 
 As a convention, all single-letter (only english alphabet letters: a-z, A-Z) key tags are expected to be indexed by relays, such that it is possible, for example, to query or subscribe to events that reference the event `"5c83da77af1dec6d7289834998ad7aafbd9e2191396d75ec3cc27f5a77226f36"` by using the `{"#e": "5c83da77af1dec6d7289834998ad7aafbd9e2191396d75ec3cc27f5a77226f36"}` filter.
 
@@ -80,9 +82,9 @@ Kinds specify how clients should interpret the meaning of each event and the oth
 And also a convention for kind ranges that allow for easier experimentation and flexibility of relay implementation:
 
 - for kind `n` such that `1000 <= n < 10000`, events are **regular**, which means they're all expected to be stored by relays.
-- for kind `n` such that `10000 <= n < 20000 || k == 0 || k == 3`, events are **replaceable**, which means that, for each combination of `pubkey` and `kind`, only the latest event is expected to (SHOULD) be stored by relays, older versions are expected to be discarded.
+- for kind `n` such that `10000 <= n < 20000 || n == 0 || n == 3`, events are **replaceable**, which means that, for each combination of `pubkey` and `kind`, only the latest event is expected to (SHOULD) be stored by relays, older versions are expected to be discarded.
 - for kind `n` such that `20000 <= n < 30000`, events are **ephemeral**, which means they are not expected to be stored by relays.
-- for kind `n` such that `30000 <= n < 40000`, events are **parameterized replaceable**, which means that, for each combination of `pubkey`, `kind` and the `d` tag, only the latest event is expected to be stored by relays, older versions are expected to be discarded.
+- for kind `n` such that `30000 <= n < 40000`, events are **parameterized replaceable**, which means that, for each combination of `pubkey`, `kind` and the `d` tag's first value, only the latest event is expected to be stored by relays, older versions are expected to be discarded.
 
 In case of replaceable events with the same timestamp, the event with the lowest id (first in lexical order) should be retained, and the other discarded.
 
diff --git a/11.md b/11.md
index 083ae8f..deb6f19 100644
--- a/11.md
+++ b/11.md
@@ -80,6 +80,8 @@ are rejected or fail immediately.
         "min_pow_difficulty": 30,
         "auth_required": true,
         "payment_required": true,
+        "created_at_lower_limit":31536000,
+        "created_at_upper_limit":3,
   }
 ...
 }
@@ -123,6 +125,10 @@ Even if set to False, authentication may be required for specific actions.
 
 - `payment_required`: this relay requires payment before a new connection may perform any action.
 
+- `created_at_lower_limit`: 'created_at' lower limit as defined in [NIP-22](22.md)
+
+- `created_at_upper_limit`: 'created_at' upper limit as defined in [NIP-22](22.md)
+
 ### Event Retention ###
 
 There may be a cost associated with storing data forever, so relays
diff --git a/15.md b/15.md
index 01ef05b..edece81 100644
--- a/15.md
+++ b/15.md
@@ -220,6 +220,28 @@ The below json goes in `content` of [NIP04](https://github.com/nostr-protocol/ni
     "shipped": <Bool, true/false has been shipped>,
 }
 ```
+## Customize Marketplace
+Create a customized user experience using the `naddr` from [NIP-19](https://github.com/nostr-protocol/nips/blob/master/19.md#shareable-identifiers-with-extra-metadata). The use of `naddr` enables easy sharing of marketplace events while incorporating a rich set of metadata. This metadata can include relays, merchant profiles, and more. Subsequently, it allows merchants to be grouped into a market, empowering the market creator to configure the marketplace's user interface and user experience, and share that marketplace. This customization can encompass elements such as market name, description, logo, banner, themes, and even color schemes, offering a tailored and unique marketplace experience.
+
+### Event `30019`: Create or update marketplace UI/UX
+
+**Event Content**:
+```json
+{
+    "name": <String (optional), market name>,
+    "about": <String (optional), market description>,
+    "ui": {
+      "picture": <String (optional), market logo image URL>,
+      "banner": <String (optional), market logo banner URL>,
+      "theme": <String (optional), market theme>,
+      "darkMode": <Bool, true/false>
+    },
+    "merchants": <[String] (optional), array of pubkeys>,
+    ...
+}
+```
+
+This event leverages naddr to enable comprehensive customization and sharing of marketplace configurations, fostering a unique and engaging marketplace environment.
 
 ## Customer support events
 
diff --git a/45.md b/45.md
index a525391..7b11950 100644
--- a/45.md
+++ b/45.md
@@ -21,6 +21,7 @@ This NIP defines the verb `COUNT`, which accepts a subscription id and filters a
 ```
 
 Counts are returned using a `COUNT` response in the form `{"count": <integer>}`. Relays may use probabilistic counts to reduce compute requirements.
+In case a relay uses probabilistic counts, it MAY indicate it in the response with `approximate` key i.e. `{"count": <integer>, "approximate": <true|false>}`.
 
 ```
 ["COUNT", <subscription_id>, {"count": <integer>}]
@@ -36,4 +37,8 @@ Examples:
 # Count posts and reactions
 ["COUNT", <subscription_id>, {"kinds": [1, 7], "authors": [<pubkey>]}]
 ["COUNT", <subscription_id>, {"count": 5}]
+
+# Count posts approximately
+["COUNT", <subscription_id>, {"kinds": [1]}]
+["COUNT", <subscription_id>, {"count": 93412452, "approximate": true}]
 ```
diff --git a/52.md b/52.md
index 846fbf4..f5bd0ad 100644
--- a/52.md
+++ b/52.md
@@ -30,7 +30,7 @@ The list of tags are as follows:
 * `start` (required) inclusive start date in ISO 8601 format (YYYY-MM-DD). Must be less than `end`, if it exists.
 * `end` (optional) exclusive end date in ISO 8601 format (YYYY-MM-DD). If omitted, the calendar event ends on the same date as `start`.
 * `location` (optional) location of the calendar event. e.g. address, GPS coordinates, meeting room name, link to video call
-* `g` (optional) [geohash](https://en.wikipedia.org/wiki/Geohash) to associate calendar event with a searchable physical location as suggested as an example by [NIP-12](12.md)
+* `g` (optional) [geohash](https://en.wikipedia.org/wiki/Geohash) to associate calendar event with a searchable physical location
 * `p` (optional, repeated) 32-bytes hex pubkey of a participant, optional recommended relay URL, and participant's role in the meeting
 * `t` (optional, repeated) hashtag to categorize calendar event
 * `r` (optional, repeated) references / links to web pages, documents, video calls, recorded videos, etc.
@@ -88,7 +88,7 @@ The list of tags are as follows:
 * `start_tzid` (optional) time zone of the start timestamp, as defined by the IANA Time Zone Database. e.g., `America/Costa_Rica`
 * `end_tzid` (optional) time zone of the end timestamp, as defined by the IANA Time Zone Database. e.g., `America/Costa_Rica`. If omitted and `start_tzid` is provided, the time zone of the end timestamp is the same as the start timestamp.
 * `location` (optional) location of the calendar event. e.g. address, GPS coordinates, meeting room name, link to video call
-* `g` (optional) [geohash](https://en.wikipedia.org/wiki/Geohash) to associate calendar event with a searchable physical location as suggested as an example by [NIP-12](12.md)
+* `g` (optional) [geohash](https://en.wikipedia.org/wiki/Geohash) to associate calendar event with a searchable physical location
 * `p` (optional, repeated) 32-bytes hex pubkey of a participant, optional recommended relay URL, and participant's role in the meeting
 * `t` (optional, repeated) hashtag to categorize calendar event
 * `r` (optional, repeated) references / links to web pages, documents, video calls, recorded videos, etc.
diff --git a/58.md b/58.md
index d6bb27d..ccabc7b 100644
--- a/58.md
+++ b/58.md
@@ -11,7 +11,7 @@ user profiles:
 
 1. A "Badge Definition" event is defined as a parameterized replaceable event with kind `30009` having a `d` tag with a value that uniquely identifies the badge (e.g. `bravery`) published by the badge issuer. Badge definitions can be updated.
 
-2. A "Badge Award" event is a kind `8` event with a single `a` tag referencing a "Define Badge" event and one or more `p` tags, one for each pubkey the badge issuer wishes to award. Awarded badges are immutable and non-transferrable.
+2. A "Badge Award" event is a kind `8` event with a single `a` tag referencing a "Badge Definition" event and one or more `p` tags, one for each pubkey the badge issuer wishes to award. Awarded badges are immutable and non-transferrable.
 
 3. A "Profile Badges" event is defined as a parameterized replaceable event
 with kind `30008` with a `d` tag with the value `profile_badges`.
diff --git a/75.md b/75.md
new file mode 100644
index 0000000..6c8cb7b
--- /dev/null
+++ b/75.md
@@ -0,0 +1,76 @@
+# NIP-75
+
+## Zap Goals
+
+`draft` `optional` `author:verbiricha`
+
+This NIP defines an event for creating fundraising goals. Users can contribute funds towards the goal by zapping the goal event.
+
+## Nostr Event
+
+A `kind:9041` event is used.
+
+The `.content` contains a human-readable description of the goal.
+
+The following tags are defined as REQUIRED.
+
+- `amount` - target amount in milisats.
+- `relays` - a list of relays the zaps to this goal will be sent to and tallied from.
+
+Example event:
+
+```json
+{
+  "kind": 9041,
+  "tags": [
+    ["relays", "wss://alicerelay.example.com", "wss://bobrelay.example.com", ...],
+    ["amount", "210000"],
+  ],
+  "content": "Nostrasia travel expenses",
+  ...other fields
+```
+
+The following tags are OPTIONAL.
+
+- `closed_at` - timestamp for determining which zaps are included in the tally. Zap receipts published after the `closed_at` timestamp SHOULD NOT count towards the goal progress.
+
+```json
+{
+  "kind": 9041,
+  "tags": [
+    ["relays", "wss://alicerelay.example.com", "wss://bobrelay.example.com", ...],
+    ["amount", "210000"],
+    ["closed_at", "<unix timestamp in seconds>"],
+  ],
+  "content": "Nostrasia travel expenses",
+  ...other fields
+```
+
+The goal MAY include an `r` or `a` tag linking to a URL or parameterized replaceable event.
+
+The goal MAY include multiple beneficiary pubkeys by specifying [`zap` tags](57.md#appendix-g-zap-tag-on-other-events).
+
+Parameterized replaceable events can link to a goal by using a `goal` tag specifying the event id and an optional relay hint.
+
+```json
+{
+  "kind": 3XXXX,
+  "tags": [
+    ...
+    ["goal", "<event id>", "<Relay URL (optional)>"],
+  ],
+  ...other fields
+```
+
+## Client behavior
+
+Clients MAY display funding goals on user profiles.
+
+When zapping a goal event, clients MUST include the relays in the `relays` tag of the goal event in the zap request `relays` tag.
+
+When zapping a parameterized replaceable event with a `goal` tag, clients SHOULD tag the goal event id in the `e` tag of the zap request.
+
+## Use cases
+
+- Fundraising clients
+- Adding funding goals to events such as long form posts, badges or live streams
diff --git a/94.md b/94.md
index 24dd346..c1b322a 100644
--- a/94.md
+++ b/94.md
@@ -13,7 +13,7 @@ The purpose of this NIP is to allow an organization and classification of shared
 This NIP specifies the use of the `1063` event type, having in `content` a description of the file content, and a list of tags described below:
 
 * `url` the url to download the file
-* `m` a string indicating the data type of the file. The MIME types format must be used (https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types)
+* `m` a string indicating the data type of the file. The [MIME types](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types/Common_types) format must be used, and they should be lowercase.
 * `"aes-256-gcm"` (optional)  key and nonce for AES-GCM encryption with tagSize always 128bits
 * `x` containing the SHA-256 hexencoded string of the file.
 * `size` (optional) size of file in bytes
diff --git a/98.md b/98.md
index ecbebc0..c8cba0f 100644
--- a/98.md
+++ b/98.md
@@ -6,9 +6,9 @@ HTTP Auth
 
 `draft` `optional` `author:kieran` `author:melvincarvalho`
 
-This NIP defines an ephemerial event used to authorize requests to HTTP servers using nostr events.
+This NIP defines an ephemeral event used to authorize requests to HTTP servers using nostr events.
 
-This is useful for HTTP services which are build for Nostr and deal with Nostr user accounts.
+This is useful for HTTP services which are built for Nostr and deal with Nostr user accounts.
 
 ## Nostr event
 
@@ -16,7 +16,7 @@ A `kind 27235` (In reference to [RFC 7235](https://www.rfc-editor.org/rfc/rfc723
 
 The `content` SHOULD be empty.
 
-The following tags are defined as REQUIRED.
+The following tags MUST be included.
 
 * `u` - absolute URL
 * `method` - HTTP Request Method
@@ -45,7 +45,7 @@ Example event:
 
 Servers MUST perform the following checks in order to validate the event:
 1. The `kind` MUST be `27235`.
-2. The `created_at` MUST be within a reasonable time window (suggestion 60 seconds).
+2. The `created_at` timestamp MUST be within a reasonable time window (suggestion 60 seconds).
 3. The `u` tag MUST be exactly the same as the absolute request URL (including query parameters).
 4. The `method` tag MUST be the same HTTP method used for the requested resource.
 
@@ -53,11 +53,11 @@ When the request contains a body (as in POST/PUT/PATCH methods) clients SHOULD i
 
 If one of the checks was to fail the server SHOULD respond with a 401 Unauthorized response code.
 
-All other checks which server MAY do are OPTIONAL, and implementation specific.
+Servers MAY perform additional implementation-specific validation checks.
 
 ## Request Flow
 
-Using the `Authorization` header, the `kind 27235` event MUST be `base64` encoded and use the Authorization scheme `Nostr`
+Using the `Authorization` HTTP header, the `kind 27235` event MUST be `base64` encoded and use the Authorization scheme `Nostr`
 
 Example HTTP Authorization header:
 ```
@@ -65,4 +65,4 @@ Authorization: Nostr eyJpZCI6ImZlOTY0ZTc1ODkwMzM2MGYyOGQ4NDI0ZDA5MmRhODQ5NGVkMjA
 ```
 
 ## Reference Implementations
-- C# ASP.NET `AuthenticationHandler` [NostrAuth.cs](https://gist.github.com/v0l/74346ae530896115bfe2504c8cd018d3)
\ No newline at end of file
+- C# ASP.NET `AuthenticationHandler` [NostrAuth.cs](https://gist.github.com/v0l/74346ae530896115bfe2504c8cd018d3)
diff --git a/README.md b/README.md
index 7951339..98f6ddb 100644
--- a/README.md
+++ b/README.md
@@ -63,6 +63,7 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos
 - [NIP-58: Badges](58.md)
 - [NIP-65: Relay List Metadata](65.md)
 - [NIP-72: Moderated Communities](72.md)
+- [NIP-75: Zap Goals](75.md)
 - [NIP-78: Application-specific data](78.md)
 - [NIP-89: Recommended Application Handlers](89.md)
 - [NIP-94: File Metadata](94.md)
@@ -93,6 +94,7 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos
 | `1984`  | Reporting                  | [56](56.md) |
 | `1985`  | Label                      | [32](32.md) |
 | `4550`  | Community Post Approval    | [72](72.md) |
+| `9041`  | Zap Goal                   | [75](75.md) |
 | `9734`  | Zap Request                | [57](57.md) |
 | `9735`  | Zap                        | [57](57.md) |
 | `10000` | Mute List                  | [51](51.md) |
@@ -159,12 +161,13 @@ Please update these lists when proposing NIPs introducing new event kinds.
 | `p`               | pubkey (hex)                         | relay URL, petname   | [01](01.md), [02](02.md) |
 | `a`               | coordinates to an event              | relay URL            | [01](01.md)              |
 | `d`               | identifier                           | --                   | [01](01.md)              |
-| `alt`             | Alt tag                              | --                   | [31](31.md)              |
+| `alt`             | summary                              | --                   | [31](31.md)              |
 | `g`               | geohash                              | --                   | [52](52.md)              |
 | `i`               | identity                             | proof                | [39](39.md)              |
 | `k`               | kind number (string)                 | --                   | [18](18.md), [72](72.md) |
 | `l`               | label, label namespace               | annotations          | [32](32.md)              |
 | `L`               | label namespace                      | --                   | [32](32.md)              |
+| `m`               | MIME type                            | --                   | [94](94.md)              |
 | `r`               | a reference (URL, etc)               | petname              |                          |
 | `r`               | relay url                            | marker               | [65](65.md)              |
 | `t`               | hashtag                              | --                   |                          |
@@ -173,10 +176,10 @@ Please update these lists when proposing NIPs introducing new event kinds.
 | `challenge`       | challenge string                     | --                   | [42](42.md)              |
 | `content-warning` | reason                               | --                   | [36](36.md)              |
 | `delegation`      | pubkey, conditions, delegation token | --                   | [26](26.md)              |
-| `description`     | badge description                    | --                   | [58](58.md)              |
-| `description`     | invoice description                  | --                   | [57](57.md)              |
+| `description`     | invoice/badge description            | --                   | [57](57.md), [58](58.md) |
 | `emoji`           | shortcode, image URL                 | --                   | [30](30.md)              |
 | `expiration`      | unix timestamp (string)              | --                   | [40](40.md)              |
+| `goal`            | event id (hex)                       | relay URL            | [75](75.md)              |
 | `image`           | image URL                            | dimensions in pixels | [23](23.md), [58](58.md) |
 | `lnurl`           | `bech32` encoded `lnurl`             | --                   | [57](57.md)              |
 | `location`        | location string                      | --                   | [52](52.md), [99](99.md) |