diff options
| author | fiatjaf_ <fiatjaf@gmail.com> | 2025-02-03 15:23:38 -0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-02-03 15:23:38 -0300 |
| commit | 4ab75f0c3db12c9213b915e5e91041dc892b75ae (patch) | |
| tree | dbb2b632f6bd2709d17e342b3a1eb7bc23be434c /60.md | |
| parent | bb88c66c1dbbdaed6283e594f33e59452ae9eada (diff) | |
| parent | 8577545faad887396d413707bc9020d024407818 (diff) | |
Merge branch 'master' into simplify-nuts
Diffstat (limited to '60.md')
| -rw-r--r-- | 60.md | 3 |
1 files changed, 2 insertions, 1 deletions
| @@ -71,7 +71,6 @@ There can be multiple `kind:7375` events for the same mint, and multiple proofs | |||
| 71 | * `proofs`: unecoded proofs | 71 | * `proofs`: unecoded proofs |
| 72 | * `del`: token-ids that were destroyed by the creation of this token. This assists with state transitions. | 72 | * `del`: token-ids that were destroyed by the creation of this token. This assists with state transitions. |
| 73 | 73 | ||
| 74 | ### Spending proofs | ||
| 75 | 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). | 74 | 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). |
| 76 | 75 | ||
| 77 | 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. | 76 | 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 | |||
| 100 | * `destroyed` - A token event was destroyed. | 99 | * `destroyed` - A token event was destroyed. |
| 101 | * `redeemed` - A [NIP-61](61.md) nutzap was redeemed. | 100 | * `redeemed` - A [NIP-61](61.md) nutzap was redeemed. |
| 102 | 101 | ||
| 102 | All tags can be [NIP-44](44.md) encrypted. Clients SHOULD leave `e` tags with a `redeemed` marker unencrypted. | ||
| 103 | |||
| 103 | Multiple `e` tags can be added, and should be encrypted, except for tags with the `redeemed` marker. | 104 | Multiple `e` tags can be added, and should be encrypted, except for tags with the `redeemed` marker. |
| 104 | 105 | ||
| 105 | # Flow | 106 | # Flow |