laantungir/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2025-12-13 18:38:52 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'master' into simplify-nuts

Browse Source
This commit is contained in:
fiatjaf_
2025-02-03 15:23:38 -03:00
committed by GitHub
parent bb88c66c1d 8577545faa
commit 4ab75f0c3d
3 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
60.md
View File

@@ -71,7 +71,6 @@ There can be multiple `kind:7375` events for the same mint, and multiple proofs
* `proofs`: unecoded proofs
* `del`: token-ids that were destroyed by the creation of this token. This assists with state transitions.
### Spending proofs
When one or more proofs of a token are spent, the token event should be [NIP-09](09.md)-deleted and, if some proofs are unspent from the same token event, a new token event should be created rolling over the unspent proofs and adding any change outputs to the new token event (the change output should include a `del` field).
The `kind:5` _delete event_ created in the [NIP-09](09.md) process MUST have a tag `["k", "7375"]` to allow easy filtering by clients interested in state transitions.
@@ -100,6 +99,8 @@ Clients MUST add `e` tags to create references of destroyed and created token ev
* `destroyed` - A token event was destroyed.
* `redeemed` - A [NIP-61](61.md) nutzap was redeemed.
All tags can be [NIP-44](44.md) encrypted. Clients SHOULD leave `e` tags with a `redeemed` marker unencrypted.
Multiple `e` tags can be added, and should be encrypted, except for tags with the `redeemed` marker.
# Flow