From ae2708a4f56243f9b34a458e83c2bc765a57712a Mon Sep 17 00:00:00 2001
From: Sergio Ovalle <sergio@lynx.com.gt>
Date: Sun, 3 Sep 2023 11:08:15 -0600
Subject: [PATCH] feat: Update contract types with NIP-32 label structure

- Added NIP-32 instruction for label structure in the "Types" section.
- Updated the definitions for Contract, Covenant, and Agreement.
---
 79.md | 27 ++++++++++++++-------------
 1 file changed, 14 insertions(+), 13 deletions(-)

diff --git a/79.md b/79.md
index 97a0ca1..5c8e62a 100644
--- a/79.md
+++ b/79.md
@@ -4,7 +4,7 @@ NIP-79
 Digital Contracts
 -----------------
 
-`draft` `optional` `author:vpirato` `author:vitorpamplona`
+`draft` `optional` `author:vpirato` `collaborator:vitorpamplona` `collaborator:brandenespinoza`
 
 ### Abstract
 
@@ -16,14 +16,14 @@ As digital transactions, promises, and agreements become more prevalent, it's es
 
 ### Specification
 
-1. **Types**:
+1. **Types**(Following NIP-32 for label structure):
    - **Contract**: A legally binding agreement between two or more parties.
    - **Covenant**: A written promise or restriction within a contract or agreement.
    - **Agreement**: A mutual understanding between parties regarding their relative rights and responsibilities.
 
 2. **Format**: Following NIP-23 (Long-form Content), the content should be in Markdown format to structure and present the content in a human-readable manner.
 
-3. **Metadata**: Using NIP-78 (Application-specific data), specific application metadata fields can be added to the event, such as:
+3. **Metadata**: Specific application metadata fields can be added to the event, such as:
    - `title`: Title of the contract, covenant, or agreement.
    - `parties`: Parties involved.
    - `signed_date`: Date it was signed.
@@ -52,10 +52,11 @@ As digital transactions, promises, and agreements become more prevalent, it's es
     ["summary", "<Short Description>"],  // Optional: Short Description for preview
     ["valid_from", "Timestamp"], // Optional: Start date of the contract 
     ["valid_to", "Timestamp"],   // Optional: End date of the contract 
-    ["type", "Contract"],
-    ["party_pubkey", "<party's 1 pubkey>"],
-    ["party_pubkey", "<party's 2 pubkey>"],
-    ["party_pubkey", "<party's 3 pubkey>"],
+    ["L", "nostr_contracts"],
+    ["l", "Contract", "nostr_contracts"], // One could use "Covenant", "Agreement", or another type according to your specifications.
+    ["p", "party", "<party's 1 pubkey>"],
+    ["p", "party", "<party's 2 pubkey>"],
+    ["p", "party", "<party's 3 pubkey>"],
     ["expiration", "<Time stamp limit to sign>"],
   ],
   "pubkey": "[Signer's Public Key]",
@@ -113,12 +114,12 @@ The contract execution represents the finalization and activation of the contrac
     ["valid_from", "Timestamp"], // Optional: Start date of the contract 
     ["valid_to", "Timestamp"],   // Optional: End date of the contract 
     ["e", "<Contract's (kind:900) Event ID>" ], // Base text. 
-    ["party_pubkey", "<party's 1 pubkey>", "Stringified JSON of the signed kind:901"],
-    ["party_pubkey", "<party's 2 pubkey>", "Stringified JSON of the signed kind:901"],
-    ["party_pubkey", "<party's 3 pubkey>", "Stringified JSON of the signed kind:901"],
-    ["witness_pubkey", "<party's 4 pubkey>", "Stringified JSON of the signed kind:902"],
-    ["witness_pubkey", "<party's 5 pubkey>", "Stringified JSON of the signed kind:902"],
-    ["witness_pubkey", "<party's 6 pubkey>", "Stringified JSON of the signed kind:902"]
+    ["p", "party", "<party's 1 pubkey>", "Stringified JSON of the signed kind:901"],
+    ["p", "party", "<party's 2 pubkey>", "Stringified JSON of the signed kind:901"],
+    ["p", "party", "<party's 3 pubkey>", "Stringified JSON of the signed kind:901"],
+    ["p", "witness", "<party's 4 pubkey>", "Stringified JSON of the signed kind:902"],
+    ["p", "witness", "<party's 5 pubkey>", "Stringified JSON of the signed kind:902"],
+    ["p", "witness", "<party's 6 pubkey>", "Stringified JSON of the signed kind:902"]
   ],
   "pubkey": "[Signer's Public Key]",
   "id": "[Event ID]",