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

feat(nip-79): add jurisdiction tag to contract model

Browse Source 
Added a new 'jurisdiction' tag to the contract model in NIP-79 to specify the legal jurisdiction for the contract. The tag includes details such as the court name and geographical location (city, state, country).
This commit is contained in:
Sergio Ovalle 2023-09-04 20:31:18 -06:00
parent c0ec7ca8fc
commit 5f20ab6b0e
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
79.md
View File

@ -28,7 +28,7 @@ As digital transactions, promises, and agreements become more prevalent, it's es
- `parties`: Parties involved.
- `signed_date`: Date it was signed.
- `expiry_date`: Expiration date, if applicable.
- `type`: Whether it's a Contract, Covenant, or Agreement.
- `jurisdiction`: Specifies the legal jurisdiction governing the contract. It should include details such as the court, city, state, and country. For example, `["jurisdiction","Superior Court of California","San Francisco","California","USA"]`.
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.
@ -52,6 +52,7 @@ 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
["jurisdiction","[Court Name]","[City]","[State]","[Country]"],
["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>"],
@ -112,6 +113,7 @@ The contract execution represents the finalization and activation of the contrac
["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
["jurisdiction","[Court Name]","[City]","[State]","[Country]"],
["e", "<Contract's (kind:900) Event ID>" ], // Base text.
["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"],