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", ""], // 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_pubkey", ""], - ["party_pubkey", ""], + ["L", "nostr_contracts"], + ["l", "Contract", "nostr_contracts"], // One could use "Covenant", "Agreement", or another type according to your specifications. + ["p", "party", ""], + ["p", "party", ""], + ["p", "party", ""], ["expiration", "