### Non-Technical Explanation of NIP-79
NIP-79 is a proposal that seeks to introduce a standardized way of handling digital contracts, covenants, and agreements within the Nostr protocol. In simple terms, this protocol acts as a digital platform that allows parties involved in a contract to interact in a more secure and verifiable manner. Here is a detailed explanation of each section:
1. Types of Documents:
- 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: The documents will be in Markdown format, allowing for structured and human-readable presentation.
3. Metadata: Specific metadata fields can be added to the event, such as the title of the contract, the parties involved, the signing date, the expiration date, etc.
4. Timestamping with OpenTimestamps: Once signed, OpenTimestamps can be used to create a cryptographic proof of the contract's existence at a specific moment, stored on the Bitcoin blockchain.
5. References and Linking: Documents can reference other events in Nostr, such as annexes, terms and conditions, or other relevant documents.
6. New 'kind' Definitions: New definitions are introduced to categorize different stages and elements of the contractual process.
### Usage Example:
Imagine that two companies, Company A and Company B, decide to enter into a collaboration contract. Here is how they might use this protocol:
1. Contract Creation: Company A creates a draft of the contract on the platform, detailing the terms and conditions of their collaboration with Company B.
2. Review and Signature: Company B reviews the contract, and once they are satisfied with the terms, both parties digitally sign the contract on the platform.
3. Signature Witnesses: Witnesses can be designated to verify the authenticity of the signatures involved, adding an additional layer of verification to the signing process.
4. Contract Execution: Once all parties have signed, the contract is officially activated on the platform, marking the beginning of the collaboration.
5. Verification and Security: At any time, the parties can verify the authenticity and integrity of the contract on the platform, ensuring that the agreed terms remain intact and secure.
This protocol, therefore, facilitates a more secure, transparent, and efficient contractual process, which could be of great value in the legal world.
CC NostReport (npub19md…6vzk)
vpirato
npub1kk…jqz9u
2023-09-04 17:17:49
in reply to nevent1q…457k
Author Public Key
npub1kkm4ueng5fyta3p20dwcvr5433ufeyh88dq592ngqr9azw7pwtjqejqz9uPublished at
2023-09-04 17:17:49Event JSON
{
"id": "7a01dfc450d068ad207750ce90407d77127facc547fc859824535159641314e7",
"pubkey": "b5b75e6668a248bec42a7b5d860e958c789c92e73b4142aa6800cbd13bc172e4",
"created_at": 1693847869,
"kind": 1,
"tags": [
[
"e",
"09069fc2bc7aae61b13fb9ee5a743bb11473fd65c03e6bf52aedbac623b921fc",
"",
"reply"
],
[
"p",
"b5b75e6668a248bec42a7b5d860e958c789c92e73b4142aa6800cbd13bc172e4"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
],
[
"p",
"2edbcea694d164629854a52583458fd6d965b161e3c48b57d3aff01940558884",
"",
"mention"
]
],
"content": "### Non-Technical Explanation of NIP-79\n\nNIP-79 is a proposal that seeks to introduce a standardized way of handling digital contracts, covenants, and agreements within the Nostr protocol. In simple terms, this protocol acts as a digital platform that allows parties involved in a contract to interact in a more secure and verifiable manner. Here is a detailed explanation of each section:\n\n1. Types of Documents:\n - Contract: A legally binding agreement between two or more parties.\n - Covenant: A written promise or restriction within a contract or agreement.\n - Agreement: A mutual understanding between parties regarding their relative rights and responsibilities.\n\n2. Format: The documents will be in Markdown format, allowing for structured and human-readable presentation.\n\n3. Metadata: Specific metadata fields can be added to the event, such as the title of the contract, the parties involved, the signing date, the expiration date, etc.\n\n4. Timestamping with OpenTimestamps: Once signed, OpenTimestamps can be used to create a cryptographic proof of the contract's existence at a specific moment, stored on the Bitcoin blockchain.\n\n5. References and Linking: Documents can reference other events in Nostr, such as annexes, terms and conditions, or other relevant documents.\n\n6. New 'kind' Definitions: New definitions are introduced to categorize different stages and elements of the contractual process.\n\n### Usage Example:\n\nImagine that two companies, Company A and Company B, decide to enter into a collaboration contract. Here is how they might use this protocol:\n\n1. Contract Creation: Company A creates a draft of the contract on the platform, detailing the terms and conditions of their collaboration with Company B.\n \n2. Review and Signature: Company B reviews the contract, and once they are satisfied with the terms, both parties digitally sign the contract on the platform.\n\n3. Signature Witnesses: Witnesses can be designated to verify the authenticity of the signatures involved, adding an additional layer of verification to the signing process.\n\n4. Contract Execution: Once all parties have signed, the contract is officially activated on the platform, marking the beginning of the collaboration.\n\n5. Verification and Security: At any time, the parties can verify the authenticity and integrity of the contract on the platform, ensuring that the agreed terms remain intact and secure.\n\nThis protocol, therefore, facilitates a more secure, transparent, and efficient contractual process, which could be of great value in the legal world.\n\nCC nostr:npub19mduaf5569jx9xz555jcx3v06mvktvtpu0zgk47n4lcpjsz43zzqhj6vzk",
"sig": "644c4c2718c5d1619b9670fb67196aa5dff60fe0e4e45a8e77f5cec226b228ed0c8aff120cd2be0a4b5f82b9608ee9c4aaab3cc304c4f0c8dfe827d897544f34"
}