diff options
| -rw-r--r-- | 88.md | 8 |
1 files changed, 6 insertions, 2 deletions
| @@ -45,6 +45,9 @@ A pubkey that wants to provide others the ability to subscribe to them can creat | |||
| 45 | // Relay and payment-verification | 45 | // Relay and payment-verification |
| 46 | [ "r", "wss://my-subscribers-only-relay.com" ], | 46 | [ "r", "wss://my-subscribers-only-relay.com" ], |
| 47 | [ "p", "<payment-verifier-pubkey>" ], | 47 | [ "p", "<payment-verifier-pubkey>" ], |
| 48 | |||
| 49 | // A unique identifier | ||
| 50 | [ "d", "<random-id>" ], | ||
| 48 | ] | 51 | ] |
| 49 | } | 52 | } |
| 50 | ``` | 53 | ``` |
| @@ -77,7 +80,7 @@ Zero or more `p` tags can be included to specify a pubkey that is trusted by the | |||
| 77 | "content": "<optional-message>", | 80 | "content": "<optional-message>", |
| 78 | "tags": [ | 81 | "tags": [ |
| 79 | [ "p", "<recipient-pubkey>" ], | 82 | [ "p", "<recipient-pubkey>" ], |
| 80 | [ "a", "<supporting-tier-event-id>" ], | 83 | [ "e", "<supporting-tier-event-id>" ], |
| 81 | [ "event", "<stringied-event-subscribed-to>" ], | 84 | [ "event", "<stringied-event-subscribed-to>" ], |
| 82 | [ "amount", "<amount-in-base-unit>", "<currency>", "<cadence>" ], | 85 | [ "amount", "<amount-in-base-unit>", "<currency>", "<cadence>" ], |
| 83 | 86 | ||
| @@ -92,7 +95,7 @@ When a user wants to subscribe to support a user they create a `kind:7001` event | |||
| 92 | 95 | ||
| 93 | * `.content` is an optional message the supporter can write. | 96 | * `.content` is an optional message the supporter can write. |
| 94 | * The `p` tag MUST tag the pubkey being supported. | 97 | * The `p` tag MUST tag the pubkey being supported. |
| 95 | * The `a` tag is optional; it should point to a `kind:37001` support tier event. There MUST be exactly 0 or 1 `a` tag. | 98 | * The `e` tag is optional; it should point to a `kind:37001` support tier event. There MUST be exactly 0 or 1 `e` tag. |
| 96 | * The `event` tag is optional; subscribers can opt to keep the version of the event they subscribed to. There MUST be exactly 0 or 1 `event` tag. | 99 | * The `event` tag is optional; subscribers can opt to keep the version of the event they subscribed to. There MUST be exactly 0 or 1 `event` tag. |
| 97 | * The `amount` tag specifies what the supporters is committing to pay to the supported pubkey and the cadence. MUST be equal to one of the amounts specified in the | 100 | * The `amount` tag specifies what the supporters is committing to pay to the supported pubkey and the cadence. MUST be equal to one of the amounts specified in the |
| 98 | `kind:37001` event if one is tagged. There MUST be exactly 1 `amount` tag. | 101 | `kind:37001` event if one is tagged. There MUST be exactly 1 `amount` tag. |
| @@ -113,6 +116,7 @@ The supporting user should create a zap `p`-tagging the receiver and e-tagging t | |||
| 113 | [ "p", "<recipient-pubkey>" ], | 116 | [ "p", "<recipient-pubkey>" ], |
| 114 | [ "e", "<kind-7001-event-id>" ] | 117 | [ "e", "<kind-7001-event-id>" ] |
| 115 | ] | 118 | ] |
| 119 | } | ||
| 116 | ``` | 120 | ``` |
| 117 | 121 | ||
| 118 | Clients supporting this NIP can check for zaps e-tagging the `kind:7001` event to find the pubkeys that have a valid, paid subscriptions at each different period. | 122 | Clients supporting this NIP can check for zaps e-tagging the `kind:7001` event to find the pubkeys that have a valid, paid subscriptions at each different period. |