nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-23 00:45:53 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

fix(79.md): update internal links for better navigation

Browse Source
This commit is contained in:
Sergio Ovalle 2023-09-03 12:07:11 -06:00
parent 0151f1f988
commit c0ec7ca8fc
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
79.md
View File

@ -16,12 +16,12 @@ As digital transactions, promises, and agreements become more prevalent, it's es
### Specification
1. **Types**(Following NIP-32 for label structure):
1. **Types**: Following [NIP-32](32.md) 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.
2. **Format**: Following [NIP-23](23.md) (Long-form Content), the content should be in Markdown format to structure and present the content in a human-readable manner.
3. **Metadata**: Specific application metadata fields can be added to the event, such as:
- `title`: Title of the contract, covenant, or agreement.
@ -30,7 +30,7 @@ As digital transactions, promises, and agreements become more prevalent, it's es
- `expiry_date`: Expiration date, if applicable.
- `type`: Whether it's a Contract, Covenant, or Agreement.
4. **Timestamping with OpenTimestamps**: Following NIP-03 (OpenTimestamps Attestations for Events), once signed, OpenTimestamps can be used to create a cryptographic proof of existence at a specific moment. This proof is stored on the Bitcoin blockchain, providing immutable evidence of the date and time of signing. For those unfamiliar with OpenTimestamps, it's a system for creating provable timestamps recorded on the Bitcoin blockchain.
4. **Timestamping with OpenTimestamps**: Following [NIP-03](03.md) (OpenTimestamps Attestations for Events), once signed, OpenTimestamps can be used to create a cryptographic proof of existence at a specific moment. This proof is stored on the Bitcoin blockchain, providing immutable evidence of the date and time of signing. For those unfamiliar with OpenTimestamps, it's a system for creating provable timestamps recorded on the Bitcoin blockchain.
5. **References and Linking**: Can reference other events in Nostr, such as annexes, terms and conditions, or any other relevant document.
@ -128,6 +128,6 @@ The contract execution represents the finalization and activation of the contrac
### Considerations
- Should be treated with a high level of security and privacy. Protect the private keys used for signing, as outlined in NIP-24.
- Should be treated with a high level of security and privacy. Protect the private keys used for signing, as outlined in [NIP-24](24.md).
- Verifying the authenticity and integrity is crucial. Ensure the public key used to verify a signature genuinely belongs to the indicated signer.
- Recommended to consult with legal experts when using the Nostr protocol for these purposes.