From 3815a6fd09529e82454c08f2ea59e18ab660b901 Mon Sep 17 00:00:00 2001 From: ben Date: Fri, 9 Jun 2023 12:20:18 +0100 Subject: [PATCH 01/24] init --- NIP-121.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 NIP-121.md diff --git a/NIP-121.md b/NIP-121.md new file mode 100644 index 00000000..49d1614a --- /dev/null +++ b/NIP-121.md @@ -0,0 +1,19 @@ +NIP-121 +====== + +Unicast event `"tags": "r"` +------------------------------- + +`draft` `mandatory` `author:benarc` + +`route` list of relays as a new tag `"r"`, to help create a unicast route for an events. + +```json +{ + "tags": [ + ["r", ""] + ] +} +``` + +A client receives an event with tag `"r"`, if the client received the event from a relay in the list and it has a connection with the next relay in the list, the client will pass the event to that relay. \ No newline at end of file From 4cf6ea7137151a5e41976526aa1b6570d04df950 Mon Sep 17 00:00:00 2001 From: Ben Date: Thu, 29 Jun 2023 11:40:25 +0100 Subject: [PATCH 02/24] added nostr cash --- 88.md | 189 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 189 insertions(+) create mode 100644 88.md diff --git a/88.md b/88.md new file mode 100644 index 00000000..62ee3420 --- /dev/null +++ b/88.md @@ -0,0 +1,189 @@ +NIP-15 +====== + +Nostr Cash (simple Nostr ecash) +----------------------------------- + +`draft` `optional` `author:benarc` + +> Nostr Cash is not blinded by default. + +Ecash is useful and relays should have the option to offer ecash mints. Other mints could exist as stand-alone clients, but relays are ideally placed to package in with their service offerings. + +Users can use relays offering mints they trust, or mints and relays they don't trust but for smaller amounts. + +The relay must have a keypair and an additional keypair for its mint. + +Nostr Cash uses derived keys, much like [NIP26](https://github.com/nostr-protocol/nips/blob/master/26.md). + +All communication between the relay and user happen over [NIP04](https://github.com/nostr-protocol/nips/blob/master/04.md). + +The mints ledger is two tables `active` and `spent`: + +``` +active: + key: , + amount: , + user: , + timestamp: + +spent: + key: , + amount: , + user: , + timestamp: +``` + +User client ecash wallet stores: + +``` +active: + key: , + amount: , + relay: , + relaykey: , + timestamp: + +spent: + key: , + amount: , + relay: , + relaykey: , + timestamp: +``` + +## Workflows + +### Mint details + +User DMs the relay: + +```json +{ + "mint": +} +``` + +Relay DMs user (maybe after a check if the relays mint has restricted access): + +```json +{ + "title": , + "description": , + "liquiity": , + "type": , + "fee": , +} +``` + +### Minting + +User DMs the relay: + +```json +{ + "amount": +} +``` + +Relay responds with payment request, which user pays: + +```json{ +{ + "request": , +} +``` + +Once paid the mint generates derived keypair from the mints private key, storing in table `active`: + +```json +{ + "key": , + "amount": , + "user": +} +``` + +Mint replies: + +```json +{ + "key": , + "amount": +} +``` + +User client stores: + +```json +{ + "key": , + "amount": , + "relay": , + "relaykey": , + "timestamp": , + "amount": , + "type": +} +``` + +Relay DMs user: + +```json +{ + "type": +} +``` + +User DMs relay: + +```json +{ + "request": , +} +``` + +### Sending + +User DMs relay: + +```json +{ + "key": , + "amount": , + "type": +} +``` + +Mint `burns` the old record for the ecash and creates a new record(s), depending on if sending user is owed change (the old record from `active` to `spent` table). The mint creates a new record in `active` and DMs the recipient user the private-key/ecash. If change is due, another record is created in `active` and sent back to the sender user. + +Relay DMs user(s): + +```json +{ + "key": , + "amount": +} +``` + +User(s) client stores: + +```json +{ + "key": , + "amount": , + "relay": , + "relaykey": , + "timestamp": Date: Thu, 29 Jun 2023 11:51:14 +0100 Subject: [PATCH 03/24] Update 88.md --- 88.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/88.md b/88.md index 62ee3420..fce34a6f 100644 --- a/88.md +++ b/88.md @@ -10,9 +10,9 @@ Nostr Cash (simple Nostr ecash) Ecash is useful and relays should have the option to offer ecash mints. Other mints could exist as stand-alone clients, but relays are ideally placed to package in with their service offerings. -Users can use relays offering mints they trust, or mints and relays they don't trust but for smaller amounts. +Users can use relays offering mints they trust, or relays they don't trust but for smaller amounts. -The relay must have a keypair and an additional keypair for its mint. +Relays offering mints must have a keypair and an additional nostr keypair for its mint. Nostr Cash uses derived keys, much like [NIP26](https://github.com/nostr-protocol/nips/blob/master/26.md). From a0bf41e8606cc60528fae3e2e9f60406a7229670 Mon Sep 17 00:00:00 2001 From: Arc <33088785+arcbtc@users.noreply.github.com> Date: Thu, 29 Jun 2023 11:53:08 +0100 Subject: [PATCH 04/24] Update 88.md --- 88.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/88.md b/88.md index fce34a6f..bcb92122 100644 --- a/88.md +++ b/88.md @@ -90,7 +90,7 @@ Relay responds with payment request, which user pays: ```json{ { - "request": , + "request": , } ``` From c831ee252fe319b149960c8ef7edf803048831ff Mon Sep 17 00:00:00 2001 From: Arc <33088785+arcbtc@users.noreply.github.com> Date: Thu, 29 Jun 2023 11:53:36 +0100 Subject: [PATCH 05/24] Update 88.md --- 88.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/88.md b/88.md index bcb92122..b2334105 100644 --- a/88.md +++ b/88.md @@ -90,7 +90,7 @@ Relay responds with payment request, which user pays: ```json{ { - "request": , + "request": , } ``` From 72d686ff3ae834674ebc92659515052b655668e9 Mon Sep 17 00:00:00 2001 From: Arc <33088785+arcbtc@users.noreply.github.com> Date: Thu, 29 Jun 2023 11:53:47 +0100 Subject: [PATCH 06/24] Update 88.md --- 88.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/88.md b/88.md index b2334105..01356395 100644 --- a/88.md +++ b/88.md @@ -1,4 +1,4 @@ -NIP-15 +NIP-88 ====== Nostr Cash (simple Nostr ecash) From 6c273e42bfff126cc7305c365c4b8cc967d91f87 Mon Sep 17 00:00:00 2001 From: Ben Date: Thu, 29 Jun 2023 11:57:14 +0100 Subject: [PATCH 07/24] typo --- 88.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/88.md b/88.md index 01356395..625ac86d 100644 --- a/88.md +++ b/88.md @@ -90,7 +90,7 @@ Relay responds with payment request, which user pays: ```json{ { - "request": , + "request": , } ``` @@ -100,7 +100,7 @@ Once paid the mint generates derived keypair from the mints private key, storing { "key": , "amount": , - "user": + "user": } ``` @@ -119,7 +119,7 @@ User client stores: { "key": , "amount": , - "relay": , + "relay": , "relaykey": , "timestamp": Date: Thu, 29 Jun 2023 11:58:37 +0100 Subject: [PATCH 08/24] typos --- 88.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/88.md b/88.md index 625ac86d..4357386f 100644 --- a/88.md +++ b/88.md @@ -88,9 +88,9 @@ User DMs the relay: Relay responds with payment request, which user pays: -```json{ +```json { - "request": , + "request": } ``` @@ -121,7 +121,7 @@ User client stores: "amount": , "relay": , "relaykey": , - "timestamp": } ``` @@ -184,6 +184,6 @@ User(s) client stores: "amount": , "relay": , "relaykey": , - "timestamp": } ``` From aef4ad0e53d6dfb36600c835c2faef7e30774d2c Mon Sep 17 00:00:00 2001 From: Ben Date: Thu, 29 Jun 2023 11:59:25 +0100 Subject: [PATCH 09/24] typo --- 88.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/88.md b/88.md index 4357386f..133e9bde 100644 --- a/88.md +++ b/88.md @@ -165,7 +165,7 @@ User DMs relay: } ``` -Mint `burns` the old record for the ecash and creates a new record(s), depending on if sending user is owed change (the old record from `active` to `spent` table). The mint creates a new record in `active` and DMs the recipient user the private-key/ecash. If change is due, another record is created in `active` and sent back to the sender user. +Mint `burns` the old record for the ecash and creates a new record(s), depending on if sending user is owed change (the old record moves from `active` to `spent` table). The mint creates a new record in `active` and DMs the recipient user the private-key/ecash. If change is due, another record is created in `active` and sent back to the sender user. Relay DMs user(s): From d3b5da312d7a6db400bdf68a369debfae6479ab5 Mon Sep 17 00:00:00 2001 From: Ben Date: Thu, 29 Jun 2023 12:08:28 +0100 Subject: [PATCH 10/24] adding descriptions for workflows --- 88.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/88.md b/88.md index 133e9bde..be536612 100644 --- a/88.md +++ b/88.md @@ -78,6 +78,8 @@ Relay DMs user (maybe after a check if the relays mint has restricted access): ### Minting +**For creating new ecash from a mint.** + User DMs the relay: ```json @@ -127,6 +129,8 @@ User client stores: ### Claiming +**For cashing in ecash with the mint.** + User DMs relay: ```json @@ -155,6 +159,8 @@ User DMs relay: ### Sending +**For sending ecash to another nostr user.** + User DMs relay: ```json From b0526aec4dd57d358a3d4ec90739a723d3f8dd18 Mon Sep 17 00:00:00 2001 From: Ben Date: Thu, 29 Jun 2023 12:11:06 +0100 Subject: [PATCH 11/24] Expanded explanation --- 88.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/88.md b/88.md index be536612..4348fea7 100644 --- a/88.md +++ b/88.md @@ -14,7 +14,7 @@ Users can use relays offering mints they trust, or relays they don't trust but f Relays offering mints must have a keypair and an additional nostr keypair for its mint. -Nostr Cash uses derived keys, much like [NIP26](https://github.com/nostr-protocol/nips/blob/master/26.md). +Nostr Cash uses derived keys, much like [NIP26](https://github.com/nostr-protocol/nips/blob/master/26.md). Each "ecash" is actually just a derived privatekey that can be burned or passed to another user. All communication between the relay and user happen over [NIP04](https://github.com/nostr-protocol/nips/blob/master/04.md). From 933674fea07df029ee58a461e755b3494fef21f2 Mon Sep 17 00:00:00 2001 From: Ben Date: Thu, 29 Jun 2023 12:13:44 +0100 Subject: [PATCH 12/24] added explanation --- 88.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/88.md b/88.md index 4348fea7..922ed73a 100644 --- a/88.md +++ b/88.md @@ -14,7 +14,7 @@ Users can use relays offering mints they trust, or relays they don't trust but f Relays offering mints must have a keypair and an additional nostr keypair for its mint. -Nostr Cash uses derived keys, much like [NIP26](https://github.com/nostr-protocol/nips/blob/master/26.md). Each "ecash" is actually just a derived privatekey that can be burned or passed to another user. +Nostr Cash uses derived keys, much like [NIP26](https://github.com/nostr-protocol/nips/blob/master/26.md). Each "ecash" is actually just a derived private key that can be burned or passed to another user. All communication between the relay and user happen over [NIP04](https://github.com/nostr-protocol/nips/blob/master/04.md). @@ -56,6 +56,8 @@ spent: ### Mint details +For fetching info about the mint. + User DMs the relay: ```json From cf71afb42d2bbcab50c1dcd9a96ebc11e03100f9 Mon Sep 17 00:00:00 2001 From: Ben Date: Thu, 29 Jun 2023 12:14:01 +0100 Subject: [PATCH 13/24] added nostr cash Update 88.md Update 88.md Update 88.md Update 88.md typo typos typo adding descriptions for workflows Expanded explanation added explanation --- 88.md | 197 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 197 insertions(+) create mode 100644 88.md diff --git a/88.md b/88.md new file mode 100644 index 00000000..922ed73a --- /dev/null +++ b/88.md @@ -0,0 +1,197 @@ +NIP-88 +====== + +Nostr Cash (simple Nostr ecash) +----------------------------------- + +`draft` `optional` `author:benarc` + +> Nostr Cash is not blinded by default. + +Ecash is useful and relays should have the option to offer ecash mints. Other mints could exist as stand-alone clients, but relays are ideally placed to package in with their service offerings. + +Users can use relays offering mints they trust, or relays they don't trust but for smaller amounts. + +Relays offering mints must have a keypair and an additional nostr keypair for its mint. + +Nostr Cash uses derived keys, much like [NIP26](https://github.com/nostr-protocol/nips/blob/master/26.md). Each "ecash" is actually just a derived private key that can be burned or passed to another user. + +All communication between the relay and user happen over [NIP04](https://github.com/nostr-protocol/nips/blob/master/04.md). + +The mints ledger is two tables `active` and `spent`: + +``` +active: + key: , + amount: , + user: , + timestamp: + +spent: + key: , + amount: , + user: , + timestamp: +``` + +User client ecash wallet stores: + +``` +active: + key: , + amount: , + relay: , + relaykey: , + timestamp: + +spent: + key: , + amount: , + relay: , + relaykey: , + timestamp: +``` + +## Workflows + +### Mint details + +For fetching info about the mint. + +User DMs the relay: + +```json +{ + "mint": +} +``` + +Relay DMs user (maybe after a check if the relays mint has restricted access): + +```json +{ + "title": , + "description": , + "liquiity": , + "type": , + "fee": , +} +``` + +### Minting + +**For creating new ecash from a mint.** + +User DMs the relay: + +```json +{ + "amount": +} +``` + +Relay responds with payment request, which user pays: + +```json +{ + "request": +} +``` + +Once paid the mint generates derived keypair from the mints private key, storing in table `active`: + +```json +{ + "key": , + "amount": , + "user": +} +``` + +Mint replies: + +```json +{ + "key": , + "amount": +} +``` + +User client stores: + +```json +{ + "key": , + "amount": , + "relay": , + "relaykey": , + "timestamp": +} +``` + +### Claiming + +**For cashing in ecash with the mint.** + +User DMs relay: + +```json +{ + "key": , + "amount": , + "type": +} +``` + +Relay DMs user: + +```json +{ + "type": +} +``` + +User DMs relay: + +```json +{ + "request": , +} +``` + +### Sending + +**For sending ecash to another nostr user.** + +User DMs relay: + +```json +{ + "key": , + "amount": , + "type": +} +``` + +Mint `burns` the old record for the ecash and creates a new record(s), depending on if sending user is owed change (the old record moves from `active` to `spent` table). The mint creates a new record in `active` and DMs the recipient user the private-key/ecash. If change is due, another record is created in `active` and sent back to the sender user. + +Relay DMs user(s): + +```json +{ + "key": , + "amount": +} +``` + +User(s) client stores: + +```json +{ + "key": , + "amount": , + "relay": , + "relaykey": , + "timestamp": +} +``` From 3cf4a54aaddfd31731393b406354bfc6cd338a7c Mon Sep 17 00:00:00 2001 From: Ben Date: Thu, 29 Jun 2023 12:14:54 +0100 Subject: [PATCH 14/24] format --- 88.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/88.md b/88.md index 922ed73a..b90e2ded 100644 --- a/88.md +++ b/88.md @@ -56,7 +56,7 @@ spent: ### Mint details -For fetching info about the mint. +**For fetching info about the mint.** User DMs the relay: From 10407208a6200ea761b199b6e9dfa0271a11d3a5 Mon Sep 17 00:00:00 2001 From: Ben Date: Thu, 29 Jun 2023 13:56:29 +0100 Subject: [PATCH 15/24] added ecash disclaimer --- 88.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/88.md b/88.md index b90e2ded..f0263344 100644 --- a/88.md +++ b/88.md @@ -6,7 +6,7 @@ Nostr Cash (simple Nostr ecash) `draft` `optional` `author:benarc` -> Nostr Cash is not blinded by default. +> Nostr Cash is not blinded, so prob not stricly an ecash. The logic is relays who want to offer a custodial service can do without the risk of being used for coin mixing. Ecash is useful and relays should have the option to offer ecash mints. Other mints could exist as stand-alone clients, but relays are ideally placed to package in with their service offerings. From 2198147d2ba1d5cc99a0074e2fcda755312bf2d2 Mon Sep 17 00:00:00 2001 From: Ben Date: Thu, 29 Jun 2023 13:59:52 +0100 Subject: [PATCH 16/24] disclaimer elaborated on --- 88.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/88.md b/88.md index f0263344..1a6d72a9 100644 --- a/88.md +++ b/88.md @@ -6,7 +6,7 @@ Nostr Cash (simple Nostr ecash) `draft` `optional` `author:benarc` -> Nostr Cash is not blinded, so prob not stricly an ecash. The logic is relays who want to offer a custodial service can do without the risk of being used for coin mixing. +> Nostr Cash is not blinded, so prob not stricly an ecash. The reason for not blinding, is to keep implementing simple, and also on the assumption the type of relays who want to offer a legitimate custodial service would prefer to do without the risk of being used for things like "coin mixing". Ecash is useful and relays should have the option to offer ecash mints. Other mints could exist as stand-alone clients, but relays are ideally placed to package in with their service offerings. From feba8cf6a1ccee9ce5a3eb284b0703494f0d5aa3 Mon Sep 17 00:00:00 2001 From: Ben Date: Thu, 29 Jun 2023 14:11:13 +0100 Subject: [PATCH 17/24] removed ecash mention, its not ecash --- 88.md | 34 +++++++++++++++++----------------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/88.md b/88.md index 1a6d72a9..2abf2e16 100644 --- a/88.md +++ b/88.md @@ -1,20 +1,20 @@ NIP-88 ====== -Nostr Cash (simple Nostr ecash) +Nostr Cash (simple Nostr cash/token/cheque) ----------------------------------- `draft` `optional` `author:benarc` -> Nostr Cash is not blinded, so prob not stricly an ecash. The reason for not blinding, is to keep implementing simple, and also on the assumption the type of relays who want to offer a legitimate custodial service would prefer to do without the risk of being used for things like "coin mixing". +> Nostr Cash is not blinded, so is not cash. The reason for having unblinded, is to keep implementing simple/flexible, and also on the assumption the type of relays who want to offer a legitimate custodial service would prefer to do without the risk of being used for things like "coin mixing". -Ecash is useful and relays should have the option to offer ecash mints. Other mints could exist as stand-alone clients, but relays are ideally placed to package in with their service offerings. +Electronic cash is useful and relays should have the option to offer minting/custodial services. Other mints could exist as stand-alone clients, but relays are ideally placed to package in with their service offerings. Users can use relays offering mints they trust, or relays they don't trust but for smaller amounts. Relays offering mints must have a keypair and an additional nostr keypair for its mint. -Nostr Cash uses derived keys, much like [NIP26](https://github.com/nostr-protocol/nips/blob/master/26.md). Each "ecash" is actually just a derived private key that can be burned or passed to another user. +Nostr Cash uses derived keys, much like [NIP26](https://github.com/nostr-protocol/nips/blob/master/26.md). Each "cash" is actually just a derived private key that can be burned or passed to another user. All communication between the relay and user happen over [NIP04](https://github.com/nostr-protocol/nips/blob/master/04.md). @@ -34,18 +34,18 @@ spent: timestamp: ``` -User client ecash wallet stores: +User client cash wallet stores: ``` active: - key: , + key: , amount: , relay: , relaykey: , timestamp: spent: - key: , + key: , amount: , relay: , relaykey: , @@ -80,7 +80,7 @@ Relay DMs user (maybe after a check if the relays mint has restricted access): ### Minting -**For creating new ecash from a mint.** +**For creating new cash from a mint.** User DMs the relay: @@ -112,7 +112,7 @@ Mint replies: ```json { - "key": , + "key": , "amount": } ``` @@ -121,7 +121,7 @@ User client stores: ```json { - "key": , + "key": , "amount": , "relay": , "relaykey": , @@ -131,13 +131,13 @@ User client stores: ### Claiming -**For cashing in ecash with the mint.** +**For cashing in cash with the mint.** User DMs relay: ```json { - "key": , + "key": , "amount": , "type": } @@ -161,25 +161,25 @@ User DMs relay: ### Sending -**For sending ecash to another nostr user.** +**For sending cash to another nostr user.** User DMs relay: ```json { - "key": , + "key": , "amount": , "type": } ``` -Mint `burns` the old record for the ecash and creates a new record(s), depending on if sending user is owed change (the old record moves from `active` to `spent` table). The mint creates a new record in `active` and DMs the recipient user the private-key/ecash. If change is due, another record is created in `active` and sent back to the sender user. +Mint `burns` the old record for the cash and creates a new record(s), depending on if sending user is owed change (the old record moves from `active` to `spent` table). The mint creates a new record in `active` and DMs the recipient user the private-key/cash. If change is due, another record is created in `active` and sent back to the sender user. Relay DMs user(s): ```json { - "key": , + "key": , "amount": } ``` @@ -188,7 +188,7 @@ User(s) client stores: ```json { - "key": , + "key": , "amount": , "relay": , "relaykey": , From 29a83686786df8828fafb409dc1d96f0b5c32d42 Mon Sep 17 00:00:00 2001 From: Arc <33088785+arcbtc@users.noreply.github.com> Date: Thu, 29 Jun 2023 14:13:56 +0100 Subject: [PATCH 18/24] Update 88.md --- 88.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/88.md b/88.md index 2abf2e16..9ce97431 100644 --- a/88.md +++ b/88.md @@ -6,8 +6,6 @@ Nostr Cash (simple Nostr cash/token/cheque) `draft` `optional` `author:benarc` -> Nostr Cash is not blinded, so is not cash. The reason for having unblinded, is to keep implementing simple/flexible, and also on the assumption the type of relays who want to offer a legitimate custodial service would prefer to do without the risk of being used for things like "coin mixing". - Electronic cash is useful and relays should have the option to offer minting/custodial services. Other mints could exist as stand-alone clients, but relays are ideally placed to package in with their service offerings. Users can use relays offering mints they trust, or relays they don't trust but for smaller amounts. From b57abac1d58bf404f5ce280650cd6f02e916a0a8 Mon Sep 17 00:00:00 2001 From: Arc <33088785+arcbtc@users.noreply.github.com> Date: Thu, 29 Jun 2023 14:54:28 +0100 Subject: [PATCH 19/24] Update 88.md --- 88.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/88.md b/88.md index 9ce97431..b906c0f0 100644 --- a/88.md +++ b/88.md @@ -6,6 +6,8 @@ Nostr Cash (simple Nostr cash/token/cheque) `draft` `optional` `author:benarc` +Nostr Cash is simple and flexible. User gives a mint some money and the mint issues the user electromic cash/cheque/token that can be used as money in nostr. + Electronic cash is useful and relays should have the option to offer minting/custodial services. Other mints could exist as stand-alone clients, but relays are ideally placed to package in with their service offerings. Users can use relays offering mints they trust, or relays they don't trust but for smaller amounts. From d3a2cddbc690cb4e365485a027d7a36abfc2ae9f Mon Sep 17 00:00:00 2001 From: Arc <33088785+arcbtc@users.noreply.github.com> Date: Thu, 29 Jun 2023 14:55:01 +0100 Subject: [PATCH 20/24] Update 88.md --- 88.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/88.md b/88.md index b906c0f0..0a979345 100644 --- a/88.md +++ b/88.md @@ -6,10 +6,10 @@ Nostr Cash (simple Nostr cash/token/cheque) `draft` `optional` `author:benarc` -Nostr Cash is simple and flexible. User gives a mint some money and the mint issues the user electromic cash/cheque/token that can be used as money in nostr. - Electronic cash is useful and relays should have the option to offer minting/custodial services. Other mints could exist as stand-alone clients, but relays are ideally placed to package in with their service offerings. +Nostr Cash is simple and flexible. User gives a mint some money and the mint issues the user electromic cash/cheque/token that can be used as money in nostr. + Users can use relays offering mints they trust, or relays they don't trust but for smaller amounts. Relays offering mints must have a keypair and an additional nostr keypair for its mint. From 131b1cca4ff3fd3b4883d8fd809adbcbe1cdd63a Mon Sep 17 00:00:00 2001 From: Arc <33088785+arcbtc@users.noreply.github.com> Date: Thu, 29 Jun 2023 14:58:08 +0100 Subject: [PATCH 21/24] Update 88.md --- 88.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/88.md b/88.md index 0a979345..13892a7a 100644 --- a/88.md +++ b/88.md @@ -10,7 +10,7 @@ Electronic cash is useful and relays should have the option to offer minting/cus Nostr Cash is simple and flexible. User gives a mint some money and the mint issues the user electromic cash/cheque/token that can be used as money in nostr. -Users can use relays offering mints they trust, or relays they don't trust but for smaller amounts. +Nostr Cash is entirely custodial and trust based, and is just a common standard for users to send/receive value in nostr. Keepiong mints simple means more users can run, for themselves, their family, or the whole world. Relays offering mints must have a keypair and an additional nostr keypair for its mint. From 8bb004db59d4c42b61e736907983ea17d9788913 Mon Sep 17 00:00:00 2001 From: Arc <33088785+arcbtc@users.noreply.github.com> Date: Thu, 29 Jun 2023 14:58:28 +0100 Subject: [PATCH 22/24] Update 88.md --- 88.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/88.md b/88.md index 13892a7a..519ecbda 100644 --- a/88.md +++ b/88.md @@ -10,7 +10,7 @@ Electronic cash is useful and relays should have the option to offer minting/cus Nostr Cash is simple and flexible. User gives a mint some money and the mint issues the user electromic cash/cheque/token that can be used as money in nostr. -Nostr Cash is entirely custodial and trust based, and is just a common standard for users to send/receive value in nostr. Keepiong mints simple means more users can run, for themselves, their family, or the whole world. +Nostr Cash is entirely custodial and trust based, and is just a common standard for users to send/receive value in nostr. Keeping mints simple means more users can run, for themselves, their family, or the whole world. Relays offering mints must have a keypair and an additional nostr keypair for its mint. From fa086e0c6aeeaf92d423ce87f4dc23430725f5e7 Mon Sep 17 00:00:00 2001 From: Arc <33088785+arcbtc@users.noreply.github.com> Date: Thu, 29 Jun 2023 15:03:36 +0100 Subject: [PATCH 23/24] Update 88.md --- 88.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/88.md b/88.md index 519ecbda..985db5eb 100644 --- a/88.md +++ b/88.md @@ -108,7 +108,7 @@ Once paid the mint generates derived keypair from the mints private key, storing } ``` -Mint replies: +Mint replies to user: ```json { From 4fa5b4f9974ec82877ae11a0c72f65b9f6b25817 Mon Sep 17 00:00:00 2001 From: Arc <33088785+arcbtc@users.noreply.github.com> Date: Fri, 30 Jun 2023 12:18:56 +0100 Subject: [PATCH 24/24] Update 88.md Co-authored-by: arthurfranca --- 88.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/88.md b/88.md index 985db5eb..b68bd663 100644 --- a/88.md +++ b/88.md @@ -14,7 +14,7 @@ Nostr Cash is entirely custodial and trust based, and is just a common standard Relays offering mints must have a keypair and an additional nostr keypair for its mint. -Nostr Cash uses derived keys, much like [NIP26](https://github.com/nostr-protocol/nips/blob/master/26.md). Each "cash" is actually just a derived private key that can be burned or passed to another user. +Nostr Cash uses derived keys, much like [NIP06](https://github.com/nostr-protocol/nips/blob/master/06.md). Each "cash" is actually just a derived private key that can be burned or passed to another user. All communication between the relay and user happen over [NIP04](https://github.com/nostr-protocol/nips/blob/master/04.md).