nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-11-10 06:09:08 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update 70.md

Browse Source
This commit is contained in:
LeandroBitcoiner21 2023-03-28 19:40:03 -03:00 committed by GitHub
parent 1e5f27a64b
commit 973fe01407
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 35 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

38
70.md
View File

@ -10,9 +10,9 @@ Collaborative Events
Collaborative Events are events involving several users that can be useful for applications such as publications involving several users, creation of content involving several content producers, publications by companies with the signature of several partners, public digital contracts, etc. Collaborative Events are events involving several users that can be useful for applications such as publications involving several users, creation of content involving several content producers, publications by companies with the signature of several partners, public digital contracts, etc.
The event is created and signed by its creator, then he distributes the event for the other users involved to sign, sending can be done in several ways, for example through `Encrypted Direct Message KIND-4`, after the event is signed by all parties involved, it can be sent to the relays. The event is created and signed by its creator, then he distributes the event for the other users involved to sign, sending can be done in several ways, for example through `Encrypted Direct Message KIND-4`, after the event is signed by all parties involved, it can be sent to the relays, the collaborative event can be replaceable or not, if it is not replaceable it will be identified by `KIND-70`, if it is replaceable it will be identified by `KIND-10070`
## Example: ## Fully Signed Example:
```json ```json
{ {
@ -26,4 +26,36 @@ The event is created and signed by its creator, then he distributes the event fo
} }
``` ```
Collaborative events are identified by `KIND-70` ## Fully Signed Replaceable Example:
```json
{
"id": <id>,
"pubkey": [<pubkey1>, <pubkey2>],
"created_at": <created_at>,
"kind": 10070,
"tags": [],
"content": <content>,
"sig": [<sig1>, <sig2>]
}
```
## Partially Signed Collaborative Event
A partially signed collaborative event can be published but in that case it must be replaced every time a new signature is added and therefore a partially signed collaborative event is identified by `KIND-10069`
## Partially Signed Example:
```json
{
"id": <id>,
"pubkey": [<pubkey1>, <pubkey2>],
"created_at": <created_at>,
"kind": 10069,
"tags": [],
"content": <content>,
"sig": [<sig1>]
}
```
After a collaborative event is fully signed by the involved parties it can be published as replaceable or not according to the first 2 examples.