2024
A Response is an event that actions a Quote. Like quotes, response content is end-to-end encrypted (NIP-44) — only the two parties in the thread can read it.
Thread Closure
A quoting thread can be closed in two ways: rejection (by either party), or mutual acceptance (both parties accept). The"s" and "z" tags track the state of the thread:
s— The response status:"accepted"or"rejected".z— The thread finalization state:"pending"(awaiting the other party) or"complete"(thread closed).
| Scenario | s | z |
|---|---|---|
| Rejected | rejected | complete |
| First party accepts | accepted | pending |
| Second party accepts (final closure) | accepted | complete |
["s", "accepted"]. Once both parties have accepted and the thread is marked "complete", the transaction is considered closed.
Content:
This is the plaintext JSON content before encryption. The resulting ciphertext is placed in the content field of the event.
- Responses SHOULD copy the listing tags over.
- Responses MUST set the recipient
"p"tag to the quote event’s Author pubkey. - Responses MUST set the status
"s"tag toacceptedorrejected. - Responses MUST set the status
"z"tag topendingif they are the first to accept, orcompleteif they reject, or are accepting another accepted response. - Responses MUST be published to the listing’s
"r"tag inbox node URL, as well as the sender’s inbox node.

