NIPs nostr improvement proposals

NIP-75 - Zap Goals

Table of Contents

Zap Goals

draft optional

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.

Example event:

{
"kind": 9041,
"tags": [
["relays", "wss://alicerelay.example.com", "wss://bobrelay.example.com", ...],
["amount", "210000"],
],
"content": "Nostrasia travel expenses",
...

The following tags are OPTIONAL.

{
"kind": 9041,
"tags": [
["relays", "wss://alicerelay.example.com", "wss://bobrelay.example.com", ...],
["amount", "210000"],
["closed_at", "<unix timestamp in seconds>"],
["image", "<image URL>"],
["summary", "<description of the goal>"],
],
"content": "Nostrasia travel expenses",
...
}

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.

Parameterized replaceable events can link to a goal by using a goal tag specifying the event id and an optional relay hint.

{
...
"kind": 3xxxx,
"tags": [
...
["goal", "<event id>", "<Relay URL (optional)>"],
],
...
}

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